SOFTWARE TESTING LIFE CYCLE – STLC – Part – 1

This blog explains about SOFTWARE TESTING LIFE CYCLE – STLC – Part – 1 and is given below :     

_______________________________________________________________________________________

                                                                     STLC

INTRODUCTION:

  • STLC stands for Software Testing Life Cycle. STLC is a sequence of different activities performed by the testing team to ensure the quality of the software or the product.
  • STLC is an integral part of Software Development Life Cycle (SDLC). But, STLC deals only with the testing phases.
  • STLC starts as soon as requirements are defined or SRD (Software Requirement Document) is shared by stakeholders.
  • STLC provides a step-by-step process to ensure quality software.
  • In the early stage of STLC, while the software or the product is developing, the tester can analyze and define the scope of testing, entry and exit criteria and also the Test Cases. It helps to reduce the test cycle time along with better quality.
  • As soon as the development phase is over, the testers are ready with test cases and start with execution. This helps to find bugs in the initial phase.

 

                                                   PHASES OF STLC                                          

1.REQUIREMENT ANALYSIS:

  • Entry criteria for this phase is BRS (Business Requirement Specification) document. During this phase, test team studies and analyzes the requirements from a testing perspective.
  • This phase helps to identify whether the requirements are testable or not. If any requirement is not testable, test team can communicate with various stakeholders (Client, Business Analyst, Technical Leads, System Architects etc) during this phase so that the mitigation strategy can be planned.

Entry Criteria: BRS (Business Requirement Specification)

Deliverables: List of all testable requirements, Automation feasibility report (if applicable)

2.PLANNING PHASE:

  • In practical scenarios, Test planning is the first step of the testing process. In this phase we identify the activities and resources which would help to meet the testing objectives.
  • During planning we also try to identify the metrics, the method of gathering and tracking those metrics.

On what basis the planning is done? Only requirements?

The answer is NO. Requirements do form one of the bases but there are 2 other very important factors which influence test planning. These are:

– Test strategy of the organization.

– Risk analysis / Risk Management and mitigation.

3.TEST DESIGN:

  • Test team starts with test cases development activity here in this phase. Test team prepares test cases, test scripts (if automation) and test data. Once the test cases are ready then these test cases are reviewed by peer members or team lead.
  • Also, test team prepares the Requirement Traceability Matrix (RTM). RTM traces the requirements to the test cases that are needed to verify whether the requirements are fulfilled.
  • The deliverables of this phase are Test Cases, Test Scripts, Test Data, Requirements Traceability Matrix

Entry Criteria: Requirements Documents (Updated version of unclear or missing requirement)

Deliverables: Test cases, Test Scripts (if automation), Test data.

4.TEST ENVIRONMENT SETUP:

  • This phase can be started in parallel with Test design phase. Test environment setup is done based on the hardware and software requirement list. Some cases test team may not be involved in this phase.
  • Development team or customer provides the test environment. Meanwhile, test team should prepare the smoke test cases to check the readiness of the given test environment.

Entry Criteria: Test Plan, Smoke Test cases, Test Data

Deliverables: Test Environment. Smoke Test Results.

5.TEST EXECUTION:

  • Test team starts executing the test cases based on the planned test cases. If a test case result is Pass/Fail then the same should be updated in the test cases.
  • Defect report should be prepared for failed test cases and should be reported to the Development Team through bug tracking tool (eg., Quality Center) for fixing the defects. Retesting will be performed once the defect was fixed. Click here to see the Bug Life Cycle.

Entry Criteria: Test Plan document, Test cases, Test data, Test Environment.

Deliverables: Test case execution report, Defect report, RTM

6.TEST CLOSURE:

The final stage where we prepare Test Closure Report, Test Metrics.

Testing team will be called out for a meeting to evaluate cycle completion criteria based on Test coverage, Quality, Time, Cost, Software, Business objectives. Test team analyses the test artifacts (such as Test cases, Defect reports etc.,) to identify strategies that have to be implemented in future, which will help to remove process bottlenecks in the upcoming projects. Test metrics and Test closure report will be prepared based on the above criteria.

Entry Criteria: Test Case Execution report (make sure there are no high severity defects opened), Defect report

Deliverables: Test Closure report, Test metrics.

                                                                                       +————————-+———————–+

    BY

BHUVANESHWARI

Reference :             

www.softwaretestingmaterial.com/stlc-software-testing-life-cycle/

www.tutorialspoint.com/stlc/stlc_overview.htm

http://www.oraclechennai.com/stlc.html

https://xbsoftware.com/blog/software-testing-life-cycle-stlc-benefits-major-testing-steps/