Demo Data users for each component
Refer to demo data readme for more details about user permissions: https://github.com/OpenLMIS/openlmis-referencedata/blob/master/demo-data/README.md
ONLY test with the users "Admin" or "Administrator" when executing test cases related to Administration activities.
When testing Requisitions and External Fulfillment, please use the following usernames listed in the diagram below depending on the :
When testing Vaccine Stock Based Requisitions, Local Fulfillment, CCE, and Stock Management, please use the following usernames listed in the diagram below:
Gliffy | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Requisitions test cases
- All test cases for this label are named 001-100 (to assist in ordering test case execution)
- Labels include: Requisitions
Gadget | ||||
---|---|---|---|---|
|
Test cases that need to be created/updated:
- Editable vs nonread-editable only (when a req should be editable - may update View Req test case or add edge case)Modifying requisition (after submitted and you are an approver making edits, edge case for non-approver who cannot make edits)
Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-4158 Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-4159 - Approved qty = req qty OR calc order qty Role based actions (edge case for who can't delete or reject)qty (updated steps in
)Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2870
Vaccine Stock based requisitions
- All test cases for this label are named 101-110
- Labels include: VaccineSBR
Gadget | ||||
---|---|---|---|---|
|
Stock Management test cases
- All test cases for this label are named 301-350 (to assist in ordering test case execution)
- Labels include: StockManagement
Gadget | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Test cases that need to be created/updated:
Combine test cases to complete a workflow (physical inventory, receipts, issue)When creating an adjustment for a product that has a VVM status (check existing test case, will need updating)- Combine test cases for enabling stock cards to populate requisitions (this is covered by test
Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-4138
Order/Fulfillment test cases
- All test cases for this label are named 201-300 (to assist in ordering test case execution)
- 201-250 are External Fulfillment
- 251-300 are Local Fulfillment
- Labels include: Fulfillment and LocalFulfillment
Gadget | ||||
---|---|---|---|---|
|
Test cases that need to be created/updated:
- When converting an order, compare the requisition to the order and confirm quantities are correct.
- Manage POD (test case should get updated)
- Create a POD from an order (test case should get updated)
- View Orders (test case should get updated)
- Separate workflows for external fulfillment vs local fulfillment
- Convert to order (external fulfillment & local fulfillment should be separate test cases)
- Edge case: convert to order should only show the externally fulfilled orders
CCE test cases
- All test cases for this label are named 351-400 (to assist in ordering test case execution)
Test cases that need to be created/updated: N/A
Gadget | ||||
---|---|---|---|---|
|
Administration test cases
- All Administration test cases for this label are named 401-500 (to assist in ordering test case execution)are not required to be completed in a specific order, and do not have order numbers in their description
Gadget | ||||
---|---|---|---|---|
|
Exploratory Testing on 2/26/18
Test Cycle Name: Exploratory Testing - Team ILL
List the programs and facilities in demo data that support the following scenarios:
- Enable stock on hand for requisitions (happy path - stock cards and unhappy path - no stock cards)
- Requisition and Stock Management tests
- External Fulfillment vs Local Fulfillment
- Convert to order vs auto convert
- Skip Authorization step
Program | Facility | Fulfillment type | Convert to Order |
---|---|---|---|
Family Planning | Comfort Health Clinic | External | Manual - user must convert |
EPI | Cuamba | Local | Automatically converted |
Tests Completed:
Phase 1 Bugs:
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|