QA Feedback - Staging Review - "Your VA payment history" - eBenefits

[ddzz]

VFS acceptance criteria

• [x] 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

Feedback

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

Should:

• Include a TestRail test case for existing automated E2E tests and label them as Automation Type: Cypress.

Consider:

• Consider investigating table formatting inconsistencies for the View Payment History Paage. See this bug.
• The prototype shows 12 payment rows per page while on staging 6 rows are shown per page. Some of the TestRail cases also mention intervals of 5. Please reconcile these differences.
• Consider fixing the copy mismatch described in this bug.
• Consider splitting up TestRail test cases to test both payments received and payments returned.

[tlei123]

@ddzz , it's still early days as far as an official VSA Cypress-TestRail integration/process goes, but I'm gonna pilot for this product: #17843

@micahchiang , FYI, as part of Cypress-TestRail integration, I'll be prepending TestRail test-case IDs to your Cypress test-descriptions (the strings inside the it(...)s), and requesting your review & approval of my upcoming PR when ready.

cc @jason-gcio @pjhill

[tlei123]

[Just moved my comment here to my Crypess-TestRail integration ticket]

[tlei123]

@ddzz , Should item's been addressed via #17843 .

@cohnjesse @micahchiang , when you add/delete tests to/from view-payments.cypress.spec.js test-file, pls. be sure to either:

• let me know; or
• update the corresponding TestRail test-cases yourself. For a quick-view of the relevant procedure, see my ticket-comment.. Here're the cypress-testrail-reporter docs: VSP-QA's cypress-testrail-reporter docs, VSA-QA's cypress-testrail-reporter help.

Successful TestRail test-run R1536:

cc @jason-gcio @pjhill