TPT17 Preview: Automatic Test Case Generation with TASMO – Improved
In TPT 17 generating test cases automatically with TASMO has been improved considerably. Namely, the usability and performance have seen extensive touch-ups.
In TPT 17 generating test cases automatically with TASMO has been improved considerably. Namely, the usability and performance have seen extensive touch-ups.
The testing tool TPT can now read and write ReqIF files which allows for a seamless exchange of requirements and their corresponding meta data.
With TPT 17 you can use TPT in the Cloud, as well. Thanks to this new feature even big testing projects can now be processed within reasonable time.
Prior to the release of TPT 17 we have revamped the TPT API and its corresponding functionalities. API automation and DevOps have been improved.
With the new version of TPT you can control TPT directly from Simulink via the MATLAB toolbox for TPT. This increases the usability of the platforms and makes working on TPT projects a lot easier.
There are many ways to find deficiencies in your system under test (SUT). One method sees defects being intentionally introduced into the SUT. This test strategy is also known as fault injection.
Testing based on requirements and maintaining traceability of requirements are invaluable components of efficient testing and test management. Download our White Paper on the subject, illustrated with the integration of TPT and codebeamer.
The testing tool TPT has developed a new Jenkins plugin, improving the use of TPT via Jenkins. The new plugin now supports pipelines.
Model-in-Loop testing with TPT can now also be done with ASCET-DEVELOPER – the latest platform for software modeling, code generation and simulation developed by ETAS, replacing all ASCET 6.x versions.
If you want to make sure that you have at least one test case per requirement, you can link your requirements in TPT to your test cases. In this tutorial we show you how to do that.