Data Structure
Networking
RDBMS
Operating System
Java
MS Excel
iOS
HTML
CSS
Android
Python
C Programming
C++
C#
MongoDB
MySQL
Javascript
PHP
Physics
Chemistry
Biology
Mathematics
English
Economics
Psychology
Social Studies
Fashion Studies
Legal Studies
- Selected Reading
- UPSC IAS Exams Notes
- Developer's Best Practices
- Questions and Answers
- Effective Resume Writing
- HR Interview Questions
- Computer Glossary
- Who is Who
Software Testing Life Cycle (STLC) Phases
The Software Testing Life Cycle (STLC) is a term that refers to the process of testing software.
The Software Testing Life Cycle (STLC) is a set of actions that are carried out during the testing process to guarantee that software quality objectives are satisfied. Both verification and validation are part of the STLC process. Software testing is not merely a single/isolated operation, contrary to the common notions. It comprises a set of operations that are carried out in a methodical manner to assist with the certification of your software product. Software Testing Life Cycle (STLC) is an acronym for Software Testing Life Cycle.
This guide will teach you how to −
Phases of the STLC
Analysis of Requirements
Test Preparation
Development of Test Cases
Setup of the Test Environment
Execution of the Test
Closure of the Test Cycle
Phases of the STLC, as well as Entry and Exit Criteria
Phases of the STLC
Every Software Testing Life Cycle Model (STLC Model) has the following six key phases −
Analysis of Requirements
Test Preparation
Creating test cases
Setup of the Test Environment
Execution of the Test
Closure of the Test Cycle
What are STLC's Entry and Exit Criteria?
Entry Criteria − The required things that must be done before testing can begin are listed in Entry Criteria.
Exit Criteria − The elements that must be done before testing may be finished are defined by exit criteria.
All phases of the Software Testing Life Cycle contain Entry and Exit Criteria (STLC)
In an ideal world, you would not go to the next step until the previous stage's departure conditions had been satisfied. However, this is not always achievable in practice. As a result, we'll concentrate on activities and deliverables for the various stages of the STLC life cycle in this lesson. Let's take a closer look at them.
Phases of Requirement Testing
Requirement Phase Testing, also known as Requirement Analysis, is a process in which a test team examines requirements from a testing standpoint to determine testable requirements, and the QA team may communicate with multiple stakeholders to gain a thorough understanding of the requirements. Functional or non-functional requirements are both possible. The testing project's automation viability is also determined at this point.
Requirement Phase Testing Activities
Determine the sorts of tests that will be done.
Collect information about testing priorities and emphasis.
Make a Matrix of Requirement Traceability (RTM).
Determine the details of the test environment in which the testing will take place.
Analyze the viability of automation (if required).
Requirement Phase Testing Deliverables
RTM
Report on the viability of automation (if applicable)
STLC Test Planning
In the STLC, Test Planning is the phase in which a Senior QA Manager defines the test plan approach, as well as the project's effort and cost estimations. Also determined are the resources, test environment, test constraints, and testing timetable. In the same step, the Test Plan is created and completed.
Planning Activities for Tests
Test plan/strategy document preparation for various types of testing
Choosing a test tool
Estimation of the test effort
Organizing resources and identifying roles and responsibilities
Requirement for education
Test Planning Deliverables
A document containing a test plan/strategy.
Document for estimating effort.
The phase of developing test cases
Following the completion of the test strategy, the Test Case Development Phase entails the design, verification, and revision of test cases and test scripts. The Test data is first selected, then prepared, examined, and modified in accordance with the preconditions. The QA team then begins the process of creating test cases for specific units.
Activities to Develop Test Cases
Create test cases and scripts for automation (if applicable)
Test cases and scripts are reviewed and baselined.
Make some test data (If Test Environment is available)
Test Case Development Deliverables
Scripts and test cases
Data from the tests
Setup of the Test Environment
The software and hardware circumstances under which a work product is evaluated are determined by the Test Environment Setup. It is an important part of the testing process and can be completed concurrently with the Test Case Development Phase. If the development team supplies the test environment, the test team may not be involved in this task. A readiness check (smoke testing) of the provided environment is needed of the test team.
Setup Activities for the Test Environment
Prepare a hardware and software need list for the Test Environment by understanding the required architecture, setting up the environment, and understanding the required architecture.
Set up the test data from the tests and the environment
Carry out a smoke test on the structure.
Test Environment Setup Deliverables
Test data is put up and the environment is ready.
Results of the Smoke Test.
The phase of Test Execution
The testers do the test execution phase, in which they test the software build using the test plans and test cases that have been generated. Test script execution, test script maintenance, and defect reporting are all part of the process. If bugs are found, they are reported to the development team for rectification, and retesting is done.
Execution Activities for Tests
Carry out the tests as planned.
Test results should be documented, and any failed instances should be logged as defects.
In RTM, map defects to test cases.
Retest the Fixes for Defects
Follow up on the issues until they're resolved.
Test Execution Deliverables
RTM has been completed and the execution status has been set.
Test cases have been updated with the findings.
Reports of flaws
Closure of the Test Cycle
The Test Cycle Closure phase encompasses numerous operations such as test completion reporting, the collecting of test completion matrices, and the analysis of test findings. Members of the testing team meet, discuss, and review testing artifacts in order to develop tactics that must be applied in the future, based on the current test cycle's lessons. The goal is to eliminate bottlenecks in the process for future test cycles.
Closure of the Test Cycle
Time, test coverage, cost, software, critical business objectives, and quality are all factors to consider when evaluating cycle completion requirements.
Prepare test metrics depending on the characteristics listed above.
Keep track of what you learned through the project.
Prepare a test conclusion report.
Reporting to the client on the quality of the work output in both qualitative and quantitative terms.
Analysis of test results to determine the defect distribution by kind and severity.
Closure of the Test Cycle Deliverables
Report on the completion of the test
Metrics for testing
| STLC Stage | Entry Criteria | Activity | Exit Criteria | Deliverables |
|---|---|---|---|---|
| Analysis of Requirements |
|
|
|
|
| Test Preparation |
|
|
|
|
| Test Case Development |
|
|
|
|
| Setup of the Test Environment |
|
|
|
|
| Execution of the Test |
|
|
|
|
| Closure of the Test Cycle |
|
|
|
|
940 Views
