QA Feedback - Staging Review - eBenefits [Personalized Career Planning and Growth (CH36)]

[pjhill]

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

Thoughts/questions

• Great job including a wide range of platforms in your cross-platform testing!

Feedback

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

Must: Ch36 - Copy mismatches: Given that this issue was resolved as invalid because new copy/design changes were implemented, the test cases should be updated to reflect the design changes and re-executed prior to launch in order to validate the design matches the implementation.

Should: None

Consider: CH36 - Unauth'd Vet / Svc Mbr - Copy/Styling:

• Consider using unordered lists to define the required fields in forms and their corresponding error messages.
• There appear to be a few outdated screen shots in the test case as well. Consider updating screen shots to reflect final prototype information.
• Update language in step 11 to reflect language in app, or file defect:

[tlei123]

@pjhill , re. the "Must" item...

All previously-failed test-cases now re-run and all Passed.

Test-cases' page-references now updated ("Claimant" -> "Applicant"). At least for my two previously-failed steps in each copy/styling case, the expected-results actually had links to the updated designs, so no need to replace any screenshots there.

@jason-gcio @sporeboy , about the first two "Consider" items:

• Required-field list w/ corresponding error-messages: Might it help your Team to do this as a regular process-step? For my QA, I think the value-add would be if we do track a customized req'd-field list [for those req'd fields where we're customizing the error-message(s)]. Otherwise, I'm fine w/ just checking field-labels on design-screens -- the error-messages are mostly standardized.
• Outdated screenshots: I always prefer links over screenshots, so that I get the latest versions. I should have bandwidth next week to either update the stale screenshots or better yet replace them w/ links.

P.S. @pjhill , finding updating designs here is actually the exception more than the rule -- most of the time, across most Teams, the designs inevitably go stale as further changes are made directly in the product [which is why I've recently started wording my expected-results "Copy/styling should look like this prototype," instead of "...should match this screen."].

[jason-gcio]

Links are definitely a better idea...not sure why I submitted screenshots. Content is always moving! I'll see about switching those over to links, you shouldn't have to do that.

[tlei123]

I'll see about switching those [screenshots] over to links, you shouldn't have to do that.

Thanks so much, @jason-gcio ! I'll leave this to you then. :)