Lector: Aleksandar Karamfilov

Skype: sanders_kar
E-mail: aleksandar.karamfilov@pragmatic.bg
Facebook: http://www.facebook.com/aleksandar.karamfilov.1
LinkedIn: bg.linkedin.com/in/akaramfilov/

Copyright © Pragmatic LLC 2013 – 2014

The Software Testing Life
Cycle
Software testing life cycle (STLC) identifies what
test activities to carry out and when (what is the
best time) to accomplish those test activities. Even
though testing differs between organizations,
there is a testing life cycle.
 Planning and Control
 Analysis and Design
 Implementation and execution
 Evaluation of exit criteria and reporting
 Test closure activities
 The Test Plan describes how the Test Strategy is
implemented
 A project plan for testing
 Defines what is to be tested, how is to be testing,
what is needed for testing etc.
 The most critical stage of the process
 Effort spent now will be rewarded later
 The foundation on which testing is built
 Usually requires heavy involvement from QA Lead
or QA Manager
1. High Level Test Plan
(includes multiple test cycles)

2. Quality Assurance Plan

3. Identify when reviews will be held.

4. Problem Reporting Procedures

5. Identify Problem Classification.

6. Identify Acceptance Criteria - for QA and Users

8. Identify measurement criteria, i.e. defect
quantities/severity level and defect origin (to name
a few).

9. Identify metrics for the project

10. Begin overall testing project schedule (time,

resources etc.)
11. Review Product Definition Document

- Help determine scope issues based on Features of

the Product

- 5 - 10 hours / month approximately

12. Plan to manage all test cases in a database,

both manual or automated.
Can be viewed as three step process:
 Preparation and analysis
 Building test cases
 Defining expected results
 Analyze the Application(software)
 Identify test conditions
 Identify test cases
 Document it well
 Cross-referencing with specification and other
sources
 Test case assembling
 Standing data
 Defining Transaction data
 Defining Actions
 Expected results
 More(see list with activities)
 Test Execution Schedule/Log
 Identify which tests are to be run
 Prepare test environment
 Prepare test data
 Back-up and recovery of the environment
procedure ready and in place.
 Batch runs(if we have) ready and in place
 More(see list with activities)
Have we fulfilled the Test Exit Criteria?
 Exit Criteria Body:
 Key functionality tested
 Test coverage
 Budget used
 Defect detection rate
 Performance satisfactory
• When testing is over the testing project can be
closed
• Documents should be updated and put under
version control
• The exact way depends on your company policy
and standards.
We should understand the
SDLC and STLC in order to
do our job properly!