VSP QA feedback for Public Websites [Staging Review]

[pjhill]

VSP QA feedback for Public Websites [Staging Review]

Feedback framework

• ❗️ Must for if the feedback must be applied
• ⚠️Should if the feedback is best practice
• ✔️ Consider for suggestions/enhancements

Links

Test Plan / Execution logs: https://dsvavsp.testrail.io/index.php?/plans/view/685 Coverage for References Report https://dsvavsp.testrail.io/index.php?/reports/view/142 Summary (Defects) Report https://dsvavsp.testrail.io/index.php?/reports/view/143

Feedback

Test Execution Logs

1. Comment: That's a lot of test failures. Once you've been able to confirm that the in-process defect resolutions described in the staging review are in place, I would recommend re-running your test plan in at least one browser completely and target the test cases that uncovered the related defect.
2. Comment: As defects are worked and resolved, be sure to update the defect tickets with new information in order to inform the timing and parameters of QA test runs.
3. Comment: Good cross-browser coverage is demonstrated in this test plan execution. You may want to expand to include some cross-platform test runs as well such as iOS + Safari, Android + Chrome, or macOS + Safari. Consult with the appropriate analytics for your product to identify additional platforms based on usage.

Coverage for References Report

1. ⚠️Should: Although there are GitHub tickets linked for each test case, the derivation of the test steps from those issues relies on a fair amount of undocumented information or assumptions. In the future, the team should create more granular user stories that can be linked 1:1 to test cases.

Summary (Defects) Report

1. ✔️ Consider: Defect 15610 -- Given the duplicate defect between 15488 and 15610 and given that 15488 has been closed, consider linking to the open defect in future test runs so others don't have to dig as much for the defect status / resolution.

Definition of Done

• [x] Acknowledge each item of feedback with a decision
• [ ] VSP QA will close ticket after reviewing feedback decisions

[brianalloyd]

Concur on the recommendation to create more granular user stories that can be linked 1:1 to test cases, we're going to work this into planning efforts forward. Appreciate the feedback and recommendations.