On the subject of testing formal requirements, we have gone one step further.
Formalized requirements can already be evaluated automatically with TPT today. New: As of TPT 19, the corresponding test data can now be generated with one click.
Is that still testing? Yes, but fully automatically and without the need to create complex test cases.
Do you wonder for what kind of test objects this works?
For everything you can test with TPT: for models (ASCET, Simulink, Targetlink), for generated or handwritten C/C++ code, for AUTOSAR components, ECUs and many more.
The requirements are the basis – you import them with one click. Then formalize the requirements with our own language set – optimized for embedded scenarios. Now a few more clicks and the test report is ready.
Sounds too good to be true?
Just give it a try.
How can this feature help to increase product quality and speed up your testing process?
There are two scenarios how you can use Formal Requirements in your organization:
1. As a fundamental basis for all tests
2. As a supplement to existing tests
Testing of formalized requirements can be combined with other types in the test case creation process as well, like manual test case creation and test data generation.
Whatever you decide – you can support your test team with a reallocation of tasks, for example: experienced requirements managers and developers – instead of testers – could take care of the formalization. The testers can thus focus on classic test automation topics, such as
- the connection of the system under test (SUT),
- additional automation and supplementary tests for higher code coverage (also automatically) for software or
- on load tests for ECUs.