Unit testing on target debuggers [1] [2] Contact  

 

The test system Tessy offers automated module testing of C and C++ code directly on the target system using standard debugging technology. It supports the whole unit testing cycle and works transparently on all supported target debuggers.

Tessy includes the Classification Tree Editor CTE [Test system - Tessy] for Test Case Specification. CTE has a direct interface to Tessy and allows to assign values for variables of the test object interface within the classification tree. You can export all test items and the assigned test data into the test database of Tessy.

Tessy @ CTE

Tessy builds up the complete test driver including the necessary module environment and controls the testing process. It allows systematic and reproducible testing in batch mode as well as step by step execution using all available debugging features of the target system. This enables really easy debugging with test data from previously failed test cases.

Tessy analyzes the source code and recognizes the usage of variables and their respective types. The interface information is stored separately from the test data and expected values. This enables Tessy to use browser editors for interface settings and data input.

Tessy supports C1, MCC, MC/DC coverage measurement. The results of every coverage measurement can be reviewed in a coverage viewer in form of a flowchart.

coverage viewer

Tessy supports test documentation in various formats, e.g. XML, HTML, Word, Excel, CHM.

standardized test reporting

On interface changes (during regression testing of new builds), test data may easily be re-used after assignment of the changed to the old interface.

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).

 

 
------------------------------------------------------------------------------------------------------------------
top © 2009 Razorcat Development GmbH :: errors and omissions excepted :: updated 07/24/2009