Critical embedded software must often be tested for functional correctness, and must meet the constraints of the hardware it will run on, the first being achieved by a combination of testing methods including unit testing, and the second by timing analysis.
These are often carried out separately by different groups of engineers, with little or no communication between the two.
Being able to produce timing data during unit testing allows timing optimization, and the identification of potential issues, earlier during the development process, particularly if unit tests are run from an early stage.
You can do this using both RapiTest and RapiTime together.
Feature applies to: