Software Testing - Life Cycle
Software Testing - Life Cycle
Features of STLC
The features of STLC are listed below −
STLC begins from the time requirements are shared from the client’s side.
STLC is a methodical approach to achieve software quality.
What is STLC?
Typically, the STLC should begin right from the start of the project when the requirements
have been shared by the customers. It is introduced to make the testing process more
methodical.
In the beginning stages of the STLC, the testers are mostly involved in analyzing the
requirements and coming up with a plan and a strategy to test the software thoroughly.
Thus the initial phases of the STLC mainly involve defining the periphery of testing, how
much testing is to be done, looking for scopes to reduce the test cycle without
compromising the quality etc. At this time, the developers are mostly involved in creating
the software from scratch. The test plan and test strategy are the deliverables at the early
stages of the STLC.
Based on the test plan, and test strategy, a collective decision is made by the project
stakeholders on the testing approaches to be taken, tools to be used for testing,
resources, environments, scopes, skills needed for the team, the timelines, percentage of
manual and automation test cases etc. Then, the test team identifies the probable use
cases, scenarios, data, and other details required to create the test cases involving all the
requirements. As all these items are approved and reviewed by the product stakeholders,
the focus of the test team shifts to actually building the test cases.
A Requirement Traceability Matrix (RTM) is made to map every requirement to at least one
test case and to ensure all possible scenarios - positive, negative, and edge are covered.
As the software development has been completed, the testing team begins verifying it.
The detailed execution of test cases results in detecting defects and verifying if all the
features of the software are working as expected.
Page 2 of 4
Explore our latest online courses and learn new skills at your own pace. Enroll and
become a certified expert to boost your career.
Requirement Analysis
In the requirement analysis phase of the STLC, the requirements are shared to the team
by the clients. Then the testing team goes through these requirements, analyzes them,
and comes up with the planning and strategizing of the testing process. It is very
important to have a proper test plan and strategy in place for ensuring quality software.
Test Planning
In the test planning phase of the STLC, the project managers and leads come together
and come up with a test plan. These documents contain information on the items in scope,
out of scope, budget, approach, methodologies, tasks of individual team members,
estimations, number of testing cycles, team size, tools, additional resources, percentage of
automation and manual testing efforts etc.
Test Strategizing
In the test strategizing phase of the STLC, the project managers and leads come together
with a strategy document. Once a test strategy document has been developed, it is
normally not changed till the project end. In the test strategizing phase, mainly the
protocolos and methods to be adopted for testing are finalized.
Environment Identification
In the environment identification phase of the STLC, the correct environment in which
software is to be verified is identified. A normal sanity check to ensure that it meets the
minimum requirements to test the software should be done before starting the testing
process.
test coverage and software quality. Also, RTM, and all standard test processes, and
principals are followed in this phase.
Defect Logging
In the defect logging phase of the STLC, all the defects detected during the execution
phase are documented, triaged, fixed, and brought to proper closure.
Test Closure
In the test closure phase of the STLC, all the detailed reports on test execution (count of
test cases, passed, failed, percentage of failure, impacted modules, defects etc), and
metrics are documented, and shared with all project stakeholders.
STLC is an important step towards ensuring if the software being developed is as per the
functional and non-functional requirements. It is seen that a high quality software needs
less maintenance efforts in future. The STLC ensures that the software is stable, usable,
reliable, has all the security features, good performance etc. In short, to make the
software relevant in the industry for a long time, STLC is a very important step.
Conclusion
This concludes our comprehensive take on the tutorial on Software Testing Life Cycle.
We’ve started with describing what is a STLC, various stages of the STLC, what role does
the STLC play in SDLC, and what is the entry and exit criteria in STLC. This equips you
with in-depth knowledge of the Software Testing Life Cycle. It is wise to keep practicing
Page 4 of 4
what you’ve learned and exploring others relevant to Software Testing to deepen your
understanding and expand your horizons.