R6.3 Automation for testing

[MHoov]

Refer to mural R5.4 add link

Epic Details

• User Story: Dev team will be able to have additional checks when submitting code, this will help find any issues within the code.
• Playback Demonstration: Test case can be presented for the elements/sections we're testing for - backend
• Metric: By the amount of test-cases added to the automation framework

tell them (concisely), and where?_

• Release Notes will highlight What's Changed

What project/section is the Epic for?

• engine

Folder of test cases

• List of automation flows for checker #1996
• Verify and understand the relation of files for automation #2033
• Verification of scan button dropdown pre scan - Automation  #1762
• Verification of header components before scan sanity automation  #1729
• Verification of Scan button for automation test  #1761
• Verification of header components after scan - sanity automation  #1763
• Validation of option view menu bar for automation  #1764

Definition of Done

• Results are added to the Release Mural with a description of what was accomplished, KPIs, etc
• All content has been reviewed for grammar, spelling, style and technical accuracy
• All code committed to the main branch
• All unit tests pass (including accessibility)
• Demo works in the staging environment
• At least one performance metric / monitor constructed

[MHoov]

Notes form 12 Aug:
Some of these may already have been implemented, but should be verified.
Add any of your normal testing flows
Have an initial list of flows next week to review and prioritize.

Related issues from prior release (6.2)

• Start working with checker project on writing test case automation for new work  #1841
• Prep extension environment for test automation. #1907
• chore(engine): Create archive build script that has a pull master to ensure builds are updated #1937

[MHoov]

Notes from 20 Aug:

• Need to specify what will and won't be automated for this release; e.g. Assessment Panel, Excel Reports, KCM View
• Document any assumptions, e.g. since both the Assessor view and Checker view are using the same code, so we only need to check one
• include an accessibility test at the end of each use test scenario

[MHoov]

Lost our QA resource so this was halted. It will be replaced with a new 'QA & Implementation' process the whole dev team will be responsible for.