Closed jilladams closed 2 months ago
@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: https://github.com/department-of-veterans-affairs/vets-website/pull/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.
Megamenu Promo block images don't work locally. The dev branch is pulling from Staging, and these images are broken on Drupal staging as well.
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 @chriskim2311 will run the test cases for injection locally @laflannery / @thejordanwood will divide the modernized testing on RI
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.
Update: I've addressed most of the feedback, but this one requires significant rework:
Unfortunately we'll have to go through the spreadsheet for testing again as I'll be changing most of the code.
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
@chriskim2311 @thejordanwood @laflannery I've completed the refactor and addressing the initial wave of feedback. The PR is now ready for your review again 🥳
CC @FranECross @jilladams @Agile6MSkinner
The screenshots below are intentional changes / differences; they were defects in Teamsites that have been fixed to match VA.gov.
Round 1 Feedback |
---|
I made a Round 2 page in the spreadsheet and a round 2 section in the mural for our testing
I've completed round 2 of testing and put my notes in the spreadsheet and Mural board.
I am also done and my notes are added as well
Code review and local testing complete from my end, no additional notes/comments than already stated.
@chriskim2311 @thejordanwood @laflannery Injected header/footer is ready for Round 3 of testing! The changes were more isolated this time; I don't think it'll be necessary to click every link, but test as you see fit.
@chriskim2311 here's the only commit of the changes made since the last round: https://github.com/department-of-veterans-affairs/vets-website/pull/27590/commits/75b70e424652826d19a98b0bc4f759c1b676c8fd
Here's what's changed since last time
@randimays (and others for awareness who are retesting), I went through the issues we found and for the most part everything was resolved. I found 1 item that I still saw and one new item on the promos.
@laflannery Addressed those issues in the latest commit that is pushed up to the branch: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/18358#issuecomment-2239712724
@randimays Re-reviewed and I got nothing left for you!
@randimays PR approved, no issues in code changes or visually!
@randimays Re-reviewed this and everything looks good. Approved!
CLOSING. WOO.
@jilladams Should we leave this open to test the headers in staging and prod?
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