-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QA test plan & testing of injected header flattening / header-footer #18358
Comments
@FranECross we realized today in scrum that in the spirit of our recent QA conversations we need to be very deliberate about how we go about testing Randi's injected header changes, to make sure we don't break anything in prod. We're working up this ticket and will need to figure out how to cover the work in it (most of which may happen while you're out this week.) |
The pull request for the code split is ready for review: department-of-veterans-affairs/vets-website#27590 As a reminder, the injected scenario can only be tested when running locally. But we also want to verify that no regressions were introduced to the VA.gov header/footer. This can be checked on the review instance in the PR. |
I was able to get the promo block images to show up after some metaphorical tree shaking on content-build (maybe cached Drupal assets?). It may be a toss-up whether it works for other folks, but the promo block info is in my screenshots in the PR description. |
@jv-agile6 is completing test plan for mobile steps & what injected does on prod vs. VA.gov |
I have completed my testing, all my notes are in the test plan doc and related mural. Let me know if anything needs further clarifcation |
I've also completed testing and added my notes to the spreadsheet and Mural. |
Completed testing and updated spreadsheet and added a few cards to the mural. |
Mid-sprint: testing will repeat, timing to close for end of sprint will depend on re-verification. |
Thread with more details on the rework / plan of record: https://dsva.slack.com/archives/C03LFSPGV16/p1720028486617809 |
Testing context
Implementation ticket being tested: #17291
Who wrote the changes: @randimays
Where can testing be performed
Scope of changes: high level
In #17291, Randi has made the following changes:
Everything from the header and footer that can be clicked should be checked.
Affected components / what changed / what is new and should be tested
Only things that are still react are the Search bar and login modal
Gotchas / Exceptions
Acceptance Criteria / Ownership
The text was updated successfully, but these errors were encountered: