You are on page 1of 9

UNIT TEST PLAN <CR ID>

Author: Brendan Furey


Creation Date: 1 November 2009
Version: 1.1
Last Updated:

24315840.doc . Page 1 of 9
Table of Contents

Document Control.............................................................................................3
Foreword.....................................................................................................3
Change Record............................................................................................3
Introduction.......................................................................................................4
Business Purpose.........................................................................................4
Scope...........................................................................................................4
Inclusion............................................................................................................ 4
Exclusion........................................................................................................... 4
General Information..........................................................................................5
Test Area 1........................................................................................................6
Test Area 2........................................................................................................7
Error Handling...................................................................................................8
Issues and References.......................................................................................9
Issues..........................................................................................................9
References..................................................................................................9

24315840.doc Page 2 of 9
Document Control

Foreword
This document provides a template for the unit test plan to be executed on completion of the development
of a program such as a report or a form or an interface. It corresponds roughly to the TE040 Unit Test Plan
in Oracle's Applications Implementation Methodology (AIM).
The template organises the testing into areas that will vary according to the program being tested, but an
error handling area is included explicitly as this is an area almost always needed (although often
overlooked). Within each area there is a two-level table with one record for the test scenario, followed by
detail records to describe the test steps and record results. The aim with this structure is to encourage
good test coverage by initial analysis, followed by focus on the essentials of test scenarios and test steps
without too much of the clutter of unimportant details that one often sees. The template is very general and
the specific test plan should have any sections added that are deemed necessary; for example, test data
and test output can often be best presented in tabular format in additional sections for an area.
Whenever possible a generic unit test plan should be followed for testing of generic features of a
technology, with a specific unit test plan (that can be based on this document) for the non-standard
features of a program. REF-1 gives a generic test plan for Oracle Forms (and could be the basis of one for
any Forms technology).

Change Record

Date Author Version Change Reference


1-Nov-2009 BP Furey 1.1 Initial

24315840.doc Page 3 of 9
Introduction

Business Purpose
The purpose of this document is to specify the testing of a code module.

Scope

Inclusion
These test scenarios cover the following:

Exclusion
The test scenarios exclude the following:
The Integration test scenarios will be covered in a separate document titled [TE050] Integration Test
Cases.

24315840.doc Page 4 of 9
General Information

Tester Name

Tester Role
(e.g. Super User, SME)

Tester Position
(within Company)

Test Execution
Environment

Test Execution Date

Tester Signature

24315840.doc . Page 5 of 9
Test Area 1
# Test Case Description Result/Comments Status
1
# Execution Step Expected/Obtained Results Comments
1
2
3
# Test Case Description Result/Comments Status
2
# Execution Step Expected/Obtained Results Comments
1
2
3
# Test Case Description Result/Comments Status
3
# Execution Step Expected/Obtained Results Comments
1
2
3

24315840.doc Page 6 of 9
Test Area 2
# Test Case Description Result/Comments Status
1
# Execution Step Expected/Obtained Results Comments
1
2
3
# Test Case Description Result/Comments Status
2
# Execution Step Expected/Obtained Results Comments
1
2
3
# Test Case Description Result/Comments Status
3
# Execution Step Expected/Obtained Results Comments
1
2
3

24315840.doc Page 7 of 9
Error Handling
# Test Case Description Result/Comments Status
1
# Execution Step Expected/Obtained Results Comments
1
2
3
# Test Case Description Result/Comments Status
2
# Execution Step Expected/Obtained Results Comments
1
2
3
# Test Case Description Result/Comments Status
3
# Execution Step Expected/Obtained Results Comments
1
2
3

24315840.doc Page 8 of 9
Issues and References

Issues
# Issue Description Note if closed
1

References
REF Document Location
REF-1 Oracle Forms Feneric UTP www.scribd/BrendanP

24315840.doc . Page 9 of 9