Software Testing Life Cycle talks about the testing activities performed on the software product from the requirement analysis phase till test closure phase. STLC includes preparation of various types of documents at each phase which are deliverables to the stakeholders of the project.
STLC provides an organized approach to carry out testing activities towards building a quality product in a well-planned manner. Also, STLC provides and insight into what needs to be done and when.
In this blog, we shall learn on what are the important points pertaining to STLC, from where it starts, various phases of STLC, details of each phase with examples.
From where STLC starts for a project?
First of all, Test Strategy is the document prepared by the Senior QA Manager or QA Manager with the support of the customer. This is the first step to start STLC for a software project.
What is Test Strategy document?
Test Strategy is a primary document for any testing practice to start on a software product. Preparation of Test Strategy document and finalizing it takes a considerable amount of effort from both QA as well as the client’s as the document has to contain the testing strategy for the entire software product’s lifetime.
Test Strategy document
majorly focuses on:
Modules of the software product
Different types of testing that needs to be performed
Strategy for Automation Testing implementations
Various Testing environments – Functional, Integration, Automation, Regression, Pre and Post Production etc.
Strategy to collect data for various types of testing
Software versions release model
Skill-sets required by the testers
Tools and specific third-party software and/or hardware requirements
QA Sign-Off criteria
Roles and responsibilities of various parties involved in the project and team etc.
When to prepare Test Strategy?
Test strategy is ideal to be prepared, reviewed and signed by all stakeholders by the time the project gets officially kicked-off. All the further testing activity in the project is carried out keeping the test strategy document as a reference.
Test Strategy, after
finalizing and approved by stakeholders, is updated only when there is a change
or modification to the strategy over a period of time, else it remains
unmodified throughout the software project lifetime.
Test Strategy document is ideally prepared once in the software product lifetime but can be modified or updated based on the need over a period of time. However, the modified version of the Test Strategy document has to be reviewed and approved by the stakeholders.
Phases of STLC:
Test Environment Preparation