Task: Design and Develop Test Cases and Test Scenarios

A test case is a set of conditions or variables under which tester will determine whether an application is working correctly or not.

Relationships

Roles	Primary: Performance Test Lead QA Analyst	Additional:	Assisting:
Inputs	Mandatory: Architecture Vision Business Requirements Document (BRD) Performance Test Plan Document Requirements Hand-Off Confirmation	Optional: None	External: None
Outputs	Business Flow Document (BFD) Performance Test Scenario Requirements Traceability Matrix (RTM) Test Case

Main Description

Once the functional requirements are signed off and finalized by Business Analyst (BA), QA should start analyzing requirements to develop test cases and scenarios. A test case will have known input or action and an output or expected result. Written test cases should include a description of the functionality to be tested, and the setup/preparation required to ensure that the test can be conducted.

Steps

Obtain required information

Obtain from business and project team(s) the following items before developing any test cases / test scenarios:

Finalized Business Requirements (BRD)
Use cases or business workflows
Requirement Traceability Matrix (RTM) from BA
Architect diagram
Data definitions

Create Scenario in ALM

Application walk through and Creation of Business Flow Document (BFD)

Link scenarios with requirements in ALM

Properties

Predecessor	Hand-Off from Requirements to QA
Multiple Occurrences
Event Driven
Ongoing
Optional
Planned
Repeatable

Version and Release

Unified Life Cycle (ULC): 5.1, November 3, 2014
Phase Gates: 1.1, May 27, 2014
Process Engineering Process (PEP): 1.1, May 27, 2014