Caseflow: Test attorney-co-located loop with Jed (admin action pilot)

Created on 27 Aug 2018 · 7Comments · Source: department-of-veterans-affairs/caseflow

We've finished developing both the back and front end for the attorney to co-located loop so we'd like to test the whole flow and ensure it updates VACOLS as intended.

Testing changing VACOLS locations
- When attorneys assign admin actions to co-located, VACOLS location changes to CASEFLOW
- When co-located assign translation task to translation, VACOLS location changes to 14
- When co-located assigns schedule hearing task to hearings team, VACOLS location changes to 57
- When co-located places a task on hold, VACOLS location remains CASEFLOW
- When co-located assigns case back to attorney, VACOLS location changes back to attorney's location
Testing assignment back to attorney
- When co-located assigns case back to attorney, attorney's Days waiting counter restarts at zero
Testing VACOLS reports for any empty fields
- Let's look at what Cases charged to - CASEFLOW location - looks like
- When co-located places task on hold, Cases charged to CASEFLOW
- Cases charged to 14
- Cases charged to 57
AMA attorney/co-located loop
- Attorneys cannot select Translation or Schedule hearing tasks for AMA appeals

Test users

CF_KHAN_397 station ID 397: Attorney
CF_KIRK_317 station ID 317: Co-located

caseflow-queue Foxtrot 🦊

Source

laurjpeterson

All 7 comments

Test Plan

[ ] Sign in as CF_KHAN_397 station ID 397.
[ ] https://appeals.cf.preprod.ds.va.gov/queue
[ ] Open the case of WLJ, 2722950.
[ ] Select "add colocated task".
[ ] Select "POA clarification".
[ ] Add instructions "clarify the POA".
[ ] Click Assign Action.
[ ] Refresh the page.
[ ] Confirm that the case isn't in the queue anymore.
[ ] Ask Jed to confirm that the VACOLS location of the case has been changed to "CASEFLOW".
[ ] Ask Jed to run the report to see where case 2093973 is being charged to.
[x] Open the case of NAB, 2704660.
[x] Select "add colocated task".
[x] Select "Translation"
[x] Add instructions "translate".
[x] Click Assign Action.
[x] Refresh the page.
[x] Confirm that the case isn't in the queue anymore.
[x] Open the case of NB, 1556671.
[x] Select "add colocated task".
[x] Select "Schedule Hearing"
[x] Add instructions "schedule it".
[x] Click Assign Action.
[x] Refresh the page.
[x] Confirm that the case isn't in the queue anymore.
[x] https://appeals.cf.preprod.ds.va.gov/test/users
[x] Log in as CF_KIRK_317 station ID 317.
[x] https://appeals.cf.preprod.ds.va.gov/queue
[ ] Open the case of WLJ, 2722950.
[ ] Place the case on hold for 30 days.
[ ] Confirm that the case now appears on the on-hold tab.
[ ] Ask Jed to confirm that the case is still at the location "CASEFLOW".
[ ] Send the case back to CF_KHAN_397.
[ ] Refresh the page.
[ ] Confirm that the case has disappeared from Kirk's queue.
[ ] Ask Jed to confirm that the case is now assigned to CF_KHAN_397.
[x] Open the case of NAB, 2704660.
[x] Select "Send to Translation team".
[x] "Send case".
[x] Refresh the page.
[x] Confirm that the case has disappeared from Kirk's queue.
[x] Ask Jed to confirm that the VACOLS location of the case has been changed to 14.
[x] Ask Jed to run the report to see where the case is being charged to.
[x] Open the case of NB, 1556671.
[x] Select "Send to Schedule hearing team".
[x] "Send case".
[x] Refresh the page.
[x] Confirm that the case has disappeared from Kirk's queue.
[x] Ask Jed to confirm that the VACOLS location of the case has been changed to 57.
[x] Ask Jed to run the report to see where the case is being charged to.
[ ] https://appeals.cf.preprod.ds.va.gov/test/users
[ ] Sign in as CF_KHAN_397.
[ ] Confirm that the task reappears in CF_KHAN_397's queue.

Setup

RequestStore.store[:current_user] = User.find_by(css_id: "CF_KHAN_397")
assignee = VACOLS::Staff.find_by(sdomainid: "CF_KHAN_397").slogid
AppealRepository.update_location!(LegacyAppeal.find_by(vacols_id: "2704660"), assignee)
AppealRepository.update_location!(LegacyAppeal.find_by(vacols_id: "1556671"), assignee)

evankroske on 28 Aug 2018

Testing mostly passed! We discovered an issue with the test data of case WLJ, 2722950, so we used NAB, 2704660, to test on hold instead. We haven't yet tested assignment back to attorney.

evankroske on 5 Sep 2018

👍1

I figured out what was wrong with 2722950. It had been assigned back to the attorney using an old version of the code which had assigned the task itself to the attorney instead of marking it complete. I deleted the runaway task and manually assigned the case back to the attorney.

I then tested this manually:

Confirm that the bfcurloc of the case is APADOLL.
Add a colocated task to the case.
Confirm that the bfcurloc of the case is now CASEFLOW.
As a colocated admin, assigned the case back to attorney.
Confirm that the bfcurloc of the case is now APADOLL.

I think that this testing is sufficient. Testing passed!

evankroske on 5 Sep 2018

👍1

Thanks @evankroske! Were you able to check VACOLS reports with Jed as well? I see a few steps to Ask Jed to run the report to see where the case is being charged to. but am curious to know if there were any empty fields on that report (so we can determine if they'd be concerning to users and stakeholders, even though they're bought into our approach).

Testing VACOLS reports for any empty fields:

Let's look at what Cases charged to - CASEFLOW location - looks like
When co-located places task on hold, Cases charged to CASEFLOW
Cases charged to 14
Cases charged to 57

Did we also confirm that when the case was assigned back to the attorney, the days waiting counter restarted at 0 in the attorney's queue?

Low priority note:

This came up in user research session today: an attorney noticed that when co-located was the most recent person to assign her the case, upon attorney check out, Caseflow/VACOLS/the IDT auto-populated the co-located user as the judge to send the case to instead of the judge who assigned her the case. I think we can wait to see what happens here during the pilot, because attorneys have the workaround to choose another judge.

laurjpeterson on 6 Sep 2018

@dannysellers - can we run through this test locally?

When the case was assigned back to the attorney, the days waiting counter restarted at 0 in the attorney's queue?

laurjpeterson on 6 Sep 2018

@laurjpeterson Confirmed!

gif

dannysellers on 6 Sep 2018

👍1

[x] Attorney’s on-hold tasks don’t show up in the queue
[x] When attorney assigns an AMA colocated admin task to a user, attorney’s task becomes on hold. A new colocated task is created with a parent ID of the attorney task.
[x] When attorney assigns a legacy colocated admin task to a user, attorney’s task becomes on hold. A new colocated task is created without a parent ID of the attorney task.
[x] A colocated user should see all non-completed tasks in their queue with statuses (assigned, in_progress, on_hold)
[x] If it is a hearing schedule or translation for an AMA task, a colocated user can only do two things: assign back to attorney and place on hold.
[x] If it is a hearing schedule or translation for a legacy task, a colocated user can only do two things: send to the team and place on hold.
[x] When a colocated sends back an AMA task to attorney, colocated task should become completed and attorney’s task must become assigned and assigned at should reset.
[x] When a colocated sends back a legacy task to attorney, colocated task should become completed and attorney’s task must be assigned to attorney’s location and must show up in attorney’s queue.