Create a test case for editing from Review & Submit page

[pacerwow]

Issue Description

As an DBEX product team member, I need to make sure that the Veteran can easily change the details of their application from the Review & Submit screen without error so that they feel satisfied when the form is submitted with the correct information. Additionally, a "correct" submission means that the Veteran's claim won't be incorrectly labeled as BDD, which may impact their ability to receive disability compensation benefits in a timely manner and without frustration.

---

Tasks

• [ ] What work is necessary for this story to be completed?

Acceptance Criteria

• [ ] Given a test case doesn't exist for testing edits from the Review & Submit page
• [ ] And Veterans expect to be able to edit and save changes the make to their application
• [ ] Then a test case should exist to ensure this feature works as expected for the Veteran
• [ ] And it should cover the possible changes a Veteran could make from this page
• [ ] And be tested by the team to ensure the feature's functionality meets the Veteran's expectation that VA has set

Additional Context & Information

Do we want to begin with just POW, Terminally Ill, Housing? What could we include? Exclude? What types of changes will trigger conditional more complex workflows? Maybe we can exclude just these until a later date?

---

How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[pacerwow]

If doing this as one ticket is too large, I need guidance from the team on how to break up this work. I made a suggestion in Slack, please lmk what you decide.

[pacerwow]

Action Items:

1. @aurora-a-k-a-lightning would you be able to work with the team to verify if we have automated testing that tests the functionality of this feature (editing from the Review & Submit page)? Keep the effort light.

2. @pacerwow to write a series of stories that integrate manual UI testing into the existing Test Rail test cases. Pacerwow will segment these stories by form section; Veteran Details, Disabilities, PTSD, Supporting Evidence, Additional Information, and Review. Pacerwow will integrate these into the existing test cases we have for Minimal, BDD, POW, FCD, Toxic Exposure, Housing, etc. Pacerwow to find out what test cases Conditions team and Carbs has.

3. What about 0781? How much of this coverage is valuable? How will we handle conditional form flows?