Dog Food Day Scenarios

Name
Standard Requisition Workflow

Description
During this scenario we’ll be testing the standard requisition workflow, how it works if nothing unordinary happens.

Users
srmanager1, smanager1, psupervisor, wclerk1, administrator

Story

  1. Storeroom Manager (srmanager1) initiates new requisition for Family Planning program and begins to enter data. During the process his internet connection turns off and he enters the offline mode. He continues to work on entering the data and saves the requisition locally. After a few minutes his internet connection is restored and he reenters the requisition view to submit the requisition. The user logs out.
  2. Store Manager (smanager1) reviews the requisition values. He finds out that one of the values is missing a zero so he updates it, add a comment and authorizes the requisition.

  3. Program Supervisor (psupervisor) reviews the requisition. He finds out that one of values is suspiciously large. He reject requisition with a comment about it, thinking it could be a scam.

  4. Storeroom Manager fixes the value adds a comment about it and submits the requisition again.

  5. Store Manager updates requested quantity explanation(makes a typo) and tries to authorize the requisition but loses internet connection. He waits for the internet connection to come back and proceeds with the authorization.

  6. Administrator (administrator) modifies the template for Family Planning program.

  7. Program Supervisor reviews the requisition and finds a typo in the explanation. He rejects the requisition with a comment asking to fix the typo.

  8. Storeroom Manager submit the requisition.

  9. Store Manager fixes the typo and authorizes the requisition.

  10. Program Supervisor approves the requisition.

  11. Warehouse Clerk convert the requisition to order and prints it.


Name
Robbery

Background
Robbery happened last night, the robbers stole the whole stock of Acetylsalicylic Acid. An emergency requisition must be submitted.

Users
srmanager2, smanager2, dsrmanager, wclerk2

Story

  1. Storeroom Manager (srmanager2) initiates a new emergency requisition for Essential Meds program. He skips all the products except for Acetylsalicylic Acid. He makes a typo in the explanation
  2. Store Manager (smanager2) reviews the requisition values. He finds a typo in the explanation and fixes it, leaves a comment and authorizes the requisition.
  3. District Manager (dsrmanager) reviews the requisition and approves it.
  4. Warehouse Clerk (wclerk2) converts the requisition to orders and prints it.


Name
New employee

Description
During this scenario we’ll be testing the user creation and password reset workflow.

Users
administrator, newuser

Scenario

  1. Administrator creates new user. The new user is prompted to change password after logging in for the first time.
  2. New user logs in and notices that he can’t enter any pages. He complains to the system administrator.
  3. Administrator adds some roles to the newly created user.
  4. New user logs in a some entries on the navigation bar.
  5. New user logs out and reset its password with the forgot password feature.


Name
Cold Chain Equipment Workflow

Description
During this scenario we’ll be testing the cold chain equipment workflow.

Users
administrator, ccemanager, divo

Scenario

  1. CCE Manager (ccemanager) upload an item catalog through the UI.
  2. DIVO adds a couple of freezers, but sets a Voltage Regulator to unknown and make a few typos in the reference names and additional notes.
  3. CCE Manager notices the typos and fixes them. During the process he also finds out that all the fridges have incorrect Voltage Regulator settings and ask the DIVO to fix them.
  4. A few days later four of the fridges run out of fuel and need to have their statuses updated, which is done by the DIVO.
  5. Day later the fuel is delivered and the DIVO can update the fridge statuses.

OpenLMIS: the global initiative for powerful LMIS software