Project Status Overview

Project Objective:

Implement the ability to perform automated testing within individual features instead of having to run it for the entire app
Educate and train engineering how adding and updating detox test when code changes vs waiting for QA to do it

Current Dependencies / Blockers

Blockers

|Blocker | Team / Owner | Est to Resolution | |-------|---------|-------| | Internal dependency | Internal PR review had been waiting for approval for week | Following up 4/16 on how to close out this process | | Internal dependency | Engineers prioritizing this work | Completed - Tim said engineers will do this work once feature is complete, stable and they are trained | | External dependency ? | | | | |

Project Timeline

Milestones

|Step | Timing | |-------| ---------| | Implement separate feature detox testing | | | Create documentation on how this works | | | Determine what engineers will and won't do and when | | | Develop onboarding materials so that engineers learn how to do this | | | Rollout responsibility change in having engineers handle this | | | Determine how to oversee rollout and maintain engineers completing this task | |

Monthly Update for Stakeholders

Updates

|Month| Project Health | Progress & Key Accomplishments| Issues/Risks/Blockers| |-------| ---------|--------|---------| |Month Year | |Month Year| ..... |Month Year| |Month Year|

Detailed Project Scope

Problem Statement

Currently Automated Testing through the Detox Tool can only be run for the entire app, meaning if a change is made to a specific feature it has to be run for the whole app vs a specific piece of the app. This leads wasted time in running the detox because people are waiting on it testing items that are not warranted.
QA was told if we can get Detox to run for specific feature, then can have frontend engineering on the various mobile teams be responsible for creating or updating detox tests that align with the code changes they are making vs having only QA do it
Doing so will save time and effort and reduce the risks of errors

Assumptions

Assumptions that need to be true for this project

1.) Mobile Manager of Engineering still wants to have frontend do this work 2.) Frontend engineers can perform this work, can be trained, and routinely do this work 3.)

Risks

Risks identified and accepted by stakeholders

1.) FE will push back and not do the work or routinely forget 2.) 3.)

Definition of Done

Conditions that must be true in order to consider this project completed

|Item | Completed | |-------| ---------| | Implement separate feature detox testing | | | Create documentation on how this works | | | Determine what engineers will and won't do and when | | | Develop onboarding materials so that engineers learn how to do this | | | Rollout responsibility change in having engineers handle this | | | Determine how to oversee rollout and maintain engineers completing this task | |

Project Scope

Items in and out of scope

|In Scope | Out of Scope| |-------| ---------| | | | | | |

Important Project Links

Links

- Github Epic - Github VA Mobile Page - - Product Brief - Product Canvas - Design - Discovery - Mockups - Final Design - Figma File - Research - Research Plan - Research Results and Findings -Analytics -Decision Log

Team Members

Contact List

**VA:** - **Mobile OCTO Product Leads:** Rachel Han or Ryan Thurlwell - **VA OCTO Product Leads:** - **External Team 1 & Role:** - **External Team 1 & Role:** **Ad Hoc:** - **Mobile Team**: Global, Health and Benefits, Design System, QA, API - **Mobile Team Lead:** - **FE Engineering:** - **BE Engineering:** - **Design:** - **Content** - **QA:** - **Mobile Teams that are involved:** Global, Health and Benefits, Design System, QA, API

Questions

Open Questions

- How are we measuring success? - What is MVP and what is out of scope? - Has there been existing research or work done on this project before? - Is this work being done within the VA today (ex. web)

Closed Questions

| Question | Answer | Owner | |--------|----------|------| | | | | | | | |

Change / Decision Log

Product will need to create on in the Github folder and link it here.

department-of-veterans-affairs / va-mobile-app

Automated (Detox) Testing - Implement Separate Feature Testing #8372