Code coverage

What does less than 100 percent code coverage mean?

Assuming that you adopt the approach of requirements-based testing, code coverage allows you to demonstrate that: Every requirement is implemented in code; Code implements only what the requirements describe. So what does it mean if you don’t achieve 100% code coverage? It could be:
Read More

4 key benefits of structural coverage for DO-178B systems

Sometimes the value of performing structural coverage (AKA code coverage) is questioned. When it’s performed as an end in itself, this might be true, but when it’s used to show the effectiveness of requirements-based testing, there are some really strong benefits.
Read More

What’s the point of code coverage?

Testing has to satisfy two objectives: it has to be effective, and it has to be cost-effective. Testing is effective if it can distinguish a correct product from one that is incorrect. Testing is cost-effective if it can achieve all it needs to do at the lowest cost (which usually means the fewest tests, least amount of effort and shortest amount of time).
Read More

An introduction to Modified Condition/Decision Coverage (MC/DC)

Modified Condition/Decision Coverage (MC/DC) is a method of ensuring adequate testing for safety-critical software. At its core lies the idea that if a choice can be made, all the possible factors (conditions) which contribute to that choice (decision) must be tested.
Read More

Code coverage for applications running on Windows

I was recently asked by a customer if they could use RapiTime to analyse a program compiled for Windows using GCC and CygWin. The answer, with a few caveats, is yes!
Read More