Test case template

• Test cases are created in Zephyr.
• Insert process of required data to create test case in Zephyr to maintain traceability.

Testing Standards Checklist

The purpose of this checklist is to provide testing guidelines for issues or tickets in addition to the Acceptance Criteria. These are standards that must be validated for all stories unless otherwise explained in the comments. For example, in a View-only screen story there is no user input so Field Validation testing is not required.

Does the ticket change any UIs?

If so, please check for UI Style Guide compatibility:

Product Committee Acceptance Testing Template

This template should be used for the Product Committee Acceptance Testing prior to a big release.

Table of Contents

Insert table of contents here

Please log all bugs PRIOR to DATE

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
• We are reusing the previous template, please 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

• Insert JIRA Tickets here

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

Test Roles

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

Below is a diagram describing the 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:

Scenario 2: 

Known Bugs