Since RapiTime is based on measurements and testing, good testing is vital for good WCET results.

Generally, we see RapiTime able to provide good results from existing test cases. A customer's existing test suite is normally the first place to start testing from.

The main requirement for testing is to have high code coverage (ideally at least full statement coverage). If existing test cases are insufficient, RapiTime will report untested code, allowing them to be improved, usually by adding extra test cases to the existing test set.

We find that testing at "system test" or any kind of high level "module testing" is the best time to apply RapiTime (although other test scenarios are possible). From analysis of those tests, it is useful to refine or the existing tests. RapiTime can work alongside both automatic test frameworks and manual testing methods.