Code Coverage Insights

Code Coverage Insights

The following examples show what information can be inferred from the live code coverage view at-a-glance without stopping the CPU, using break-points or modifying code:

Inferred time duration

Example #1 – Inferred time duration

Multi-conditionals

Example #2 – Multiple conditionals on separate lines

Only one mutex created

Example #3 – Only 1 mutex created

Blocked thread

Example #4 – Blocked thread

No device errors

Example #5 – No device errors

Uninitialised code

Example #6 – Uninitialised code

Example #7 – Spurious ADC conversions

Eliminate re-runs

The code coverage information is always available for every line that has (and has not) executed. When an event occurs, especially an intermittant one, having the execution history available for analysis as in the above examples often eliminates the need to re-run the code to catch the event again with a break-point. This is yet another way that QTrace saves development time.