Software Test Process

Software Test Process / STLC

Test Process may vary from one company to another and one project to another, but as per industry standards there is a 4 levels of Test Process available.
-----------------------------------------------------------------
 Quality Standards Organizations:

ISO (International Organization for Standards),

ISO has provided so many terms and guidelines for Software Testing


IEEE (Institute of Electrical and Electronics Engineers),

IEEE has provided  so many terms (Terminology) and Test documentation standards like Test Plan, Test Specification, Transmittal Report, Test Case Specification, Incident Report and Test Summary Report etc...

CMM/CMMI (Capability Maturity Model Integration),

CMMI has Provided Test process guidelines.

and some other Non-Government Organizations have provided the
the Standards for the IT Industry.
 --------------------------------------------------------------
4 Stages of Software Test Process

I) Test Planning

(Primary Role: Test Lead/Team Lead)
         
Input:/Reference:
-----------------
a) Requirements specification
b) Test Strategy
c) Project plan
----
d) Use cases/design docs/Prototype screen
e) Process Guidelines docs


Templates:
----------
Review Report

Test Plan

Roles:
------

Test Lead/team Lead: Test Planning

Test Engineers: Contribution to Test plan
---------
BA: Clarifications on Requirements


Tasks:
-------

          a) Understanding & Analyzing the Requirements
          b) Test Strategy Implementation
          c) Test Estimations (Time, Resources-Environmental, Human, Budget)
          d) Risk Analysis
          f) Team formation
          g) Configuration management plan
          h) Test Plan Documentation
          i) Test Environment set-up defining

Output:
-------           

Test Plan Document
----------------------------------------------------
                  
II) Test design:
----------------

Input:/Reference:
-----------------
a) Requirements specification
b) Test Plan
----
d) Use cases/design docs/Prototype screen
e) Process Guidelines docs

Templates:
----------
Test Scenarios

Test case

Test data

Roles:
------
Test Engineers: Test case documentation

Test Lead/team Lead: Guidance, monitoring & Control

---------
BA: Clarifications on Requirements


Tasks:
------
          a) Creating Test scenarios
          b) Test case documentation
          c) Test data collection

Output:
-------
Test case Documents
Test Data

--------------------------------

             
3) Test Execution:
-------------------

Input:/Reference:
-----------------
a) Requirements specification
b) Test Plan
c) Test Case docs
d) Test data

----
e) Test Environment


Templates:
----------
Defect Report
Test Report

Roles:
------

Test engineers: Test execution

Test Lead: Guidance, monitoring & Control
----------

BA: Clarifications on Requirements

System Administrator/Network Administration: Test Environment set-up
         

Tasks:
-------           
          a) Forming Test Batches
          b) Verifying Test Environment set-up
          c) Test Execution
          d) Test reporting
          e) Defect Reporting
          f) Regression Testing

Output:
-------
Test Reports
Opened/Closed Defect Reports

           
         
4) Test Closure

Input:/Reference:
-----------------
Requirements
Test Plan
Test Reports
Opened/Closed Defect Reports

Templates:
----------
Test Summary Report

Roles:
Test Lead: decide when to stop testing & Creating Test summary Report
Testers: Contribution


Tasks:
-------           
          a) Evaluating Exit criteria
          b) Collecting all facts from Testing activities
          c) Sending Test deliverables to the Customer
          d) Improvement suggestions for future projects

Output:
-------

Test Summary Report
Test Deliverables (Test Plan, Test scenarios, Test cases, Test Data, Test Reports, Opened/Closed defect Reports, Test Summary Report)
***********************************************************


Documents to be created and used for Software Testing:

a) Test Policy (Company Level)



A high level document describing the principles, approach and major objectives
of the organization regarding testing.

b) Test Strategy (Company Level)


A high-level description of the test levels to be performed and the testing within those levels for an organization or programme (one or more projects).
c) Test Plan (Project Level)



A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning. It is a record of the test planning process.

d) Traceability Matrix

A traceability matrix is a document, usually in the form of a table, that correlates any two baselined documents that require a many to many relationship to determine the completeness of the relationship. 

e) Test Case



A set of input values, execution preconditions, expected results and execution
Post-conditions, developed for a particular objective or test condition, such as to exercise a particular program path or to verify compliance with a specific requirement.

f) Test Data



Data that exists (for example, in a database) before a test is executed, and that affects or is affected by the component or system under test.

g) Defect Report



A document reporting on any flaw in a component or system that can cause the
component or system to fail to perform its required function.


h) Review Report

i) Test Summary Report



A document summarizing testing activities and results. It also contains
an evaluation of the corresponding test items against exit criteria.

Etc...
------------------------------------------

1 comments:

Post a Comment