Actual Test Coverage for Embedded Systems

    Research output: Contribution to conferenceAbstract

    23 Downloads (Pure)


    Testing embedded systems is inherently incomplete; no test suite will ever be able to test all possible usage scenarios. Therefore, in the past decades many coverage measures have been developed. These measures denote the portion of a system that is tested, that way providing a quality criterion for test suites. Formulating coverage criteria is not an easy task. The measures provided in the literature are consequently almost all very trivial and syntax-dependent. Well-known examples are statement and path coverage in white-box testing, and state and transition coverage in black-box testing. The complexity of designing coverage measures for embedded systems is contained in the highly dynamic behaviour of such systems, which is state-dependent and subject to many interleavings. In this talk we introduce a framework on actual test coverage. This measure denotes the number of faults actually shown present or absent. Our framework contains a method to evaluate the actual coverage of a given set of test suite executions after testing has taken place, providing a means to express the quality of a testing process. It also contains a method to predict the actual coverage a certain number of executions will yield, providing a means to select the best test suite. Both the evaluation afterwards and the prediction in advance are quite efficient, making it feasible to implement the theory in a tool and use it in a practical context.
    Original languageEnglish
    Number of pages2
    Publication statusPublished - 27 Nov 2008
    Event14th Dutch Testing Day - Utrecht, The Netherlands
    Duration: 29 Nov 200829 Nov 2008


    Workshop14th Dutch Testing Day
    Other29 November 2008


    • EWI-20906
    • Embedded Systems
    • EC Grant Agreement nr.: FP7/214755
    • EC Grant Agreement nr.: FP7-ICT-2007-1
    • Coverage Metrics
    • Model-Based Testing
    • IR-78705


    Dive into the research topics of 'Actual Test Coverage for Embedded Systems'. Together they form a unique fingerprint.

    Cite this