# Change History

[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 -> page it reappears.
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:!
### 1
1. Description of issue -> Informational banner displaying incorrect text.
2. Expected result (what **should've** occurred) -> Banner should likely state "Establish" to match the button text
3. Actual result (what **did** occur) -> Informational banner displaying "Save" even though button is displaying "Establish"
4. Steps to reproduce
5. Severity (**low**: minimal/non-blocking, **medium**: potentially blocking, **high**: significant blocker/work stoppage) -> **low**
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:

### 2
1. Description of issue -> When withdrawing an issue, and all decision dates are entered the edit issues page shows the save button instead of the establish hlr/sc button
2. Expected result (what **should've** occurred) -> The save button should have switched to the Establish Higher Level Review button
3. Actual result (what **did** occur) - The establish hlr button was a save button
4. Steps to reproduce
- Navigate to the the incomplete tasks tab in the decision review queue
- Select the select actions dropdown next to an issue
- Select withdraw issue
- Navigate to the bottom of the page, button reads "save" instead of "Establish Higher Level Review"
6. Severity **low**
7. 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:!

### 3
1. Description of issue -> page it reappears.
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:!

## Possible fixes needed

Tech-debt issue:

## USERS

| Tester | USER ID | Scenario | VET ID |Pass/Fail |
| -------- | ------- | -------- | ------- | ---- |
| Tyler | CF_Q_283 |all | 700032764 | Pass |
| Sean | CF_WORF_283 |all | 666045047 | Pass |
| Brandon | CF_KIRK_283 |all | 666044727 | |
| Oluchi | 373MCINTOSH_A_CFLW|all | 700032042 | PASS |
| Alec | CASEFLOW_283 |all | 700060379 | |
| Faraz | CF_KIRK_317 |all | 666045251 | |

extra ids: 987654613, 666045250, 456978269, 561349914, 612301365, 700032667
extra users: CASEFLOW_317 [317], DUCHENE_W_RVSR [373], VBAWASGORDOJ [328],
## Scenarios

## User generates a Event/Action report
1. Sign in as your assigned user
2. Navigate to https://appeals.cf.uat.ds.va.gov/decision_reviews/vha/
3. Press the Generate Task Report button
4. Verify that the screen has moved into report generation page
5. Select Event/Action from the Report type drop down
6. All Events/Action should be autoselected
7. Under the Timing Specification in the Range drop down selector select "None" from the drop down
8. In Conditions click add condition till the button is greyed out
9. For each condition select the follow the following options
10. Variable Personnel and VHA member "Placeholder"
11. Variable Days Waiting and in Time range select "More than" from the time range and enter 0 in number of days
12. Variable Decision Review type tick the HLR box and the SC box
13. Variable Issue type
14. Variable Issue Disspostion
15. Click the Generate button in the bottom righter
16. Verify that a CSV is generated and downloaded automaticall
17. Verify contents of CSV matches the content that was chosen

## User generates a Status report
1. Sign in as your assigned user
2. Navigate to https://appeals.cf.uat.ds.va.gov/decision_reviews/vha/
3. Press the Generate Task Report button
4. Verify that the screen has moved into report generation page
5. Select Status from the Report type drop down
6. All Statues should be autoselected as a radio button
7. Under Select type of status report the Last Action Taken radio button should be selected
8. Under the Timing Specification in the Range drop down selector select "None" from the drop down
9. In Conditions click add condition till the button is greyed out
10. For each condition select the follow the following options
11. Variable Personnel and VHA member "Placeholder"
12. Variable Days Waiting and in Time range select "More than" from the time range and enter 0 in number of days
13. Variable Decision Review type tick the HLR box and the SC box
14. Variable Issue type
15. Variable Issue Disspostion
16. Click the Generate button in the bottom righter
17. Verify that a CSV is generated and downloaded automaticall
18. Verify contents of CSV matches the content that was chosen