Testing, Preconditions, Coverage and Templates in Safety-Critical C++ Code

By Anthony Williams

Safety Critical code requires extensive testing to verify that the code does what it is supposed to do. This often maps to "code coverage" requirements.

For code that has preconditions, we may want to test that the precondition is checked, and results in the precondition violation handler being called.

For template code, every instantiation of a template is distinct. If your tests exercise a specific instantiation, that doesn’t mean that other instantiations have the same behaviour: there might be template specializations with different behaviour, or the functions found during overload resolution with a different set of template parameters might have different behaviour.

This talk will go into more specifics about these areas, and ways that my team has found to address them.





Your Privacy

By clicking "Accept Non-Essential Cookies" you agree ACCU can store non-essential cookies on your device and disclose information in accordance with our Privacy Policy and Cookie Policy.

Current Setting: Non-Essential Cookies REJECTED


By clicking "Include Third Party Content" you agree ACCU can forward your IP address to third-party sites (such as YouTube) to enhance the information presented on this site, and that third-party sites may store cookies on your device.

Current Setting: Third Party Content EXCLUDED



Settings can be changed at any time from the Cookie Policy page.