Software Testing Life Cycle – Test Design – Manual Testing

 

Software Testing Life Cycle – Test Design – Manual Testing

 

III. Test Design:

 

a) Understanding all modules:

In general tester responsibilities can start with studying user stories to understand complete sprint or software.  Here tester can follow any one of below ways to understand complete sprint or software.

Most of testers in ST can follow third way because user stories are easy to understand.

 

b) Writing Scenarios and cases for responsible module:

After completion of all modules user stories analysis tester can concentrate on responsible modules, test scenarios and cases writing.

In general, one software is developing as multiple sprints in agile scrum model. One sprintis having multiple modules. One module is having multiple multitasks. Every task is called as one scenario. Every scenario validation needs multiple conditions checking. Here one condition means one test case.

While writing test cases, we need to follow Black box testing techniques because exhaustive testing is impossible. Black box testing techniques are also called as closed box testing techniques or functional testing techniques.

 

Note:  For non-functional test cases writing, we need to follow other techniques (Exploratory techniques).

 

C) Black Box Testing Techniques:

While writing test scenarios and test cases for responsible modules functional testing, tester can follow below black box testing techniques:

->  BVA, Boundary values Analysis technique is used to define test cases related to size or range of inputs and outputs.

->  ECP, Equivalence class partitioning technique is used to define test cases related to type of inputs and outputs.

-> DT,  Decision table technique is used to define mapping in between inputs and outputs.

-> OA,  Orthogonal Arrays technique is used to remove repentant test cases to maintain test cases as unique.

->  State Transition Flow STF technique is used to write test cases in order w.r.t functionalities in sprint or software.

-> EG, Error guessing technique is used to guess defects in upcoming sprint or software depends on past experience.

 

d) IEEE 829 format for test scenarios with cases:

1. Test Scenario or Test cases document ID:

Unique name or a title for a document.

2. Test scenario:

Name of the scenario in detail.

3. Test Suite ID:

ID of a group, in which current scenario is a member.

4. Priority:

The importance of current scenario.

Example:

Functional test scenarios and cases  –  High priority.

Non-functional test scenarios and cases –  Medium priority.

Usability test scenarios –  Low priority.

 

5. Test setup or test environment:

Necessary things needed before going to check current scenario.

6. Test procedure:

A step by step process to check current scenario.

Step Number	Step Description	Test Cases	Expected Result

 

Note 1:

MS excel or open office excel is a better software to develop test scenarios and cases by following IEEE 829 standards and Black box testing techniques.

 

In this article we have seen  Software Testing Life Cycle – Test Design – Manual Testing. In the next article will see the case study of Online banking website.