QACampus PPT (STLC)

Click to add Text
Software Testing Life Cycle
www.qacampus.com

Software testing life cycle (STLC) refers to a set of
practices used to test software to ensure its quality as
per the set benchmark or specifications. Also, the STLC
includes the appropriate actions and best timing to carry
out these actions on a software.
Define Software Testing Life Cycle?

Steps involved in STLC process
There are certain practices or steps which are considered
while carrying out effective test on software. These steps
differ in different organizations according to their
requirements. But there are seven standard steps in STLC
process, which includes:
1.Test Panning
2.Test Analysis
3.Test Designing
4.Test Creation and Verification
5.Test plan execution
6.Documentation and Performance testing
7.Practices after test Implementation

Test Planning
This is a phase in which a project manager needs to
prepare a plan by identifying all the areas which needs to
be tested. A plan is developed as per the requirement
and available resources. Planning is not just limited to a
single phase, rather it is a continuous process until
project completes.

A developed test plan thoroughly explain the
following:

Scope of software testing : Identifying, defining the
areas and features to be tested.

Identifying testing approaches : Identifying techniques
which needs to be implemented while testing a project.

Risk defining : Identifying different risks associated with
the developed plan.

Resources identification: Identifying resources like
manpower, machines, and other infrastructure used while
testing a project.

Time Schedule: A project completion time is to be
decided for timely delivery.

Test Analysis
Depending on the developed high level test plan, further
analysis is to be done to identify the test requirement, this
testing phase includes:

Analyzing the types of testing, required to perform during
different SDLC stages.

Identifying the degree to which automation is required to
be done.

Identifying the time at which test automation required to
implement.

Identifying the requirement of documentation for testing
process.

The analysis part also comprises the interaction between the
developers, testing team, business analyst and the client. To
understand the customer requirement a proper interaction between
all these is necessary. Based on this customer interaction meetings
a detailed matrix is prepared to cover all functional validations
including the following areas:
During this it is to be ensured that the prepared test plan is fulfilling
all the business requirements.
It helps in identifying test cases which are best for automated
testing.
It helps in identifying areas on which performance or stress testing
can be carried our.
A detailed review is to be carried out on documentation to ensure
that project meets all the specified design, features, functionality,
and customer requirements.

Test Designing

Further review of different test cases, and test plans.

Finalizing the functional validation test matrix.

Identifying the test cases which will be automated.

Scripts creation for identified test cases for
automation.

Developing test data.

Implementing standards for unit testing with a proper
defined criteria for acceptance.

Finalizing test environment criteria.

Test Creation and Verification

Finalizing test plan and test cases.

Finalizing test creation for decided automation test
cases.

Finalizing performance and stress testing plans.

Providing support to the actual developers for unit
testing efforts.

Logging bug into the bug archive and preparing bug
reports.

Implement integration testing following the reported
defects.

Test Plan Execution

Executing all the test cases until the predefined
requirements meets or no more errors appear in
project.

Repetitive test needs to be done for ensuring the
software meeting its defined specifications. This
includes: test cases execution, bug identification,
reporting, test cases modification, and repeating the
same process until error last.

Executing test cases related to stress and
performance testing.
Reviewing and finalizing the test project
documentation.
Carry out load testing, and acceptance testing with
respect to recovery testing.
Verifying software performance by simulating number
of users to check its stability and strength.
Documentation and Performance Testing

Practices after Test Implementation

Evaluating entire testing process.

Documenting the practices followed during occurrence
of an error in future.

Creating a complete test plan and review to be used in
future project.

Identifying and fixing the newly occurred error on
constant basis.

Conclusion
These are several stages which are considered in
Software Testing Life Cycle. These steps needs to be
followed seriously for ensuring the quality and
performance of software project as per the expected
requirements. Ignoring either of these points may
result into a poor quality of developed software which
in-turn effect the business of company.

QACampus PPT (STLC)

More Related Content

What's hot (20)

Viewers also liked (16)

Similar to QACampus PPT (STLC) (20)

Recently uploaded (20)

QACampus PPT (STLC)