---
# System prepended metadata

title: '[APPEALS-9182](https://vajira.max.gov/browse/APPEALS-9182) Pre-docket uniformity dogfooding'

---

# [APPEALS-9182](https://vajira.max.gov/browse/APPEALS-9182) Pre-docket uniformity dogfooding
The purpose of [dogfooding](https://deviq.com/practices/dogfooding) is to run through as many relevant user scenarios as possible. Ideally, the individual scenarios work perfectly as intended. The reason it's important that we go through this process is to ensure the feature is ready for production. The purpose of internal testing is to identify potential gaps or defects so that items can be resolved prior to release.
## Capturing deficiencies
It's best that we document any issues that we discover in as much of a uniform standard as possible so that upon later review, we're able to parse the individual instances as easily as possible for potential translation to tech debt/tech improvement Jira tickets. </br>
Here's the template that we've decided to use for this session.  So the goal is to fill it our for each individual discovery as throroughly as possible to capture the maximum amount of information on the particular issue:
1. Description of issue
2. Expected result (what **should've** occurred)
3. Actual result (what **did** occur)
4. Steps to reproduce
5. Severity (**low**: minimal/non-blocking, **medium**: potentially blocking, **high**: significant blocker/work stoppage)
5. Relevant screenshot(s)
    * screenshots are easy to add to hackMD, simply capture the shot you want on your machine, then drag and drop it into the doc like so:![](https://i.imgur.com/BMGvEp7.png)

## ISSUE 1 - Not an Issue
1. Description of issue: Modal text does not match
2. Expected result (what **should've** occurred): Modal text should read "Please select where the documents for this appeal are stored"
3. Actual result (what **did** occur): Modal reads "Please select where the documents for this appeal were returned"
4. Steps to reproduce: Log in as a VISN user > select a case > task action drop down > Documents ready for VHA Program Office team Review
5. Severity (**low**: minimal/non-blocking, **medium**: potentially blocking, **high**: significant blocker/work stoppage): low
5. Relevant screenshot(s):
![](https://i.imgur.com/c26x3t8.png)

    
## ISSUE 2 - Not an Issue 
1. Description of issue: Modal text does not match
2. Expected result (what **should've** occurred): Modal text should read "This appeal will be sent to VHA Progran Office for review."
3. Actual result (what **did** occur): Actually reads "This appeal will be sent to VHA CAMO for review."
4. Steps to reproduce: Sign in as VHAPOUSER -> Navigate to VHA Program Office Queue (Community Care POM) -> Navigate to case details page for an appeal -> Select “Documents ready for VHA CAMO team review” in task action drop down
5. Severity (**low**: minimal/non-blocking, **medium**: potentially blocking, **high**: significant blocker/work stoppage): low
5. Relevant screenshot(s)
![](https://i.imgur.com/GnMlSdO.png)

## ISSUE 3
1. Description of issue
Expected messaging for Education in Scenario 1 not received
2. Expected result (what **should've** occurred)
Receive "Appeal recorded and sent to Education for document assessment" messaging when selection Education benefit type
3. Actual result (what **did** occur)
Received "Appeal recorded in pre-docket queue" instead when selecting pre-docketing
4. Steps to reproduce
Run through scenario 1 steps
5. Severity (**low**: minimal/non-blocking, **medium**: potentially blocking, **high**: significant blocker/work stoppage)
Low?
6. Relevant screenshot(s)
![](https://i.imgur.com/vKvkF0l.png)


## ISSUE 4
1. Description of issue
2. Expected result (what **should've** occurred)
3. Actual result (what **did** occur)
4. Steps to reproduce
5. Severity (**low**: minimal/non-blocking, **medium**: potentially blocking, **high**: significant blocker/work stoppage)
5. Relevant screenshot(s)

## TESTERS

| Tester    | Pass/FAIL|
| --------  | -------- | 
| 1.Jay     |          |          
| 2.Craig   | PASS     |          
| 3.Oluchi  | PASS     |          
| 4.Heather | PASS     |          
| 5.Lianna  | PASS     |          
| 6.Clay    | PASS     |          
| 7.Heather | PASS     |          
| 8.Clay    | PASS     |          
| 9.Emily   | PASS     |          
| 10.Prajwal| PASS     |          
| 11.Faraz  |   Pass   |          
| 12.Sean   |   PASS   | 
| 13.Tyler  |   PASS   | 


## Cases (Veteran ID will be provided after data staging)
## APPEALS-9413 410000010, 410000011, 410000012
* Test Scenario 1 - Verify pre-docket confirmation screen uniformity for each business line 
1. Sign in as a BVAI Intake user ex: BVAISHAW
2. Navigate to mail intake page (caseflowdemo.com/intake)
3. Select Decision Review Request: Board Appeal (Notice of Disagreement) — VA Form 10182 from drop down 
4. Search a Vet ID
5. Fill out required fields and press enter 
6. Select "Add Issue" button 
7. Select benefit type Veterans Health Admin 
8. Select one of the 4 caregiver issues 
9. Fill out remaining required fields 
10. Submit appeal 
11. Verify success title states "Appeal recorded and sent to VHA Caregiver for document assessment"
12. Repeat steps 2-7
13. Select any issues that is not one of the 4 caregiver issues 
14. Fill out remaining required fields and submit appeal
15. Verify success title states "Appeal recorded and sent to VHA CAMO for document assessment"
16. Repear steps 2-6
17. Select benefit type Education 
18. Fill out remaining required fields and submit appeal 
19. Verify success title states "Appeal recorded and sent to Education for document assessment"

## APPEALS-9206 (Need appeal in VHA PO) 000100001
* Test Scenario 2 - Verify Ready for Review Radio Field Label Uniformity in VHA PO
1. Sign in as a VHA PO user ex: VHAPOUSER
2. Navigate to VHA Program Office Queue (Community Care POM) 
3. Navigate to case details page for an appeal 
4. Select "Documents ready for VHA CAMO team review" in task action drop down 
5. Verify modal text states "This appeal will be sent to VHA Progran Office for review. Please select where the documents for this appeal are stored"
6. Verify modal matches design 

## APPEALS-9206 (Need Appeal in VISN Office NY) 000100002
* Test Scenario 3 - Verify Ready for Review Radio Field Label Uniformity in VISN
1. Sign in as Regional Office User ex: VISNUSER
2. Navigate to the queue for NY/NJ Office 
3. Navigate to case details page for appeal
4. Verify In the task action dropdown the task action, "Return to VHA Program Office team" exists and select "Documents ready for VHA Program Office team review"
5. Verify modal text states "This appeal will be sent to VHA Progran Office for review. Please select where the documents for this appeal are stored" 
6. Verify modal matches design 


## APPEALS-9156 (Create Appeal in Caregiver queue) 000100003
* Test Scenario 4 - Verify "Mark task in progress" Task Action labels standardization
1. Sign in as a CSP user ex: CAREGIVERUSER
2. Navigate to caregiver queue, unassigned tab
3. Select task action dropdown and verify option says "Mark task in progress"
4. Select Mark task in progress option and verify modal button states "Mark in progress"

## APPEALS-9143 (Create Appeal in VHA PO) 000100004
* Test Scenario 5 - Verify VHA PO Queue Tab Titles 
1. Sign in as VHA PO user ex:VHAPOUSER
2. Navigate to VHA PO Member Services Health Eligibility Center queue
3. Take note of number next to On hold tab ex: "On Hold (1)" AND take note of the number next to the Ready for Review tab ex: "Ready for Review (0)"
4. Navigate to case details page of appeals 
5. Select Assign to VISN/VA Medical Center from Task Action dropdown
6. Assign appeal to NY/NJ VA Health Care Network and submit the appeal 
7. Verify the On Hold tabs number has increased by 1 ex "On Hold (2)"
8. Sign in as VISN User ex: VISNUSER
9. Navigate to VISN QUEUE NY/NJ VA Health Care Network, and to the case details page of the appeal sent over from VHA PO 
10. Select Ready for review from the dropdown and submit the appeal back to VHA PO 
11. Sign in as a VHA PO User 
12. Navigate to the VHA PO queue 
13. Verify the "Ready for Review tab" number has increased by 1 ex: "Ready for Review (2)"

## APPEALS-9109
* Test Scenario 6 - Verify BVA Intakes Completed Tab Description
1. Sign in as BVA Intake user ex: BVAISHAW
2. Navigate to BVA Intake queue 
3. Go to completed tab 
4. Verify the tab description reads "Cases Completed"

## APPEALS-9231 (Create Appeal in VHA CSP queue and VHA CAMO) CSP = 000100007 CAMO = 090330030
* Test Scenario 7 - Verify Placement of Alert Banners Used in Pre-Docket Workflows
1. Sign in as a CSP User ex: CAREGIVERUSER 
2. Navigate to organization queue page (CSP)
3. Select the appeal and navigate to case details page 
4. Select Mark task in progress in task action dropdown 
5. Select Mark in progress on modal 
6. Verify the success banner is above the queue segment and below the page header. 
7. Sign in as a VHA CAMO user ex: CAMOUSER
8. Repeat steps 2-5 
9. Verify the success banner is above the queue segment and below the page header.

## APPEALS-9105 
* Test Scenario 8 - Verify VHA CAMO Assigned Tab Description 
1. Sign in as VHA CAMO user ex: CAMOUSER 
2. Navigate to VHA CAMO queue 
3. Navigated to Assigned tab
4. Verify tab's description states "Cases assigned to VHA CAMO"

## APPEALS-9106
* Test Scenario 9 - Verify Education RPO Completed Tab Description 
1. Sign in as Education Regional Processing Office user ex: EDURPOUSER
2. Navigate to the organization queue for any of the RPOs
3. Navigate to completed tab 
4. Verify the description states "Cases completed (last 7 days):"

## APPEALS-9100
* Test Scenario 10 - Verify BVA Intake's "Return appeal to VHA" to "Return appeal to VHA CAMO"
1. Sign in as Intake user ex: BVAISHAW 
2. Navigate to organization queue
3. Navigate to assigned tab 
4. Select appeal and navigate to case details page 
5. Select Task dropdown
6. Verify "Return to VHA CAMO" options exists 
7. Select "Return to VHA CAMO"
8. Verify Modal appears and states 
* The title is: "Return to VHA CAMO" The description text is: "If you are unable to docket this appeal due to insufficient documentation, you may return this to VHA CAMO."
9. Enter required fields and submit 
10. Verify success banner states "You have successfully returned <appellant's name>'s case to VHA CAMO"

## Appeals-9150 & 9281 (eduemo 090330020, 090330018, 090330016, 090330014, 090330012 and VHAcamo 090330022, 090330024, 090330026, 090330028)
* Test Scenario 11 - Verify Task Action Modal button standardization (Return)
* While going through these modals verify the following as well 
* The buttons should be solid blue with the font color being white
* The buttons should have a hover effect
1. Swap to a CAMO user. There is one with the cssid of CAMOUSER. Navigate to the Camo organization queue.
2. Select one of the created appeals and go to the details page.
3. Select the Send to Board Intake task action and verify the button text is "Send"
4. Send one of the appeals back to intake for later testing
5. Select the Assign to Program Office task action and verify the button text is "Assign"
6. Send a task/appeal to a program office of your choosing, note it #Beneficiary Tr
7. Switch to a program office user VHAPOUSER is the css id and navigate to the program office queue that you sent the appeal to
8. Select that appeal and go to the details page
9. Select the Ready for Review task action and verify the button text is "Send"
10. Select the Assign to VISN task action and verify the button text is "Assign"
11. Select the Return to Camo team task action and verify the button text is "Return"
12. Select the Mark task in progress task action and verify the button text is "Mark in progress"
13. Select the Put task on hold task action and verify the button text is "Put task on hold"
14. Place the task on hold
15. Select the End hold early task action and verify the button text is "End hold"
16. Switch to an emo user the css id is EMOUSER
17. Select an appeal and go to the details page
18. Select the Assign to regional processing office task action and verify the button text is "Assign"
19. Send an appeal to an office of your choosing for po testing and select a new appeal
20. Select the Return to board intake task action and verify the button text is "Return"
21. Send a task back to intake for later testing and select a new appeal
22. Select the Ready for review task action and verify the button text is "Send"
23. Swap to an edu rpo user the css id is EDURPOUSER
24. Go to the program office queue you sent the earlier appeal to
25. Select the appeal and go to the case details page
26. Select the Return to Executive Management Office task action and verify the button text is "Return"
27. Select the Ready for Review task action and verify the the button text is "Send"
28. Select the mark task in progress task action and verify the button text is "Mark in progress"
29. Swap to a BVA intake user css id is BVAISHAW
30. Navigate to the queue, go to the review tab and select the appeal returned from Camo
31. Select the Docket Appeal task action and verify the button text is "Confirm" ? unsure about this one
32. Select the Return appeal to VHA task action and verify the button text is "Return"
33. Navigate back to the queue, go to the review tab, and select the appeal returned from Emo
34. Select the Return appeal to Education Service task action and verify the button text is "Return"

## APPEALS - 9110 (Create Appeal in VHAPO 000100031, CSP 000100030, EMO 000100033, EDU RPO 000100032)
* Test Scenario 12 - Verify standardization of ready for review modal buttons and labels 
1. Sign in to VHAPOUSER
2. Navigate to organizations queue page and find the appeal 
3. Navigate to case details page 
4. Select the task action dropdown 
5. Verify the following option is in the actions dropdown: "Documents ready for CAMO team review"
5. Click on "Documents ready for VHA CAMO review". Verify A modal appears.
6. Verify modal's title states "Ready for review"
7. The submission button states "Send"
8. Sign in to EMOUSER
9. Navigate to EMO queue page
10. Select the appeal mentioned above 
11. Verify the following option is in the the dropdown "Documents ready for Board Intake review"
12. Click on "Documents ready for Board Intake review" a modal should appear 
13. Verify modal title states "Ready for review" and submission button states "Send"
14. Sign in as EDURPOUSER
15. Navigate to the queue page for Buffalo RPO 
16. Select the appeal mention above 
17. Verify the following option is in the the dropdown "Documents ready for Board Intake review"
18. Click on "Documents ready for Board Intake review" a modal should appear 
19. Verify modal title states "Ready for review" and submission button states "Send"
20. Sign in CAREGIVERUSER
21. Navigate to the caregiver queue page 
22. Select the appeal mention above 
23. Verify the following option is in the the dropdown "Documents ready for Board Intake review"
24. Click on "Documents ready for Board Intake review" a modal should appear 
25. Verify modal title states "Ready for review" and submission button states "Send"


## Appeals - 9155 (CAMO 090330038, 090330040, 090330036 )(EMO 090330004, 090330006, 090330008)
* Test Scenario 13 - Verify standardization of modal text areas 
1. Sign in to CAMO user ex: CAMOUSER 
2. Navigate to organization queue 
3. Select an appeal and navigate to case details page 
4. Select Send to Board Intake from task action dropdown and verify there is no colon next to text area label. 
5. Verify Modal matches [design](https://https://github.com/department-of-veterans-affairs/caseflow/pull/17493)
6. Fill out modal and send to intake 
7. Select a new appeal and select the Assign to Program Office task action and verify the colon is gone from the text area label. Also verify the change in the dropdown label change and spacing. Also verify the text field is marked as optional
8. Send appeal to PO office (note the PO office here: )
9. Sign in as VHAPOUSER
10. Navigate to organization queue for PO office that the appeal was sent to
11. Select appeal and navigate to case details page 
12. Select the Documents ready for vha camo team review task action and verify the colon is gone from the text area label and that the spacing is correct for the other fields and other text box
13. Select the Assign to VISN task action and verify the colon is gone from the text area label also verify the dropdown label and spacing
14. Select the Return to Camo team task action and verify the colon is gone from the text area label
15. Select the Put task on hold task action and verify the colon is gone from the text area label. Also select the custom field and verify the spacing is correct.
16. Sign in as an EMOUSER
17. Navigate to organization queue 
18. Select appeal and navigate to case details page 
19. Select the Assign to Program Office task action and verify the colon is gone from the text area label. Also verify the change in the dropdown label change and spacing. Also verify the text area is marked as optional.
20. Send the appeal to a Program office 
21. Select a new appeal 
22. Select the Return to board intake task action and verify the colon is gone from the text area label
23. Send appeal back to intake for later testing and select a new appeal
24. Select the Ready for review task action and verify the colon is gone from the text area label and that the spacing is correct for the other fields and other text box.
25. Sign is as EDURPOUSER
26. Go to the program office queue you sent the earlier appeal to
27. Select the appeal and go to the case details page
28. Select the Return to Executive Management Office task action and verify the colon is gone from the text area label 
29. Select the Ready for Review task action and verify the colon is gone from the text area label and that the spacing is correct for the other fields and other text box.
30. Sign in as BVAISHAW
31. Navigate to the queue, go to the review tab and select the appeal returned from Camo
32. Select the Docket Appeal task action and verify the colon is gone from the text area label
33. Select the Return appeal to VHA task action and verify the colon is gone from the text area label
34. Navigate back to the queue, go to the review tab, and select the appeal returned from Emo
35. Select the Return appeal to Education Service task action and verify the colon is gone from the text area label