For a next-build layout to launch we will need sign off by multiple stakeholders to ensure consistency from content-build to next-build. This ticket aims at reviewing the "Stories" template of next-build to make sure it matches what is currently in production (content build). The end result should be a 1:1 mirror of the current production and next build dev pages.
Description or Additional Context
We need to complete frontend QA to confirm that the Next Build templates are producing the same front end experience as the existing templates within Content Build. The IIR team will perform the QA on the "Stories" template and provide feedback about their findings in the IIR - QA Template Tracker - Stories
An overview of the review process can be found here
[ ] Reviewer should QA 25 URLs for Next Build's "Stories" template vs. its corresponding Content Build's "Stories" template.
You can find Stories URLs to test by going to any facilities homepage and clicking on the "Stories" section
The Next Build version of that same template can be found by putting "dev" in front of the current Content Build URL for that page.
[ ] For each URL, the reviewer should review that following and track their findings in the IIR - QA Template Tracker - Stories. No more than 5 stories "Stories" from a given Facility should be tested (we need to review multiple Facilities).
[ ] Fonts (spacing, color, weight)
[ ] Images (icons, background images)
[ ] Layout
[ ] Functionality
[ ] Navigation (to other pages and back)
[ ] Data (content is consistent)
Stories
Any current production link can be used to test a "Stories" page.
Simply find any "Stories" page and replace the beginning of the url with https://dev.va.gov.
Updated the tracker, please add Operating System, Browser and Size (Desktop or Mobile) when issues are identified, it helps the team troubleshooting. Thanks!!
User Story or Problem Statement
For a next-build layout to launch we will need sign off by multiple stakeholders to ensure consistency from content-build to next-build. This ticket aims at reviewing the "Stories" template of next-build to make sure it matches what is currently in production (content build). The end result should be a 1:1 mirror of the current production and next build dev pages.
Description or Additional Context
We need to complete frontend QA to confirm that the Next Build templates are producing the same front end experience as the existing templates within Content Build. The IIR team will perform the QA on the "Stories" template and provide feedback about their findings in the IIR - QA Template Tracker - Stories
An overview of the review process can be found here
Reference Documentation
Steps for Implementation
You can find Stories URLs to test by going to any facilities homepage and clicking on the "Stories" section
The Next Build version of that same template can be found by putting "dev" in front of the current Content Build URL for that page.
Stories
Any current production link can be used to test a "Stories" page. Simply find any "Stories" page and replace the beginning of the url with https://dev.va.gov.
Prod (Content Build) - https://www.va.gov/eastern-oklahoma-health-care/stories/access-va-health-care-during-federal-holidays-and-247-365-with-va-health-connect/ Dev (Next Build) - https://www.dev.va.gov/eastern-oklahoma-health-care/stories/access-va-health-care-during-federal-holidays-and-247-365-with-va-health-connect/
Known Issues
Next
Production
Next
Production
Next
Production
Next
Production
Acceptance Criteria