30min: Qt C++ and QML Code Coverage
Measure the degree of your testing
Code coverage is a metric for the degree of testing that is being done. This talk will explain the various metrics from Statement Coverage to Modified Condition/Decision Coverage (MC/DC), depict their strengths and drawbacks and show how to deal with the challenges posed by Qt C++ and QML code.
Software safety standards like ISO 26262 (road
vehicles), EN 50128 (railway applications) an DO-178 C (airborne systems) and others require software developers to ensure software quality through analysis of code coverage achieved through their tests. Among other measures. This talk will define what this metric means and - equally important - what it does not mean.
Standard levels measured are statement coverage, branch coverage, decision coverage and the more complex modified/condition decision coverage (MC/DC) or multiple condition coverage (MCC). We'll look at the advantages and drawbacks of these levels and what kind of testing efforts they require.
Above topics will be illustrated through some live demonstrations with different tools. The automated Qt tests will serve as a relatively large real-world example for viewing test coverage. Based on selected spots in the code we'll investigate gaps in current QA measures.
Dynamic analysis like code coverage has to be distinguished from static analysis. Nevertheless, some classic static code metrics will be listed as their monitoring is also recommended by the safety standards listed at the beginning.
At the end efforts and benefits of code coverage will be compared with pragmatic recommendations for every day usage.
Start time: 16:45
Track: Testing and Continuous Integration
Click here to let us know how you liked this event.