3.3 Release Test Plan update tracking

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 :

Open

When testing Vaccine Stock Based Requisitions, Local Fulfillment, CCE, and Stock Management, please use the following usernames listed in the diagram below:

Requisitions test cases

• All test cases for this label are named 001-100 (to assist in ordering test case execution)

• Labels include: Requisitions

Test cases that need to be created/updated:

1. Editable vs read-only (when a req should be editable - may update View Req test case or add edge case) https://openlmis.atlassian.net/browse/OLMIS-4158 https://openlmis.atlassian.net/browse/OLMIS-4159

2. Approved qty = req qty OR calc order qty (updated steps in https://openlmis.atlassian.net/browse/OLMIS-2870)

Vaccine Stock based requisitions

• All test cases for this label are named 101-110

• Labels include: VaccineSBR

Stock Management test cases

• All test cases for this label are named 301-350 (to assist in ordering test case execution)

• Labels include: StockManagement

Test cases that need to be created/updated:

1. Combine test cases to complete a workflow (physical inventory, receipts, issue)

2. Combine test cases for enabling stock cards to populate requisitions (this is covered by test https://openlmis.atlassian.net/browse/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

Test cases that need to be created/updated:

1. When converting an order, compare the requisition to the order and confirm quantities are correct.

2. Manage POD (test case should get updated)

3. Create a POD from an order (test case should get updated)

4. View Orders (test case should get updated)

5. Separate workflows for external fulfillment vs local fulfillment

6. Convert to order (external fulfillment & local fulfillment should be separate test cases)

7. 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

Administration test cases

• Administration test cases are not required to be completed in a specific order, and do not have order numbers in their description

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

Tests Completed: