Testing and Validation

Each test case must have a header containing descriptive information. It will have the below format and will be inserted at the beginning of the testcase file. Each test-case can have one or more test-units, and their number will be counted in the test case.

Test Case Header

//======================================================================

// Test case name:

// Functional requirement:

// Module(s):

// Object(s):

// Prerequisites:

// Created by/when:

// Modified by/when:

// Testcase description:

//----------------------------------------------------------------------

// Test Unit Number:

// Test Unit Description:

// Input

// Expected Output:

//======================================================================

Where

  • Functional requirement will identify the requirement and its location as being from repository, or functional document, or web page.

  • Module(s) contains name of the module being tested.

  • Object(s) lists the objects presents in the current module.

  • Prerequisites lists the prerequisite component(s) specific to the tested module.

  • Created by/when records creator name and the date of creation.

  • Modified by/when records modification date and name of the change author.

  • Testcase description presents in detail the purpose and objective of the test case.

The start of each test-unit must be marked and documented:

  • Test Unit Number is the count number of the test unit in the current test case.

  • Input represents the set of values that are required for the run of the test-unit.

  • Expected Output presents the desired output of the test-unit.