Software Testing Life Cycle (STLC) – Manual Testing
Software Testing Life Cycle (STLC) – Manual Testing
In V and Fish like model, STLC stands Software Testing Life Cycle. In Agile model, STLC stands for Sprint Testing Life Cycle.
Agile scrum model with STLC:
Software bidding : A proposal to develop a new software.
a) Project : A proposal came from customer.
b) Product : A proposal based on market requirements by own company.
Kick of meeting : Selection of PO under guidance of customer and stake holders.
Product back log grooming meeting : Gather all user stories.
Sprint planning meeting : Selection of some user stories.
I. Test Initiation :
STLC can start with test initiation. In this stage PO can prepare a test strategy (or) Methodology
(or) Approach for testers.
In general , 3 types of strategies are available such as.
- Exhaustive
- Optimal
- Ad- hoc
Exhaustive testing is nothing but test with all values .
Optimal testing is nothing but test with some values w.r.t techniques.
Ad-hoc testing is nothing but test with Few Values randomly.
From testing principles exhaustive testing is impossible and Ad-hoc testing is not reasonable. Due to those reasons, PO can prepare optimal test strategy for testers.
Example : From user story , Age will take 16-60
| Exhaustive | Optimal | AD-hoc |
| 16
17 18 . . . 60 |
Minimum -1 15
Minimum +1 16 Minimum+1 17 Maximum -1 59 Maximum +1 60 Maximum +1 61
|
16
60 |
Optimal Testing Strategy Document Format :
In general PO can prepare Optimal test strategy for current sprint or software testing by following IEEE 829 standards. From these standards, test strategy document is having below fields.
- Test Strategy Document ID:
Unique name or number for document.
Ex: Title of the document
- Scope and Objective:
Importance of testing in current sprint.
- Business Issues:
Budget allocation to testing services.
4. Test Responsibility Matrix:
List of test to be conducted in current sprint or software.
Example:
| Testing Topic | Yes/No | Comments |
| Functional Testing(8 Topics) | Yes | – |
| Usability Testing | Yes | – |
| Compatibility Testing | Yes | – |
| H/W Configuration Testing | Yes | – |
| Performance Testing | No | Lack of Resources |
| Security Testing | No | Lack of Skills |
| Multilanguity Testing | No | – |
- Roles and Responsibilities:
Name of Jobs in testing team and responsibilities of each job.
| Role | Responsibilities |
| SM | -> Prepare Test Plan
-> Conduct daily scrum meet -> Responsible for Status reporting ( Burndown chart) |
| Sr. Tester | -> Prepare test scenarios, test cases and test data.
-> Track defects with developers. |
| Jr. Tester | -> Execute test cases on sprint or software.
-> Report defects to developers. |
- Automation and need for Automation:
From the above diagram PO is responsible to decide need for automation in current sprint testing.
- Defect Reporting and Tracking:
- Testing Measurements and Metrics:
To estimate efficiency of testers during testing, PO can define some measurements and metrics.
Example:
- 15 – 20 Test scenario cases preparation per day.
- 10 – 15 Test scenario cases execution per day.
- 3 – 5 Bugs detection per day.
- Test Management:
PO is responsible to store documents by developers and testers in specified folder structure in server computing.
From the above folder structure in server computer, development base is useful to store developers documents like user storage , Unit test case, Integration test cases etc.
Test base folder is used to store testing related documents like best strategy, test plan, test scenarios, test cases, test data, defect reports, test scripts etc.
Soft base folder is useful to store sprints or software builds.
- Training Plan:
PO can decide need for training to testers on current sprint or software requirements ( Optional when testers are experienced).
Note 1:
The above like optimal test strategy will be prepared by PO in MS word or Open office word.
Note 2 :
The above like optimal test strategy document is in IEEE 829 standard format.
Note 3:
PO can take approval on strategy from stake holders.
In this article we have seen Software Testing Life Cycle (STLC) – Manual Testing and Test Initiation in our next article will see Others things like Test Planning, Test Design etc.
