Purpose

OpenLMIS global version 3.0 was released on February 28, 2017. Malawi will be the first country to implement the newly released version 3.0 to replace the current logistics management information system, Supply Chain Manager (SCMgr). As such, testing with a group of core users (see appendix A) was conducted on March 2, 2017 to validate the core features of global OpenLMIS 3.0 against the features and processes currently supported by Supply Chain Manager. Additionally, the testing aimed to identify and document any gaps in OpenLMIS 3.0's features compared to SCMgr, bugs in OpenLMIS 3.0, and/or specific changes or customizations required for Malawi.

...

Global validation testing focused on testing the requisition process.

In Scope

Based on the processes currently supported by SCMgr, the testing scenarios cover the following functionalities:

• Creating and submitting a regular type requisition
  1. Adding comments
  2. Check validations
• Authorizing a requisition
• Approving a requisition
• Rejecting a requisition
• Converting a requisition to an order
• View a list of requisitions
• Reference UI

Out of Scope

• • Reports
  • Notifications
  • Configuration
  • Malawi-specific reference data
  • Malawi-specific UI

Test Environment & Tools

The testing session took place in the Chemonics office and was conducted using the global UAT instance configured with demo reference data and default settings. No Malawi-specific configuration, set up, or UI were completed for this testing session. Testers used their own computers or were provided computers by the Chemonics team. Testing instructions with credentials, testing steps, and space to record results were printed and provided to the testers.

...

Test cases planned vs. executed and passed vs. failed

*Includes all testing steps that were identified as failed by any participant, excluding than configuration issues

Defects identified and their Status & Severity

Defects Distribution

Lessons Learned

• There were insufficient logins and available requisition periods for the number of users included in the testing, preventing users from initially completing some testing steps (such as submitting or authorizing a requisition) since another user, signed in with the same credentials, had already performed the same action. This issue was resolved by having users start testing sequentially, to ensure that each user was working on a different period that would remain available to them.
• Login issues were prevalent due to the very fast auto-logout setting. Users were required to sign in repeatedly in order to complete the testing. This could not be changed at the time of testing, but was noted for future testing.
• Though the global version was purposefully not configured with Malawi-specific information, and this was explained to the testers, it did still create confusion and cause questions or issues for users that were configuration-related.

...

• Skip functionality
  • The skip feature was a point of confusion for several users. Difficulty was reported distinguishing between skipping individual products

    Jira Legacy
    showSummary false server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2082

    (with the checkboxes) and the skip button for skipping a requisition. The button is more prominent and many users first tried to skip the period when trying to skip a product.
  • The skip button to skip a requisition was available even for users not authorized to skip a period 

    Jira Legacy
    server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2067

• User profile
  • When accessed, the profile had labels for user related information, but did not contain any of the user's information. 

    Jira Legacy
    server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2060

• Field required box did not disappear
  • One user received the "field required" error for a field, which remained on the screen (not attached to the field) even after entering a value.
• Total requisition cost
  • Most fields on the requisition have an info button that will provide the user with information on what the field is, what it means, and/or how it should be calculated. The total cost of the requisition does not, and the calculation it is using was not clear and confusing to some users. Many users might confuse the dispensing unit as the pack size, and think the calculation was not working properly.

    Jira Legacy
    showSummary false server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2059

...

Appendix A. Testing Participants

Appendix B. Global OpenLMIS v3.0 Testing Instructions

...