Create new non-lb QA standard for logging silent failures

User Story

As a Platform Team member supporting the OCTO effort for zero silent failures for VA.gov, I want to introduce a new QA Standard for VFS teams to log/capture silent failures so that OCTO can keep track of this metric moving forward.

Assignee: @it-harrison Peer Reviewer: @erinrwhite

Description

In order to help OCTO capture data relating to silent failures, specifically around capturing a silent failure and capturing the prevention of a silent failure, Governance has been asked to introduce a new QA standard requiring VFS teams to log silent failures data. The new standard will have ID QA7 and reference the Logging silent failures gh guidance.

In order to validate this logging of silent failures at a VFS team Staging Review, Governance will ask VFS teams to specify within their Collab Cycle Request ticket to "point to the lines of code in GitHub that show this logging is occurring" per Governance PO @humancompanion-usds .

Standard area: Logging silent failures ID: QA7 Standard description: The product code must log all silent failures to statsd Severity: Warning, not launch-blocking

Impacted Artifacts

Live pages

Drafted pages

Tasks

[ ] Create a draft of the QA Standards page on Platform Website
[ ] In the draft, add QA7 per the description above.
[ ] In the draft, add a new section under "How Standards are validated" for Logging Silent. Provide specific details as to how the standard is validated, including a link to the logging silent failures gh guidance.
[ ] For the How to complete a QA review for SR touchpoint doc, add a new section for Logging Silent Failures, including information wrt how Governance will validate (no need to create a draft - just edit the live doc)
[ ] For the gh template, create a PR with proposed changes to the template, including a new section for Logging Silent Failures
[ ] Draft a new post for the Collab Cycle Change history log.
[ ] Create a Slack post for #vfs-change-announcements channel following change announcement guidance. No need to create a new draft page... Slack announcement draft can be shared in this ticket via GH comment.
[ ] When all changes are drafted, shared with @humancompanion-usds for his review and approval.
[ ] If required, make changes requested by Matt.
[ ] Once Matt has signed off on changes, publish all pages to Platform Website. Once all pages are live, announce changes via #vfs-change-announcements channel on OCTO Slack.

Peer Review

To be completed by peer reviewer

[ ] User story and acceptance criteria are met

Acceptance Criteria

[ ] We have added a new QA standard for logging silent failures
[ ] We have an operational process for validating that this standard is met at Staging Reviews
[ ] We have modified our template for reporting to the VFS team at SR whether the Logging Silent Failures QA standard was met or not met.
[ ] We have announced our changes to VFS teams

Team Notification

[ ] Slack post on #platform-governance-team
[ ] Presentation at Weekly Initiative Meeting
[x] No notification needed

How to prepare this issue

Refinement

[x] Ticket has user story, description, tasks, and acceptance criteria
[x] Ticket has been sized
[x] Once all above items are checked, add the 'Ready' label.
Planning

If this ticket is picked up from the Backlog mid-sprint, connect with Shira to ensure the below items are completed correctly
[ ] Ticket has been discussed as a team at Planning
[x] Ticket has been assigned to appropriate initiative or quarterly epic
[x] Ticket has been assigned to a Sprint
[ ] Ticket has been moved to the Planned pipeline in the Governance team board
[ ] Ticket as an assignee and peer reviewer

department-of-veterans-affairs / va.gov-team