Software Testing Life Cycle (STLC)

Share

Software Testing Life Cycle (STLC)

Software Testing Life Cycle may be a testing method that is dead in an exceedingly sequence, so as to boost the standard of the productit’s process the steps/ stages/ phases in an exceedingly testing of software. It takes a sequence of steps that area unit applied so as to validate the software. There area unit completely different phases in STLC that area unit given below:

  1. Requirement analysis
  2. Test planning
  3. Test case development
  4. Environment Setup
  5. Test Execution
  6. Test Cycle Closure

Requirement analysis

This is a really 1st section of the testing life-cycle, during this stage, the Testing or Quality Assurance team decides what must be tested. By finding out the requirements, the testing groups gets associate degree understanding of the scope of testing. This section may involve conversations with developers, designers, and stakeholders.
There area unit 2 main types of testing – functional and non-functional. Functional testing includes tests to evaluate how  the software is functioning. Non-functional testing includes options that area unit covert like performance and security.

Activities done in this Phase:

  1. Categorizing the testing strategies and testing varieties
  2. Gather details concerning testing priorities and focus.
  3. Preparation of RTM that’s Requirement Traceability Matrix
  4. Identify the testing environment wherever actual testing are going to be done
  5. Automation Feasibility analysis (if required).
  6. Analyzing the System Requirement specifications from the testing purpose.
  7. Analyzing the Automation feasibility

Outcomes of Requirement analysis Phase

  1. RTM (Requirement Traceability Matrix).
  2. Automation Feasibility report.

Test Planning Phase

This section is additionally referred to as Test Strategy section. What to testhowever the test must be done, and who’s going to test it… these area unit the items resolute throughout the test planning section. A test plan documents area unit created throughout this section.

Activities done in this Phase:

  1. Preparation of test plan/strategy document for numerous varieties of testing
  2. Estimation of testing effort
  3. Selection of Testing methodology and tools
  4. Resource planning and process roles and responsibility to them
  5. Training requirement

Outcomes

  1. Effort estimation document.
  2. Test planned Strategy document.
  3. Best appropriate Testing Approach
  4. Number of Resources, talent needed and their roles and responsibilities
  5. Testing tool to be used

Test Case Development

One of the necessary stages of the Software Testing Life Cycle is Test case developing. This includes writing out a step wise procedure on how the test ought to be execute, the expected results, the actual results, and Test Fail/Pass status

Activities done in this Phase:

  1. QA team write test cases and scripts for automation
  2. Review and baseline test cases and scripts
  3. Verification of test cases and automation scripts
  4. Parameterization of Testing data into testing environment

Outcomes

  1. Test cases/scripts
  2. Test data

Test Environment Setup

This section includes the setup or installation method software and hardware that is needed for testing the appliancethis could be worn out parallel with Test Case Development Stage.

Once the installation of the build is sure-fire and complete then the test data is generated. once the creation of test Data, the Smoke testing is start on the build in order to see whether or not the essential functionalities area unit operating smart or not.

Activities done in this Phase:

  1. Understand the desired design for environment set-up
  2. Prepare hardware and software requirement list for the check Environment.
  3. Setting up Test environment and creation of test data
  4. Do smoke Test on the build

Outcomes

  1. Environment setup ready with test data
  2. Smoke test Reports.

Test Execution

Once the preparation of Test Case Development and Test Environment setup is completed then test execution phase starts. . throughout this section test team, can perform the checking supported the Testplans and also the test cases ready. Bugs are going to be according back to the event team for correction and retesting are going to be performed.

Activities done in this Phase:

  1. Execute Test Cases
  2. Reporting test results, and log defects for failing cases
  3. Verification and retesting of the defect
  4. Track the defects to closure

Outcomes

  1. Completed RTM with execution condition
  2. Updated test cases with results
  3. Defect/Bug reports

Test Cycle Closure

In this section QA team, will meet, discuss and analyze testing artifacts to spot methods that need to be enforced in future, taking lessons from the present Test cycle. the thought is to get rid of the method blocks for future Test cycles and share best practices for any similar comes in future.

Activities done in this Phase:

  1. To evaluate the Test completion and prepare Test metrics on the premise of your timeTest coverage, Cost, Software, crucial Business Objectives, and Quality
  2. Documentation of experience get from the project
    Test result analysis to search out out the defect distribution by kind and severity.
  3. Test closure report

Outcomes

  1. Test Closure report and Metrics

 

 

“Related post”

Software Development life cycle

Software Testing Life Cycle

Test Case Documentation

Alpha and Beta Testing

Regression Testing

Smoke and Sanity Testing

Software Testing

Validation and Verification

V-Model

Entry and Exit Criteria in software testing

Integration Testing 

Automation Testing

2 Comments

Leave a Reply to prash p Cancel reply

Your email address will not be published. Required fields are marked *