Scribd Logo
Upload

Welcome to Scribd!

  • 37 views

    Module ID: - Program ID: - : Unit Test Plan

    Uploaded by

    Alexandre Marius Jacob
    This document outlines a unit test plan for a software module. It includes 1) an overview of the module's purpose, inputs, and outputs, 2) test cases covering valid and invalid data, 3) identification of interfacing modules, 4) test tools used, 5) an archive plan, and 6) how updates to the plan will be identified and tracked. The purpose is to verify the module's processing logic through representative test data and edge cases.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd

    Module ID: - Program ID: - : Unit Test Plan

    Uploaded by

    Alexandre Marius Jacob
    37 views2 pages
    This document outlines a unit test plan for a software module. It includes 1) an overview of the module's purpose, inputs, and outputs, 2) test cases covering valid and invalid data, 3) identification of interfacing modules, 4) test tools used, 5) an archive plan, and 6) how updates to the plan will be identified and tracked. The purpose is to verify the module's processing logic through representative test data and edge cases.

    Original Description:

    Utp Template

    Original Title

    Utp Template

    Copyright

    © © All Rights Reserved

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document outlines a unit test plan for a software module. It includes 1) an overview of the module's purpose, inputs, and outputs, 2) test cases covering valid and invalid data, 3) identification of interfacing modules, 4) test tools used, 5) an archive plan, and 6) how updates to the plan will be identified and tracked. The purpose is to verify the module's processing logic through representative test data and edge cases.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    37 views2 pages

    Module ID: - Program ID: - : Unit Test Plan

    Uploaded by

    Alexandre Marius Jacob
    This document outlines a unit test plan for a software module. It includes 1) an overview of the module's purpose, inputs, and outputs, 2) test cases covering valid and invalid data, 3) identification of interfacing modules, 4) test tools used, 5) an archive plan, and 6) how updates to the plan will be identified and tracked. The purpose is to verify the module's processing logic through representative test data and edge cases.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    of 2

    Unit Test Plan

    Module ID: _________ Program ID: ___________


    1. Module Overview
    Briefly define the purpose of this module. This may require only a single phrase: i.e.: calculates
    overtime pay amount, calculates equipment depreciation, performs date edit validation, or
    determines sick pay eligibility, etc.
    1.1 Inputs to Module
    [Provide a brief description of the inputs to the module under test.]
    1.2 Outputs from Module
    [Provide a brief description of the outputs from the module under test.]
    1.3 Logic Flow iagram
    [Provide logic flo diagram if additional clarity is required.]
    2. Test ata
    !Provide a listing of test cases to be e"ercised to verify processing logic.#
    2.1 Positive Test !ases
    [$epresentative data samples should provide a spectrum of valid field and processing values
    including %&yntactic% permutations that relate to any data or record format issues. 'ach test
    case should be numbered, indicate the nature of the test to be performed and the e"pected proper
    outcome.]
    2.2 "egative Test !ases
    Unit Test Plan
    [The invalid data selection contains all of the negative test conditions associated ith the
    module. These include numeric values outside thresholds, invalid (haracters, invalid or missing
    header)trailer record, and invalid data structures !missing required elements, unknon elements,
    etc.#
    3. Interface Modules
    [*dentify the modules that interface ith this module indicating the nature of the interface:
    outputs data to, receives input data from, internal program interface, e"ternal program interface,
    etc. *dentify sequencing required for subsequent string tests or sub+component integration tests.]
    #. Test Tools
    [*dentify any tools employed to conduct unit testing. &pecify any stubs or utility programs
    developed or used to invoke tests. *dentify names and locations of these aids for future
    regression testing. *f data supplied from unit test of coupled module, specify module
    relationship.]
    $. %rc&ive Plan
    [&pecify ho and here data is archived for use in subsequent unit tests. ,efine any procedures
    required to obtain access to data or tools used in the testing effort. The unit test plans are
    normally archived ith the corresponding module specifications.]
    '. Updates
    [,efine ho updates to the plan ill be identified. -pdates may be required due to
    enhancements, requirements changes, etc. The same unit test plan should be re+used ith revised
    or appended test cases identified in the update section.]

    You might also like