Tessy is an eclipse based testing tool used for automated unit or integration testing of embedded software. It has different views or perspective for entering test data, requirement management and also provides detailed code coverage reports. As a test tool TESSY supports all industry-leading compilers,debuggers and microcontrollers as well as host simulation.
The classification tree editor (CTE) provides one method of systamatically specifying test cases. It makes use of classification tree method to do this, and a unique feature of tessy
KEY FEATURES:
·Automated Test Execution.
·Test Report Generation.
·Code Coverage Without Extra Effort.
·Regression And Integration Testing.
·Traceability Of Requirements To Test Cases.
·Qualified for Safety-related Software Development.
·Testing On Host Or Actual Hardware.
UNIT AND MODULE TESTING:
During unit testing of C programs, a single C-level function is tested rigorously, and is tested in isolation from the rest of the application. Rigorous means that the test cases are specially made for the unit, and they also comprise of input data that may be unexpected by the unit under test. Isolated means that the test result does not depend on the behavior of the other units in the application.
Tessy also be used to test a collection of C functions as a module and hence perform Integration testing and Component testing on them.
INTEGRATION TESTING:
The component test feature within TESSY supports testing of several functions (representing the software component) that interact with themselves as well as with underlying called functions (of other components). The main difference to unit testing of individual functions is the focus of testing on the external interface of the component instead of internal variables or control flow. The component test feature allows creating calling scenarios of functions provided by a software component. Within these scenarios, the internal values of component variables and any calls to underlying software functions can be checked. TESSY provides the Scenario Editor (SCE) for this purpose. All scenario-related inputs are available through the SCE. Instead of having individual test objects and test cases for the component functions, the component test itself provides a special node called “scenarios” seen as one test object. The test cases belonging to the scenarios node are the different scenarios for the component.
