Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 1 of 15
1. Introduction
This document helps to perform requirement unit testing using Tessy 3.1.11
Goal is to validate the software module against the software design requirement specification.
2. Preparation to perform Requirement Based Unit Test
Map the software implementation folder to O: drive
Create and keep all tessy applications in below path only:
D:\svn\3002904_MSB_EL_AU651\trunk\05_EDP\40_Test\40_Component\10_C_SW\30_DATA\
SW03 (SW03 folder will change as per SW baseline)
Project Configuration to create a new project is shown below. Do not enable source root while creating
a new project.
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]
Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 2 of 15
Module must be restored before starting the black box unit testing by selecting the preferences and
requirements as shown below.
2.1 Environment Configuration:
Set the following in the Environment configuration as shown below:
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]
Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 3 of 15
2.2 Source and Compiler settings:
Add source by providing appropriate path.
Make sure compiler Include paths are added.
Make sure only required source
Module is added for Testing. The
module shown here is only for
Click on Edit symbol to add the example. In general only one source
include path as required for the module to be added.
project.
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]
Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 4 of 15
2.3 Define settings:
2.4 Coverage Settings:
C1 = 80% others as 0%
2.5 Required function selections:
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]
Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 5 of 15
3. Defining the Interfaces:
3.1 TIE – Test Interface Editor: In Tessy 3.1, Test Interface Editor Perspective shows all the
interfaces. By default Tessy will define the interface directions. But these interfaces to be
re-checked and re-defined as per the requirements.
This section will give some general rules to define the interfaces.
a. For IN parameters, make Report flag to Yes.
b. For OUT parameters, make Report flag to Yes.
c. Parameters which are not used must be made IRRELEVENT and Report flag is set to No.
d. For INOUT parameters, make Report flag to Yes.
Consider the following priority to stub the functions.
No stub required – Example: memset, strcmp, strnicmp, wcsicmp
Create advanced stub – This means that, outputs (return value) of this function is required,
but it can be unique for each test case (Test data to be given each test case).
Note: Sometimes user code is not required. This means that functionality of this particular
function call will not affect the requirement under test.
Create stubs only for current objects
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]
Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 6 of 15
3.2 TDE - Text Data Editor: Text Data Editor is used to enter and edit the test data inputs to the test
cases.
3.2.1 TDE Settings:
Add new test case with proper and maintainable test case name.
Follow Action-Objective-Expectation approach for testcase name as per SW Design
specification.
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]
Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 7 of 15
3.2.2 Properties of Testcases:
Description: This field is filled properly as per Testers comments about test data or test design
technique or test method to make clear idea about test case for reviewer.
Specification: This field is filled properly if required else it is kept blank.
Comment: Update Defect description here.
TestCase Level Test Object Level
3.2.3 Function call check
To check whether a function is called, the below steps are followed :
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]
Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 8 of 15
[Link] Declarations/Definitions
To track the function call, a variable is declared and defined at test object level in
Declarations/Definitions tab with format [Name of the function called]_called.
[Link] Stub code
Stub code is written at test case level with format [Name of the function called]_called
=TS_CURRENT_TESTCASE;
[Link] Epilog :
Epilog is written at test step [Link] function call is checked.
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]
Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 9 of 15
4. Linking Requirements to Test Cases:
After writing the test cases, the given requirements are linked to the corresponding test cases and
this is also called as Requirements mapping.
Below figure shows the list of requirements available for the particular module.
When a testcase is selected, requirements available for mapping is shown in requirement coverage
in TDE. The below figure shows the the testcase which is not mapped.
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]
Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 10 of 15
After mapping the requirement :
Used to filter the mapped Update the testcase and
Requirements requirement mappings(save)
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]
Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 11 of 15
5. Edit Test Execution Settings:
1. Set Instrumentation: Test Object Only.
1. Select Test Cases seperately in executing options.
2. Coverage settings: Select coverage settings as shown in below screenshot. And execute test.
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]
Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 12 of 15
6. Report generation:
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]
Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 13 of 15
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]
Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 14 of 15
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]
Tech Mahindra WORK INSTRUCTION DOCUMENT
Date of Change: Revision: Page
Title
Requirement Based Unit Testing using Tessy 3.1.11 21-Dez-25 1.0 15 of 15
6.1 TBS File generation:
After selecting test objects, proper paths, report options and requirements, settings are saved and
hence TBS file is generated which has the settings selected during report [Link] file is
stored in Backup folder.
To open TBS file To save TBS file (save as)
To save TBS file
Which is already generated
Above figure shows the files in Tessy Backup folder.
© 2004 All rights reserved by TAKATA-PETRI NVD 022-1 / 0 / 020402 /conversion/tmp/activity_task_scratch/[Link]