KEMBAR78
Date Change Description: Unit Test Plan | PDF | Software Testing | Unit Testing
Scribd
Upload
248 views2 pages

Date Change Description: Unit Test Plan

This document provides a test plan for unit testing the CAMF0016 module. The plan describes the module under test, the test environment, constraints, process, and milestones. Unit testing will be carried out by testers over 4 weeks to test the functionality and error handling of the module. Test cases will be prepared to satisfy business rules and trap errors. The testing will stop when no new bugs are found or test inputs are exhausted.

Uploaded by

Vikas Salve
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
248 views2 pages

Date Change Description: Unit Test Plan

This document provides a test plan for unit testing the CAMF0016 module. The plan describes the module under test, the test environment, constraints, process, and milestones. Unit testing will be carried out by testers over 4 weeks to test the functionality and error handling of the module. Test cases will be prepared to satisfy business rules and trap errors. The testing will stop when no new bugs are found or test inputs are exhausted.

Uploaded by

Vikas Salve
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Unit Test Plan

Date Version Change description


17-01-2005 1.00 First Release

Project Code: IBMMF/PROD/ Project Name: CAMEX


2004/01/CMX
Unit Plan Id: UTP/CMX-016 Unit Name: CAMF0016
Test Plan Id: UTP/CMX-016 Test Plan Ver. No: 1.00

Change History
Date Version Change description Created/Edited by: Formal review by:
17-01-2005 1.00 First Release SENTHILKUMAR N.JEBARAJ
JEEVARATHINAM

1 . OVERALL PLANNING FOR TESTING

1.1 Description of the Unit


The CAMEX (CONTROL STATEMENTS) test plan provides the tester to list the product
with all possible input conditions and requirements. While testing CAMF0016 MODULE
tester or developer must ensure that all requirements and design documentations are kept in
desired place.
1.2 Test Environment
HARDWARE : IBM Z800.
SOFTWARE : COBOL, JCL.

1.3 Test Constraints


NIL

1.4 Testing Process


UNIT TESTING :
• UNIT Testing refers to testing of a stand alone module by a person other than the
developer who developed that module, the tester is generally a peer.
• The testing will be carried out by the tester and the results are recorded manually.
• Defects identified during testing will be reviewed by peer once the bug status will be set
to CLOSED.
1.5 Milestones
Scheduled dates for UNIT Testing 17-01-2005 through 11-02-2005
(4 weeks)

1.6 Effort Estimates


Estimated Days : 20 days.
2 . UNIT TEST PLAN

2.1 Entry Criteria for the test


• Requirement definition documents and design documents related to the item to be reviewed
• Testing to be carried out as specified in the quality plan.
• Make sure that person carrying out testing or review is well trained on those specific area.

2.2 Conditions to Stop Test


Until there is
• No bug being detected .
• Non availability of test inputs.
• Excessive number of fatal bugs being detected.

2.3 Exit criteria for the Test


The tested and reviewed items are found acceptable.

2.4 Test Cases to be prepared


Test Cases to be prepared fullfiling the following criteria
• Functionality:
Test cases to be prepared to satisfy the business rules and business needs.
• User interface:
N/A.
• Error handling:
The program should be able to trap errors like the absence of Program-Id,
Invalid input value and file errors while opening.

• Import/Export of functions:
N / A..
• Import/Export of data:
N/A.

You might also like