Working Mode Data Support Analysis

Overview

This is a summary of the data needed to execute the Working Mode. It is based on this analysis of working mode scenarios and the working mode elements defined in the Glossary.

This summary shows the data that people walking through working mode scenarios need when operating on the elements defined by the working mode, e.g., a test plan or result set. The attribute lists are not intended to define a data model; they represent user needs.

Test Plan

Attributes of a Test Plan

• Name
• Source repository
• Version = Date of last revision calculated from GIT revisions
• Version history
• Working Mode Phase
• Working Mode Phase Start Date
• Target Candidate Phase Exit Date
• Working Mode Phase Change History
• In-scope AT
• Semantic pattern name and link (e.g., APG pattern or ARIA semantic)
• Test case name and link (e.g., APG example name and link to implementation targetted by the tests)
• Collection of Tests
• Links to test results
• Links to GitHub issues raised against any of:
  • The plan itself
  • Any test in the plan
  • Any test result

Use case notes

• We are going to end up with multiple plans per APG pattern or ARIA attribute, each with a different set of in-scope AT. The ability to slice data by semantic will be essential when the project is covering many more AT.

Result Sets

Note: It might be helpful to add some additional terms to the glossary to make discussion of result sets more concise. In particular, we may want to define "Report".

Attributes of result sets

• Associated test plan
• AT
• AT version
• Browser
• Browser version
• Version = completion date
• Tester profile
• Collection of results from each test in the associated plan:
  • AT response for each command
  • Assertion verdict for each assertion for each command
  • Unexpected behaviors for each command