Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »




Working draft to complete on 5/19/17 OLMIS-2540 - Getting issue details... STATUS



Table of Contents

Please log all bugs PRIOR to mmddyy at 11:00am Pacific

Instructions

  1. Install JIRA Capture (see instructions below)
  2. Review the current state of the software test scope, and test roles for context
  3. Sign up for the test scrips you plan to do, by linking your name (typing '@' and your name) in the "Tester" column
  4. Login and start testing the system
  5. When a test fails, please log bugs using JIRA Capture and the OpenLMIS pre-3.0 UAT template 
    1. Example bug logged, here.
  6. Update the table below with your results (pass/fail) and associated bugs logged


JIRA Capture is a way to screenshot the page you are viewing in your browser where you can comment directly and log 'bugs' within JIRA easily. 

Install JIRA Capture

  • Install the JIRA Capture chrome plug-in : LINK and a great instructional video of how to install it here.
  • Enter in the JIRA URL as https://openlmis.atlassian.net 
  • Enter your JIRA/Atlassian username without the email part, for example my username is maryjo.kochendorfer
  • Enter your JIRA/Atlassian password
  • Look at the template tab (see screen shot) and expand the "SHARED" section
  • Select the template called "OpenLMIS pre-3.0 UAT" under shared and 'favorite' it. This template already has the appropriate label, epic and other parameters selected for us to track the bugs against this exercise.
  • Go to "issues" and create a new one, then select the template
  • Select "bug" as the issue type. Input the "Summary" Field and the "Description" field. The rest should be populated by the template. Example here.



Current state of software

Please review the following so you have an understand what work is currently underway or scheduled for the last sprint. There is quite a bit of information so we anticipate folks will log duplicate bugs but ideally we hope to minimize how many by providing you with the scope and current list of bugs.

Out of scope

Look and Feel

  • Please review current outstanding bugs here so that you aren't logging bugs already identified

Test Scope

The scope of this preliminary acceptance testing is to test the current state of functionalities of OpenLMIS version 3 and identify issues/bugs. There are a list of known bugs and outstanding functionalities. Please keep this in mind when capturing bugs so that we don't create too many duplicate issues. 

The testing scenarios cover the following functionalities:

  1. View Stock on Hand
  2. Manage Physical Inventory
    1. Create a new physical inventory
    2. Add new products during physical inventory
    3. Save physical inventory draft
    4. Submit a new physical inventory
    5. Remove a physical inventory draft
  3. Create an Adjustment
    1. Create new adjustment
    2. Choose products for adjustment
    3. Submit adjustment
  4. Make an Issue/Receive
    1. Perform ad hoc receipt
    2. Perform ad hoc issue

Test Roles

A complete list of users can be found in the README file on github.

Role NameLogin InformationRightsHome Facility
Storeroom Manager

user name: srmanager2

password: password

  • Adjust stock
  • Edit stock inventories
  • View stock cards
HC01- Comfort Health Clinic
Administrator

user name: administrator

password: password

  • Adjust stock
  • Edit stock inventories
  • View stock cards
  • Manage stock sources
  • Manage stock organizations
  • Manage stock card templates
  • Manage stock destinations
  • Manage stock adjustment reasons
  • Manage stock card line item reasons
HC01- Comfort Health Clinic

Below is a diagram describing the Stock Management process:



Test Scripts

Please enter your name in the Tester column. Then indicate if the steps passed/failed in the Pass/Fail column. Lastly, enter the number (example OLMIS-1725) of the bug you logged relating to the step.

Scenario 1: View SOH, summary, and search

1.TesterStepsExpected ResultsPass/FailBug logged
1


Enter http://uat.openlmis.org/ into a chrome or firefox browser
  • Starting OpenLMIS loading modal appears then login modal appears (should not take longer than 30 seconds?)



2

User logs in to view SOH summary:

  1. Log in as srmanager2
  2. Select Stock Management tab > Stock On Hand from the navigation bar
  3. Log in as administrator and complete the same process
  • User can see Stock Management tab
  • User selects Stock on Hand and is directed to the Stock on Hand search screen
  • Breadcrumbs at the top of the screen show Stock Management / Stock on Hand




3

User completes search:

  1. Facility Type is defaulted to My Facility and Facility Name is your Home Facility: Comfort Health Clinic
  2. Select Program Name: Family Planning. Click Search.
  3. Clear search to complete a free text search.
  4. Enter free text into the Keywords field and click Search.
  5. Complete same search for Program Name: Essential Meds


  • My Facility should show as the default. Facility name is defaulted to Comfort Health Center
  • The results grid should default to "No products found" showing no items
  • For Program Name, user can see Family Planning and Essential Meds to select
  • When user completes search, the results grid shows all products
  • Results list 20 products on each page with the following columns: Product Code, Product, Lot Number, Expiry Date, Last update, SOH, Actions
  • Results display Action button to View
  • When user completes free text search in the Keywords field, results display if there is a match, or the results grid shows "No products found" if there is no match.



Scenario 2: Manage Physical Inventory

2.TesterStepsExpected ResultsPass/FailBug logged
1


Enter http://uat.openlmis.org/ into a chrome or firefox browserWelcome screen appears and there is a modal asking for login credentials

Pass

Pass



Scenario 3: Creating and submitting a regular type requisition for the Family Planning program

3.TesterStepsExpected ResultsPass/FailBug logged
1



Enter http://uat.openlmis.org/ into a chrome or firefox browserWelcome screen appears and there is a modal asking for login credentials

Pass!

Pass


Scenario 4: Creating and submitting an emergency type requisition for Family Planning

4.TesterStepsExpected ResultsPass/FailBug logged
1
Enter http://uat.openlmis.org/ into a chrome or firefox browserWelcome screen appears and there is a modal asking for login credentialspassNote: smanager not srmanager

Scenario 5: Authorizing a requisition

There should be a requisition created for 


TesterStepsExpected ResultsPass/FailBug logged
1
Enter http://uat.openlmis.org/ into a chrome or firefox browserWelcome screen appears and there is a modal asking for login credentialsPass


Scenario 6: Approving a requisition

Please let Mary Jo Kochendorfer (Deactivated) know when you plan to test this so she can ensure there is a requisition ready for approval so that you can approve. 



TesterStepsExpected ResultsPass/FailBug logged
1


Enter http://uat.openlmis.org/ into a chrome or firefox browserWelcome screen appears and there is a modal asking for login credentialsPass

Scenario 7: Rejecting a requisition*

Please let Mary Jo Kochendorfer (Deactivated) know when you plan to test this so she can ensure there is a requisition ready for approval so that you can reject.


TesterStepsExpected ResultsPass/FailBug logged
1
Enter http://uat.openlmis.org/ into a chrome or firefox browser. Login as Program Supervisor.Welcome screen appears and there is a modal asking for login credentialsPass

Scenario 8: Converting a requisition to an order


TesterStepsExpected ResultsPass/FailBug logged
1
Enter http://uat.openlmis.org/ into a chrome or firefox browser. Login as a warehouse clerk.Welcome screen appears and there is a modal asking for login credentialsPass

Scenario 9: View a list of requisitions


TesterStepsExpected ResultsPass/FailBug logged
1
Enter http://uat.openlmis.org/ into a chrome or firefox browser. Login as Program Supervisor.

Welcome screen appears and there is a modal asking for login credentials.

Home screen is visible after credentials are accepted.

Pass



Known Bugs

key summary type created assignee reporter priority status resolution fixversions
Loading...
Refresh


  • No labels