1. PART06
Hands-on Training
Identifying Test Scenarios and Test Cases

2.  Identifying Test Cases
 Creating Test Scripts
Test Preparation

3. Now that we have all the requirements captured in the RTM the next step is to:
Identify the test scenarios and test cases while mapping them to the requirements.

4. Activity
Identifying Test Cases
When
During Build Phase of SDLC
During Test Preparation of STLC
Responsible: QA Analysts

5.  Updated RTM
Purpose: Test Cases are mapped to requirements to track testing coverage.

6. Requirement Traceability Matrix
Functional Design Docs
Technical Specifications

7. Let’s look at the goals we need to achieve when identifying test cases.
Identify tests to validate the functionality by describing the test objective. (RTM or in Tool)
Identify tests for all test methods in-scope.
Positive & Negative
Data Integrity

8. Example to discuss: Requirement Requirement
All fields are read-only on the page.
Only numeric inputs should be allowed

9. The Test case objective describes what testing is needed in order to validate that requirement has been met.
Requirement
Test Scenario
All fields are read-only on the page.
Test that all fields are read only on the page.
Only numeric inputs should be allowed.
Tests to ensure only numeric inputs are allowed.

10. The first step is to identify the “what”.
Requirements
Test Case Objective
All fields are read-only on the page.
Test that all fields are read only.
Only numeric inputs should be allowed.
Tests to ensure only numeric inputs are allowed.

11. The next step is to determine the requirement of the what
Requirements
Test Case Objective
All fields are read-only on the page.
Test that all fields are read only.
Only numeric inputs should be allowed.
Tests to ensure only numeric inputs are allowed.

12. Now let’s write the test objective
Requirements
Test Case Objective
All fields are read-only on the page.
Test that all fields are read only.
Only numeric inputs should be allowed.
Test that only numeric inputs are allowed.
“Test” + what + Requirement

13. Test Cases are very specific.
Requirements must be tested from both a positive and negative perspective.
A Test Case is needed for each condition (positive and negative).
Not every Test case requires both positive and negative conditions to be tested while other do.

14. All fields are read‐only on the page.
Requirement
Test Scenario
Test Case
All fields are read‐only on the page.
Test that all fields are read only.
More info is needed on what fields are on the page.
Only numeric inputs should be allowed.
Test to ensure only numeric inputs are allowed.
Input numeric values into each field to ensure they are allowed. ‐ positive
Input all non numeric values into each field to ensure they are not allowed. (Including all letters, punctuation, and all special characters) ‐ negative

15. There will be requirements that contain several functions requiring multiple test scenarios.
Req No.
Business Requirement Description
Technical Requirement Description
B1.3
Must allow a user to capture their Birthday and display a message to the user "Knowing your birthday lets yahoo provide you with a better experience"
T1.3
Birthday will be divided into 3 fields.
The first field will be a drop down list for the user to select their month of birth. It will default to "-Select Month-"
The second field will be a input field allowing only numbers, defaulting to "Day". It will allow up to 2 characters.
The last field will be for the year of birth and default to "Year" allowing up to 4 characters
Only numeric values will be allowed in the Day and Year field.
No future dates will be allowed. An error message should be displayed "Are you really from the future.
If an invalid character and if a input field was left blank an error should be displayed reading "Your full birthday is required“
When field is populated a message will be displayed “Knowing your birthday lets yahoo provide you with a better experience.”

16. Birthday will be divided into 3 fields.
Req No
Technical Requirement
TR Sub
T1.3
Birthday will be divided into 3 fields.
The first field will be a drop down list for the user to select their month of birth. It will default to "-Select Month-"
The second field will be a input field allowing only numbers, defaulting to "Day". It will allow up to 2 characters.
The last field will be for the year of birth and default to "Year" allowing up to 4 characters
Only numeric values will be allowed in the Day and Year field.
No future dates will be allowed. An error message should be displayed "Are you really from the future.
If an invalid character and if a input field was left blank an error should be displayed reading "Your full birthday is required“
When field is populated a message will be displayed “Knowing your birthday lets yahoo provide you with a better experience.”
No future dates will be allowed. An error message should be displayed "Are you really from the future"

17. Technical Requirement Description
Birthday will be divided into 3 fields.
The first field will be a drop down list for the user to select their month of birth. It will default to "-Select Month-"
The second field will be a input field allowing only numbers, defaulting to "Day". It will allow up to 2 characters.
The last field will be for the year of birth and default to "Year" allowing up to 4 characters
Only numeric values will be allowed in the Day and Year field.
No future dates will be allowed. An error message should be displayed "Are you really from the future"
If an invalid character and if a input field was left blank an error should be displayed reading "Your full birthday is required“