Quality Assurance Feedback - Usability Testing Prep - [VAOS, VAOS for Distribution]

[pjhill]

VFS acceptance criteria

• [ ] Let VSP know when the Must feedback has been incorporated
• [ ] Leave any comments for feedback you decide not to take
• [ ] VFS team closes the ticket

Thoughts/questions

• The UTP epic indicates that test artifacts are currently unavailable. Accordingly, no QA artifacts have been reviewed. Instead, VSP examined the prototypes in order to provide some guidance about QA strategy.

Feedback

• Must = the feedback must be applied
• Should = the feedback is best practice
• Consider = suggestions/enhancements

Must:

Should:

1. As you work on creating your test plan for this product, you should aim to create traceability from user stories that define the acceptance criteria to individual test cases that verify the completion of the AC. This can be accomplished in TestRail by using the reference field to refer to the user story ticket's unique ID in GitHub.
2. Based on a review of the prototype, there appear to be many varied user flows for this product. VSP strongly encourages teams to verify each flow with a use case which is strongly tied to robustly defined user stories with clearly defined acceptance criteria.
3. E2E tests should seek to verify the core user experiences of the product and not all edge cases.

Consider:

1. Consider testing both mobile and desktop views in E2E tests. Given the complexity of the feature, we want to ensure functionality is consistent among multiple platforms. Our Cypress best practices document includes notes on how to test multiple views.

[laurenernest]

Thanks for the recommendations! I chatted with our SQA support and we're trying a way to work with their process and also document. Here's the ticket for our trial run #20064.