Test case template

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

Test Case #:284	Test Case Name:
System:	Subsystem:
Test case designed by:	Design Date:17.02.2017
Short description:

Pre – conditions:

Step	Action	Expected system response	Comment
1
2
3
4
5
6
7
8

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.

Story #	QA Tester
OLMIS-0000	Sam Im

Does the ticket change any UIs?

If so, please check for UI Style Guide compatibility:

Style	Validation or Expected Result	Tested (Y/N)	If No, you must add Comments
Adds change to component CHANGELOG.MD	Change log contains JIRA Ticket number Change log contains brief high level description
Follows UI Component Guidelines http://build.openlmis.org/job/OpenLMIS-reference-ui/lastSuccessfulBuild/artifact/build/styleguide/index.html	Search results must be paginated with 10 results per page.
Capitalization https://github.com/OpenLMIS/openlmis-requisition-refUI/blob/master/styleguide/homepage.md	Buttons are titled cased "Are You Afraid of the Dark" Title headings are title cased (see above) Field labels have the first letter capitalized only
Internationalization (Translation)	Check that strings don't show message keys
UI Layout Guidelines http://build.openlmis.org/job/OpenLMIS-reference-ui/lastSuccessfulBuild/artifact/build/styleguide/index.html	Breadcrumbs visible Tables follow guidelines Only one modal visible at a time
Browser check https://openlmis.atlassian.net/wiki/display/OP/Test+Strategy	1000px and 1300px browser width Chrome and Firefox (latest versions)
Form Entry and Errors	Text inputs: users can enter in text; check length and special characters. Numeric inputs: users can enter in numbers (such as positive integers) but other entries are prevented or give a helpful error message. Error messages presented to the user should contain only that information which will allow the user to correct the page. Inline errors: user enters invalid data in field, receives error message within form. Submit errors: user initiates an action, error message includes text that explains reason for error that user can understand, user is unable to complete action and is returned to current page.
Loading Performance	Loading modal is shown for page transitions Loading modal is shown when saving or deleting objects Loading modal is shown while the UI is fetching or processing any data
Offline Performance	Will show warning if it doesn't support offline functionality If offline feature, it works as specified
Role based access control	Different users have access to view and complete certain actions based on their roles. If user doesn't have access, the correct behavior should be validated. Provide a list of which roles were tested in the ticket.

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

Install JIRA Capture (see instructions below)
Review the current state of the software test scope, and test roles for context
Sign up for the test scrips you plan to do, by linking your name (typing '@' and your name) in the "Tester" column
Login and start testing the system
When a test fails, please log bugs using JIRA Capture and the OpenLMIS pre-3.0 UAT template
1. Example bug logged, here.
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:

xxx

Test Roles

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

Role Name

Login Information

Rights

Home Facility

Storeroom Manager

user name: srmanager2

password: password

Administrator

user name: administrator

password: password

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:

1.	Tester	Steps	Expected Results	Pass/Fail	Bug logged (JIRA ticket)
1
2
3

Scenario 2:

Known Bugs