An introduction to STLC
In this blog, I will discuss STLC and its different phases. Software Testing Life Cycle is the process of different steps to be executed in a definite sequence to ensure that the quality goals have been met.
STLC is an indispensable part of the Software development life cycle (SDLC) but STLC is only meant to deal with the testing of the product.
Phases of STLC
Basically, STLC has 6 different phases all phases are unique and performed step by step to ensure a bug-free product.
Following are the phases of STLC:
1. Requirement Gathering Stage: As per the testing point of view, we need to identify testable requirements.
Requirement gathering activities
- QA team interact with stakeholders(Client, Business Analyst, Technical Lead etc.) to understand the requirement in detail.
- Identify types of tests to be performed.
- Gather details about testing priorities and focus.
- Identify test environment details to be carried out
2. Test Planning and Control: QA Managers determine effort and cost estimates of the project and would create and finalise a test plan.
Test Planning Activities:
- Type of Testing: System or Functional, UAT, Performance
- Scope of testing – Features that will be tested, Features out of scope
- Test Environment: Hardware, Software needed for the Test Environment, Test Data
- Test Tools Selections and Resources needed for testing
- Schedule: The dates when each activity will start and complete and dependencies if any
- Review & Sign-off of test artifacts from Stakeholders – PM, BA, Customer, Development Lead etc.
- Number of test cycles planned
- Risks – Software Risks, Project risks (Test Environment not ready, unable to procure a license, resource quits) and prioritization of tests based on risk during a time crunch
- What to do when deliverable to testing are delayed
- Test Control: This is to address what to do when actual progress does not match with the estimates when things go wrong etc.
3. Test Analysis and Design: This STLC stage defines “WHAT” to be tested. We basically identify the test conditions through the requirements document, product risks, and other test bases. The test condition should be traceable back to the requirement. Test Analysis and design activities
- Requirements document, Functional Spec, Design Documents etc. are reviewed and understood in detail and tests are designed.
- Levels and depth of testing
- Designing and prioritizing test cases
- Designing the test environment
- Determining the test data
4. Test Implementation and Execution: Creation of test cases and execution is the main agenda of this stage.Test Implementation and Execution Activities:
- Test cases are created from the test conditions.
- Developing and prioritizing test cases.
- Executing test cases (either manually or by using test execution tools) according to the planned sequence.
- Logging the outcome of test execution and recording the identities and versions of the software under test.
- Comparing actual results with expected results
5. Evaluating exit criteria and reporting: Evaluating exit criteria and reporting Activities
- Checking test logs against the exit criteria specified in test planning.
- Assessing if more tests are needed or if the exit criteria specified should be changed.
- Writing a test summary report for stakeholders.
6. Test Closure : Final stage of STLC Test Closure Activities
- Specified objective or target is achieved by the team.
- Maintenance and required changes are needed to be done.
- Lessons learned when testing is completed and documented.
Please tell us about your STLC knowledge before-and-after reading. I bet you’ll have something to say !!!
Happy Learning 🙂