Your browser does not support JavaScript! Skip to main content
Free 30-day trial Customer portal Careers DO-178C Handbook
 
Rapita Systems
 

Industry leading verification tools & services

Rapita Verification Suite (RVS)

  RapiTest - Unit/system testing   RapiCover - Structural coverage analysis   RapiTime - Timing analysis (inc. WCET)   RapiTask - Scheduling visualization   RapiCoverZero - Zero footprint coverage analysis   RapiTimeZero - Zero footprint timing analysis   RapiTaskZero - Zero footprint scheduling analysis

Multicore verification

  MACH178   Multicore Timing Solution   RapiDaemons

Services

  V & V Services   Qualification   Training   Tool Integration  Support

Industries

  Aerospace (DO-178C)   Automotive (ISO 26262)   Space

Other

  RTBx   Mx-Suite   Software licensing   Product life cycle policy  RVS development roadmap

Latest from Rapita HQ

Latest news

Danlaw Acquires Maspatechnologies - Expanding Rapita Systems to Spain
Rapita co-authored paper wins ERTS22 Best paper award
A look back on Rapita's Multicore DO-178C training in Huntsville
RVS 3.17 Launched
View News

Latest from the Rapita blog

Why mitigating interference alone isn’t enough to verify timing performance for multicore DO-178C projects
There are how many sources of interference in a multicore system?
Supporting modern development methodologies for verification of safety-critical software
Flexible licensing software fit for modern working
View Blog

Latest discovery pages

do178c DO-178C Guidance: Introduction to RTCA DO-178 certification
matlab_simulink MATLAB® Simulink® MCDC coverage and WCET analysis
code_coverage_ada Code coverage for Ada, C and C++
amc-20-193 AMC 20-193
View Discovery pages

Upcoming events

Aerospace Tech Week Europe 2023
2023-03-29
Certification Together International Conference
2023-05-10
View Events

Technical resources for industry professionals

Latest White papers

DO178C Handbook
Efficient Verification Through the DO-178C Life Cycle
A Commercial Solution for Safety-Critical Multicore Timing Analysis
Compliance with the Future Airborne Capability Environment (FACE) standard
View White papers

Latest Videos

Efficient DO-178C verification - WCET analysis
Efficient DO-178C verification - Code coverage
Efficient DO-178C verification - Functional testing
SCADE Test video thumbnail
Complementary DO-178C verification with Ansys(R) SCADE Test(TM) and RVS
View Videos

Latest Case studies

Supporting ISO 26262 ASIL D software verification for EasyMile
RapiCover’s advanced features accelerate the certification of military UAV Engine Control
Front cover of whitepaper collins
Delivering world-class tool support to Collins Aerospace
View Case studies

Other Downloads

 Webinars

 Brochures

 Product briefs

 Technical notes

 Research projects

Discover Rapita

Who we are

The company menu

  • About us
  • Customers
  • Distributors
  • Locations
  • Partners
  • Research projects
  • Contact us

US office

+1 248-957-9801
info@rapitasystems.com
Rapita Systems, Inc.
41131 Vincenti Ct.
Novi
MI 48375
USA

UK office

+44 (0)1904 413945
info@rapitasystems.com
Rapita Systems Ltd.
Atlas House
Osbaldwick Link Road
York, YO10 3JB
UK

Spain office

+34 930 46 42 72
info@rapitasystems.com
Rapita Systems S.L.
Parc UPC, Edificio K2M
c/ Jordi Girona, 1-3, Office 306-307
Barcelona 08034
Spain

Working at Rapita

Careers

Careers menu

  • Current opportunities & application process
  • Working at Rapita
Back to Top

If RapiTime provides Ipoint coverage, why do I need RapiCover?

Breadcrumb

  1. Home
  2. Blog
  3. If RapiTime provides Ipoint coverage, why do I need RapiCover?
2013-10-09

Users of RapiTime will probably be aware that one of the categories of information shown in a RapiTime report is "Ipoint Coverage". So, given that RapiTime supplies coverage information, why do you need RapiCover?

The answer relates to the way this information is intended to be used, and also the sections of the source code that it relates to.

