QA Q4: Stability & consistency improvements in automated & manual testing

[kellylein]

Purpose of this feature:

• For Bug tickets and maintenance tasks, mostly focused around stability & consistency across detox & manual testing

Project Status Overview

Project Objective:

Work and effort for Quality Assurance and Release Management (Qart) Team to manage team specific bugs, maintenance tasks and technical debt in order to prevent a culmination of technical / coding debt.

Items may include:

• Qart specific bugs
• Testing Automation / Detox fixes and enhancements
• Creating new or updating Qart specific documentation
• Qart team knowledge / documentation / inventoring

Stakeholder Updates

Date	Progress & Key Accomplishments	Issues/Risks/Blockers
10/30/2024	Closed several upkeep/fix tickets with detox, including starting to add comments to make the scripts more friendly for Experience teams. Published 'close-not fixing' documentation, and closed 8 bug tickets from the backlog.	n/a - Green

Detailed Project Scope

OKRs

• Stability
  • Reduce QA, DevOps, and Accessibility bugs by 25%
  • Zero failed RC testing due to bugs
  • Zero app store rejections

Assumptions

Assumptions that need to be true for this project

1.) Team will use their full capacity allocation for work on bugs and tech debt

2.) Work in this epic is purely for QA, anything tied to mobile app features (Global or H&B) will be part of their unique bug epics

3.) QA will be able to spend their allotted capacity on this epic vs being taken up by Flagship App / Platform teams which has happened in past quarters

4.) App store may reject a submission but they inform the team on why and we have the ability to fix it. It should only be seen as negative if they reject it and we miss a release.

5.) RC testing may uncover a bug or be told that a known bug is acceptable by PM or POs. When this happens RC testing will continue and account for this acceptable risk by the PM or POs.

Risks

Risks identified and accepted by stakeholders

1.) Team's capacity for bugs / tech debt is pulled off for other work (unplanned, underestimated, change in priority)

2.) Team appropriately add bug and severity labels

3.) Team adds Bug and Severity level to ticket name

Project Scope

Items in and out of scope

In Scope	Out of Scope
Qart specific work	Flagship, Design System, API, H&B, external team specific tickets

Important Project Links

Links

• Github Epic
  - Github Qa and Release Team
• Github Bugs Details
• Board with Bug Label
• Board with Sev 1 Label
• Board with Sev 2 Label
• Board with Sev 3 label
• Bug Tracking for Q2

Team Members

Contact List

VA:

• Mobile OCTO Product Leads: Don McCaughey

Ad Hoc:

• Mobile Team: Qart
• Mobile Team PM: Adam Kasmier
• FE Engineering: None
• BE Engineering: None
• Design: None
• Content None
• DevOps None
• QA: Therese, Tom, Rachael
• Mobile Teams that are involved: Qart, may need to pull in engineering if need calls for it

[kellylein]

Closing for the end of the contract 12/16/24.