After completion of test planning corresponding testers in scrum team can start test design by writing test scenarios, test cases and test data for responsible module.
a. Study all user stories in sprint backlog(SBL):
Sprint backlog is part of product backlog, testers responsible modules are part of sprint backlog.
But specific testers need to understand all user stories in sprint backlog or product backlog
b. Prepare test scenarios and test cases for responsible user stories:
From testing principles exhaustive testing impossible, Ad-hoc testing is not reasonable due to this reasons testers can prepare test scenarios and cases for responsible modules optimal testing. Here testers can follow black-box testing techniques and IEEE829 standard format to prepare optimal test cases for responsible modules.
Black-Box testing techniques:
To prepare optimal scenarios and cases for responsible modules functional testing, every tester can follow black box testing techniques or closed-box testing techniques.
BVA, Boundary values analysis techniques is used to write test cases on size of inputs and outputs.
Examples: from user stories, userid can take 4 to 16 positions long data BVA (size of userid).
Min 4 Pos valid
Min-1 3 Pos invalid
Min+1 5 Pos valid
Max 16 Pos valid
Max-1 15 Pos valid
Max+1 17 Pos invalid
ECP, equivalence classes’ partitions techniques is used to write test cases on type of inputs and outputs.
Example: From user stories, user id can take alphanumeric in lower case.
Examples: From user stories, next page will come for valid userid and valid password and error message any one is invalid in login.
Orthogonal arrays(OA):
OA, we can this technique to remove repetition in test cases.
STF, state transition flow techniques is used to write test cases in order with respective to functionality.
EG, error guessing Technique is used to guess defect in upcoming sprint or software depends on past experience.
Note: BVA -> Write test cases
ECP -> Write test cases
DT -> Write test cases
OA->Remove repetition in test cases
STF ->Arrange test cases in order
EG ->Guess defect without running cases on sprint or software
So, one software means multiple sprints. One sprint means multiple modules. One modules testing means applying multiple test scenarios. One scenario means applying multiple test cases. One case means one condition.
In above test cases document format test cases document ID is useful to refer documents in feature. Test ID is useful to group related scenarios and cases.
*Priority is used to specify importance of test cases.
Example: Functional test cases High
Non-functional test cases Medium
Usability test cases Low
While preparing test cases for functional testing we can use test step to specify necessary conditions.
While preparing test cases for non-functional testing we can use “test environment” to specify required hardware and software.
Test procedure useful to write step by step process with test cases for every scenario.