3. Software Testing Life Cycle (STLC)

The Software Testing Life Cycle (STLC) is a structured process that defines specific steps and phases followed by the QA team to ensure that software testing is carried out systematically, efficiently, and effectively.

While SDLC focuses on software development, STLC focuses on software testing.

The Software Testing Life Cycle (STLC) outlines the systematic process that quality assurance (QA) teams should follow when testing software. Its purpose is to make sure testing is conducted in an organized and thorough manner. Unlike the Software Development Life Cycle (SDLC), which emphasizes the stages of software development, STLC is specifically aimed at the various aspects of testing software. Having a structured approach helps in minimizing errors and ensures that all testing activities are documented and executed correctly.

Think of STLC like preparing for a big exam at school. You can't just sit down and start answering questions without a plan. You would typically have to review your study materials, create a study schedule, practice past papers, and finally, evaluate your performance after the exam. Similarly, STLC includes phases that ensure the testing process is effective and well-prepared.

✅ 1. Requirement Analysis Objective: Understand what needs to be tested and identify testable requirements. Activities: ● Review Business Requirement Documents (BRD), Functional Specs, User Stories ● Identify gaps, inconsistencies, or ambiguities ● Determine testable and non-testable requirements ● Involve BA/Product Owner for clarification Deliverables: ● Requirements Traceability Matrix (RTM) ● Requirements Review Report Entry Criteria: ● BRD/FRD/User Stories are available ● QA team is identified Exit Criteria: ● Requirement understanding is signed off ● RTM is initiated

The Requirement Analysis phase is critical because it establishes a clear understanding of what needs testing. The objective is to ensure that the requirements gathered are complete, clear, and can be tested effectively. The QA team reviews documents such as Business Requirements Documents and User Stories to identify if there are any missing pieces or unclear sections. The deliverables for this phase, like the Requirements Traceability Matrix, help link requirements to test cases, ensuring that all requirements are tested. This phase cannot begin unless the necessary documents are available, and it ends when the requirements are agreed upon and documented.

Consider a chef preparing a new dish. Before cooking, the chef needs to ensure they have a complete recipe and understand every ingredient's role. If there are gaps in the recipe, the dish may not turn out as expected. Similar to this, the QA team needs to analyze the requirements thoroughly to ensure nothing is missing to deliver a quality software product.

✅ 2. Test Planning Objective: Define the strategy, scope, objectives, and logistics of the testing process. Activities: ● Identify test objectives and types (functional, regression, smoke) ● Estimate effort and resources ● Decide tools, roles, responsibilities ● Define Entry and Exit Criteria for each test phase Deliverables: ● Test Plan Document ● Risk Management Plan ● Effort Estimation Sheet Entry Criteria: ● Requirements baseline is completed ● Test strategy template is available Exit Criteria: ● Test plan is reviewed and approved ● Team and environment are ready

During the Test Planning phase, the focus shifts from simply understanding requirements to outlining how testing will be conducted. This involves establishing the objectives of testing, defining what types of testing will be performed, estimating the necessary resources, and choosing the right tools for the job. The outcomes are documented in a Test Plan, which acts as a blueprint for the testing process. This phase begins only after the requirements are solidified, and it concludes when the testing plan is approved and the team is prepared to start testing.

Imagine organizing a wedding. You need to decide the venue, caterer, guest list, and schedule before the event. Each decision impacts how the day will unfold. Similarly, a QA team must prepare a detailed testing plan to ensure that testing runs smoothly and meets deadlines.

✅ 3. Test Case Development Objective: Design detailed test cases based on requirements and prepare test data. Activities: ● Write manual test cases or automated scripts ● Identify and create test data (dummy inputs) ● Review test cases for completeness and coverage Deliverables: ● Test Cases & Test Scripts ● Test Data ● Review Comments/Sign-off Entry Criteria: ● Test plan is approved ● RTM is finalized Exit Criteria: ● All test cases are reviewed and approved ● Test data is prepared

In the Test Case Development phase, the QA team translates the requirements into specific test cases that detail how each requirement will be tested. This includes both manual and automated testing scripts and the creation of necessary test data to verify those cases. It’s essential that all test cases are thoroughly reviewed for accuracy and completeness before moving forward. The phase concludes once all test cases are approved and the necessary test data is prepared for execution.

Think of this phase like a teacher preparing exam questions based on the syllabus. The teacher must ensure each question relates clearly to the content taught, and the assessment tools are available. If not prepared correctly, the assessment may not accurately measure student understanding.

✅ 4. Test Environment Setup (Parallel Phase) Objective: Prepare the hardware/software setup required for testing. Activities: ● Configure test servers, databases, staging environments ● Install required tools (e.g., Selenium, JIRA, TestRail) ● Validate environment readiness (smoke test) Deliverables: ● Environment Validation Report ● Access credentials and URLs Entry Criteria: ● Environment requirements are known ● Hardware/software is available Exit Criteria: ● Test environment is stable and accessible

During the Test Environment Setup phase, the necessary hardware and software conditions are prepared to ensure that tests can be executed effectively. This includes configuring servers and databases as well as installing any required testing tools. A smoke test is conducted to verify that the environment is functioning as needed before actual testing begins. This phase starts when the required environment specifications are finalized and ends when the testing environment is confirmed to be stable.

Setting up the testing environment can be compared to preparing a classroom before students arrive. The teacher ensures that all materials, desks, and tools are ready for a smooth learning experience. Similarly, QA teams must ensure every technical aspect is in place before test execution.

✅ 5. Test Execution Objective: Execute test cases and report any defects found. Activities: ● Execute manual/automated tests ● Record actual results and compare with expected outcomes ● Log defects in tools like JIRA ● Retest after defect fixes Deliverables: ● Test Execution Report ● Defect Report & Bug Tracker Updates ● Updated RTM Entry Criteria: ● Test cases and test data are ready ● Test environment is up and running Exit Criteria: ● All test cases executed ● All critical bugs are fixed or deferred with approval

In the Test Execution phase, the actual testing happens as planned. Test cases are executed either manually or through automation, and the results are compared against expected outputs. Any discrepancies or failures are logged as defects, and the QA team may need to retest once fixes are applied. This phase ensures that all aspects of the application are checked for quality and compliance with requirements. It begins when the test cases and environment are ready and ends when all critical tests are complete.

Executing test cases is like conducting a quality check on a product in a factory. Each product needs to be tested for quality against specifications. If any product fails, it needs to be brought back for corrective action before it can be released to customers.

✅ 6. Test Cycle Closure Objective: Formally close testing activities, assess metrics, and document learnings. Activities: ● Ensure all test cases are executed and defects addressed ● Evaluate test coverage and quality metrics ● Conduct retrospective or post-mortem analysis ● Archive testware for reuse Deliverables: ● Test Summary Report ● Lessons Learned Document ● Final RTM Entry Criteria: ● Test execution is complete ● Defect status is resolved or accepted Exit Criteria: ● All deliverables are submitted ● QA sign-off is obtained

The Test Cycle Closure phase is where the testing process is formally concluded. The QA team makes sure that all test cases have been executed and all defects have been addressed appropriately. They will also analyze data related to test coverage and quality to learn from the experiences gained. This phase provides a summary of testing outcomes through reports and final documentation, ensuring that lessons learned can be applied in future testing cycles. It starts after test execution is complete and ends with formal acceptance and submission of all deliverables.

Think about wrapping up a project at school. After completing the project, you review your work, reflect on what went well or what you'd do differently, and prepare a final report. This phase is much like that, as the QA team reflects on the testing journey and consolidates all insights for future reference.

--