Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 3

The different types of Test deliverables are:

Test cases Documents


Test Plan
Testing Strategy
Test Scripts
Test Data
Test Trace-ability Matrix
Test Results/reports

Defect Report
Release notes

A test case is a documentation which specifies input values, expected output and the
preconditions for executing the test.
A test plan is a document describing the scope, approach, objectives, resources, and
schedule of a software testing effort. It identifies the items to be tested, items not be tested,
who will do the testing, the test approach followed, what will be the pass/fail criteria,
training needs for team, the testing schedule etc.

Components of the Test Strategy document
Scope and Objectives
Business issues
Roles and responsibilities
Communication and status reporting
Test deliverability
Industry standards to follow
Test automation and tools
Testing measurements and metrices
Risks and mitigation
Defect reporting and tracking
Change and configuration management
Training plan


Test Plan
Test Plan id
Introduction
Test items
Features to be tested
Features not to be tested
Test techniques
Testing tasks
Suspension criteria
Features pass or fail criteria
Test environment (Entry criteria, Exit criteria)
Test deliverables
Staff and training needs
Responsibilities
Schedule


http://www.tutorialspoint.com/software_testing/testing_documentation.htm


http://agile.csc.ncsu.edu/SEMaterials/BlackBox.pdf

Test Metrix:
It is used to convey progres of our project status report.
Test Procedure coverage: No. of test procedures Vs total number of test procedures execution
Error Density: Total number of errors Vs no. of test procedures execution.
Test Case coverage: Total number of test cases Vs no. of test cases execution and no. of test
cases passed.
Defects: Severity and Priority , time to find defec, time to fix defect , turn around time to
defect.


Release Note : It is a document which specifies the following..

1. Modules currently released
2. unimplemented features
3. known bugs
4.changes with respect to previous release. etc..


There are 2 goals:

1)To improve the quality of product by finding hidden defects.
2)By testing ensure that all customer requirements are full fill in the product.


V model has the following phases and deliverables at each stage

User requirements--- Requirement spec document
System requirements--- Test basis document
Global Design--- Test Design Document
Detailed Design--- Test Procedure Design Document
Implementation--- Test Script and execution`

You might also like