Importing Requirements from a codebeamer Baseline into TPT
TPT 18 also brings some new features in handling the application lifecycle tool codebeamer. In the new version you can now import requirements from a specific baseline.
TPT 18 also brings some new features in handling the application lifecycle tool codebeamer. In the new version you can now import requirements from a specific baseline.
Discover TPT 18 with a wide range of new features, including MC/DC, formalized requirements, more automation features and Simulink test execution that is up to ten times faster.
With TPT18 you can add a formal notation for each requirement. You can have the so-called Formal Requirements checked automatically during each test run. Watch the tutorial.
Formal requirements differ from natural language requirements in that they use a predefined language to convey the same meaning.
In our tutorial on codebeamer and TPT we show you how to export test cases from TPT back to codebeamer.
In our tutorial on codebeamer and TPT we show you how to do import requirements and test cases and how to export test results in a few simple steps.
The testing tool TPT can now read and write ReqIF files which allows for a seamless exchange of requirements and their corresponding meta data.
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.
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.
It might sound trivial: The central goal of testing is to check whether a system does what it was designed for. How that goal is achieved, however, is already a bit less obvious. The answer lies in requirements-based testing – a central testing method for testing with TPT.