Staging Review [Authenticated Experience, Notification Preferences]

[ajakabcin]

Steps to complete Staging Review

Before meeting

VFS Product Manager

• [x] Create this issue and notify the Collaboration Cycle team of this ticket in the in #vfs-platform-support (see Slack Workflow (User guide).

• [x] Add artifacts listed below to the ticket at least 4 days before scheduled meeting.

• [x] Ensure you've provided staging access information for the tool or feature. (Don't put staging credentials in your va.gov-team ticket; store or reference them in a .md file in the va.gov-team-sensitive repository.)

  Platform

• [x] Schedule meeting with Platform reviewers and VFS team attendees listed in ticket.

• [x] Create feedback tickets and link them to the Staging Review epic (if no feedback, please comment stating that).

After meeting

VFS

• [ ] Respond to Platform feedback tickets.
• [ ] Update ticket with the product’s launch date after it has gone live.
• [ ] Close ticket when the review is complete and the product has launched.

Platform

• [x] Update Platform Collaboration Point Tracker.

Artifacts

Provide links or documents for the following:

• [ ] Staging: staging.va.gov/profile/notifications
• [ ] Test user info
  • [ ] Staging test-user information
  • [ ] QA version
  • [ ] Accessible version of test cases
• [ ] Product outline - Notification Preferences (communication permissions) product outline
  • [ ] Notification Preferences Release plan

Content artifacts

• [ ] Content source of truth: Notification Preferences FE documentation
• [ ] Prototypes: Desktop, Mobile, Interactivity

QA artifacts

Learn more about QA test plans

• [x] Product test cases/test plan in TestRail with test execution logs
• [x] Coverage for References
• [No Summary (Defects) report -- No defects logged.*]

Accessibility artifacts

• [ ] Notification Preferences - Accessibility Staging Review Prep

• [ ] List of known issues

• Issue 1

• Issue 2

• Issue 3

VFS Meeting Attendees

Required

• Product Manager: @ajakabcin
• OCTO-DE Product lead: @Samara-Strauss
• OCTO-DE Design lead: Ryan Thurlwell

Team Members

• @erikphansen
• @lihanli
• @andaleliz

VFS Attendees

• Content and IA: @DanielleThierryUSDSVA and @mnorthuis
• Accessibility: @joshkimux and/or @AngelaFowler82
• QA specialists: @tlei123

Scheduling

Thursday, October 14 at 2:00 pm ET

Additional information

Please refer to Platform Collaboration Cycle or the Staging Review Touchpoint on Platform website for more information about the Collaboration Cycle.

---

* There were Safari & IE11 sign-in issues, but not related to this Feature. [See test-plan ticket Comments starting with this one.]

[peggygannon]

@ajakabcin Hello, staging review has been scheduled for Thursday 10/14 at 2 p.m. ET.

[ajakabcin]

Thank you @peggygannon !

[tlei123]

@pjhill @ddzz , QA test-runs completed, and artifact-links provided above in main description.

cc @ajakabcin @shiragoodman

[tlei123]

FYI, @pjhill @ddzz , Cypress-TestRail integration's also done. Test-results pushed to TestRail [under Completed section > Monday, October 4, 2021].

cc @erikphansen

[ajakabcin]

@joshkimux and @AngelaFowler82 I added a a11y version of test cases to the artifacts list

[allison0034]

@ajakabcin I cannot seem to login with any of the accounts. Is staging down?

We’re sorry. Something went wrong on our end, and we couldn’t sign you in.

[Samara-Strauss]

@allison0034 looks like there might be a staging issue right now according to the identity Slack channel. Probably best to wait a bit and try again later.

[pjhill]

Platform has no QA feedback for this staging review -- great job!

[ajakabcin]

Closing this out - the remaining open issue is with Public Websites