UNIT TEST PLAN <CR ID>

Author:

Brendan Furey

Creation Date:

1 November 2009

Version:

1.1

Last Updated:

84507052.doc

.

Page 1 of 9

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

for example. Whenever possible a generic unit test plan should be followed for testing of generic features of a technology. 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. Change Record Date Author Version Change Reference 1-Nov-2009 BP Furey 1. The template organises the testing into areas that will vary according to the program being tested. test data and test output can often be best presented in tabular format in additional sections for an area. The template is very general and the specific test plan should have any sections added that are deemed necessary. followed by detail records to describe the test steps and record results. with a specific unit test plan (that can be based on this document) for the non-standard features of a program. but an error handling area is included explicitly as this is an area almost always needed (although often overlooked). It corresponds roughly to the TE040 Unit Test Plan in Oracle's Applications Implementation Methodology (AIM).doc Page 3 of 9 .1 Initial 84507052.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. The aim with this structure is to encourage good test coverage by initial analysis. Within each area there is a two-level table with one record for the test scenario. REF-1 gives a generic test plan for Oracle Forms (and could be the basis of one for any Forms technology).

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.doc Page 4 of 9 . 84507052.Introduction Business Purpose The purpose of this document is to specify the testing of a code module.

doc .g. SME) Tester Position (within Company) Test Execution Environment Test Execution Date Tester Signature 84507052. Page 5 of 9 . Super User.General Information Tester Name Tester Role (e.

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 84507052.doc Page 6 of 9 .

doc Page 7 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 84507052.

doc Page 8 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 84507052.

doc Location www.Issues and References Issues # 1 Issue Description Note if closed References REF REF-1 Document Oracle Forms Feneric UTP 84507052. Page 9 of 9 .scribd/BrendanP .

Sign up to vote on this title
UsefulNot useful