What is the purpose of RapiTime's Ipoint coverage measurement?

At first glance, RapiTime provides coverage information, i.e. an indication of how much code was exercised during testing. However, there is a specific motivation behind RapiTime’s display of coverage data.

RapiTime's analysis is carried out at the basic block level - as part of the process it generates a control-flow graph representing all the possible paths through all the blocks in the software. It then inserts instrumentation at the scope boundaries to allow it to calculate the execution time of each basic block. By a combination of analysing all the possible paths through the code, and measuring the execution time for each basic block, RapiTime is able to calculate a worst-case execution time value for the software.

In order to ensure this value is accurate (in particular, to make sure that the WCET is not optimistic) the software must be adequately exercised during the testing. As a minimum, to obtain an accurate WCET value it is necessary to have executed each basic block of code at least once. As each Ipoint is associated with a single block of code, we can tell how effectively the code has been exercised by reporting the number of executed and un-executed Ipoints. This is reason behind the Ipoint coverage measurement shown in the RapiTime report.

So why do I need RapiCover?

Typical coverage tools provide information on so-called "structural coverage metrics" - that is, the coverage information is associated with particular elements of the source code structure. Typical structural elements include functions, statements and decisions. Software developed at the highest levels of criticality is tested for coverage at MC/DC level, which requires that the effect of each condition that can contribute to the outcome of a decision must be observed during testing. Structural code coverage information is used to confirm that software has been adequately exercised during testing, and it is this type of coverage measurement, up to and including MC/DC, that RapiCover is intended to provide.

screenshot showing RapiCover structural coverage

Figure 1: RapiCover structural coverage

Because RapiTime’s Ipoint coverage is reported at the basic block level it is not possible to use it to determine structural coverage using any of the traditional metrics (other than function coverage). RapiCover inserts instrumentation to allow it to calculate structural coverage for the chosen metric. Typically, this requires more instrumentation than is necessary for timing, located at different points in the source code. The execution traces generated by instrumentation provide you with code coverage metrics which identify which sections of code are either untested or covered by unnecessary test cases.

DO-178C webinars

DO178C webinars

White papers

DO178C Handbook Efficient Verification Through the DO-178C Life Cycle
A Commercial Solution for Safety-Critical Multicore Timing Analysis
Compliance with the Future Airborne Capability Environment (FACE) standard
5 key factors to consider when selecting an embedded testing tool

Related blog posts

False positive and false negative in software testing

.
2019-05-22

1000 conditions per decision ought to be enough for anybody

.
2019-01-28

Code coverage without instrumentation

.
2018-10-18

Merging coverage data from multiple test runs

.
2017-01-31

Pagination

  • Current page 1
  • Page 2
  • Page 3
  • Page 4
  • Page 5
  • Page 6
  • Next page Next ›
  • Last page Last »
  • Solutions
    • Rapita Verification Suite
    • RapiTest
    • RapiCover
    • RapiTime
    • RapiTask
    • MACH178

    • Verification and Validation Services
    • Qualification
    • Training
    • Integration
  • Latest
  • Latest menu

    • News
    • Blog
    • Events
    • Videos
  • Downloads
  • Downloads menu

    • Brochures
    • Webinars
    • White Papers
    • Case Studies
    • Product briefs
    • Technical notes
    • Software licensing
  • Company
  • Company menu

    • About Rapita
    • Careers
    • Customers
    • Distributors
    • Industries
    • Locations
    • Partners
    • Research projects
    • Contact
  • Discover
    • AMC 20-193
    • What is CAST-32A?
    • Multicore Timing Analysis
    • MC/DC Coverage
    • Code coverage for Ada, C & C++
    • Embedded Software Testing Tools
    • Aerospace Software Testing
    • Automotive Software Testing
    • Certifying eVTOL
    • DO-178C
    • WCET Tools
    • Worst Case Execution Time
    • Timing analysis (WCET) & Code coverage for MATLAB® Simulink®

All materials © Rapita Systems Ltd. 2023 - All rights reserved | Privacy information | Trademark notice Subscribe to our newsletter