| |
Test
Latest release of RTDS introduces support of TTCN-3
standard testing language including syntax and semantic verification, simulation, code generation, debug, and graphical traces.
The formal models can be simulated against their related test suites.
The implementation of the model can be tested against the implementation of the test suites.
Traces and breakpoints can be set within the model or within the test suites and stepping
is available on both sides because the bug might be in the model or in the test suite.
A 10 minutes on-line demonstration is available here.
A simple TTCN example flash demonstration
Sample test suite
A TTCN-3 example test suite
The test verdict is displayed in the debugger window and in the graphical execution trace window.
Test verdict in an execution trace
|
|
Continuous integration
TTCN-3 test suites can be used to test the model or its implementation on target.
Automatic testing can be executed on whole or a part of the model or its implementation.
TTCN-3 can be used for unit testing, integration testing, validation testing.
Continuous integration
Easy implementation
The generated code architecture makes integration on target easy and straight forward.
Macros are used for messages going out of the test case, and a chained list of message queues is used for incoming messages.
Easy integration on target
Model coverage
At any time during a test session it is possible to view graphically the model coverage at
any architecture level. You can see how many times a transition has been fired, how many times a state has been reached,
and how many times a symbol has been executed.
Code coverage
Click here to get the brochure
|
|
