What is the Cantata RTRT Converter?
The Cantata RTRT Converter is a direct tool to tool automatic conversion of IBM Rational® Test RealTime .ptu test scripts for C code into the Cantata test script format. It allows organisations who have invested substantial resources over time using RTRT to automatically migrate tests to the modern Cantata tool without losing that investment
Read the comprehensive Cantata Feature Brief: RTRT Converter
To arrange a demonstration or a free trial of the Cantata RTRT Converter, please contact us.
RETAIN ORIGINAL TEST SCENARIOS
Through a fine-grain understanding of the C code under test and the associated RTRT ptu syntax, logic and test data, the Cantata RTRT Converter ensures the same test pre-conditions, test driver data, processing logic, call simulations, checks and post-conditions are all retained in the conversion. A comprehensive mapping log is produced for each test script converted, and Cantata coverage analysis ensure the same levels of code coverage are achieved.
ENSURE TEST MAINTAINABILITY AND ENABLE EXTENSIBILITY
The Cantata RTRT Converter ensures 100% of all identifiable elements (including names and comments) from the ptu test scripts are automatically mapped to their equivalents in Cantata test scripts. In addition, the Cantata Makefiles are automatically generated to build and execute the converted test scripts.
Extensibility of tests is enabled by the converted Cantata test scripts and Makefiles being fully editable in the Cantata Test Script Manager UI or any C code editor, and by accessing the rich set of Cantata features compatible with the tests generated from the RTRT converter.
RETAIN TEST ENVIRONMENT AND ACCELERATE EXECUTION
Cantata can be deployed to any target environment for which RTRT tests were configured, re-using parts of RTRT Target Deployment Packages (TDPs).
When benchmarked, the converted Cantata tests execute 3 times faster than RTRT.
Why convert RTRT tests to Cantata?
RTRT is a legacy testing tool no longer actively maintained by IBM. If you feel stuck with the limitations of your legacy testing tool, you may wish to consider the advantages of moving on to a modern replacement such as Cantata.
Any tool migration will come at a cost to the organisation, so the potential benefits of a new tool must outweigh these costs. Here are some of the benefits of converting from RTRT® to Cantata:
LOWER TESTING COSTS
GREATER TOOL RELIABLITY AND COMPATIBILITY
Where a legacy tool interacting with other tools holds back the complete toolchain, the impact can affect developer productivity beyond the impact of the test tool alone.
MEET CURRENT TOOL CERTIFICATION REQUIREMENTS
Current safety standards tool certification or qualification requirements for test tools are not supported by RTRT, but are by Cantata.
“This migration tool offers RTRT users an alternative to upgrades and also the difficulty of maintaining older versions. We recommend this solution to our customers and we support them in its deployment.”
Nathaël Nedelec, EASA qualified, Eurogiciel Engineering
How does it work?
Cantata makes use of an internal representation of the code under test and the test script (Test Script Model). This model provides an interface to almost any intermediate testing language (e.g. the PTU syntax used by IBM Rational® Test RealTime scripts), and provides the required information for an end-to-end test script conversion. The process works as follows:
The entry point to the conversion which maintains overall control of the process.
Creates the Parser object, and initiates the parse of the selected PTU script. This will read all statements and constructs within the PTU creating an understanding of the content and storing it in memory using the unique Cantata Model representation.
This is the internal representation of the input PTU script, and the interface between the old PTU and the new Cantata C test script.
The functions to be tested are calculated by using Cantata’s knowledge of the software under test, combined with the understanding of functions called by Elements in the PTU.
For every source file being tested, a new Cantata test script is generated using the normal Cantata generation mechanism.
The generated Cantata test script is updated with all Service, Test, and Element entries from the PTU in the form of Cantata Test cases and functions. Stubs and Environments are added/set up for each created test case. Each test case is then set up with the inputs, outputs and checks as defined from the PTU
The updated Cantata test script is then written to disk together with a mapping log file for the conversion.