Skip to main content
Magline joins Rapita Trailblazer Partnership Program to support DO-178 Certification
Eve Air Mobility joins Rapita Systems Trailblazer Partnership Program for eVTOL projects
Rapita Systems launches MACH178 Foundations for multicore DO-178C compliance
Collins Aerospace and Rapita present award winning paper at DASC 2024
Data Coupling Basics in DO-178C
Control Coupling Basics in DO-178C
Components in Data Coupling and Control Coupling
The ‘A’ Team comes to the rescue of code coverage analysis
DO-278A Guidance: Introduction to RTCA DO-278 approval
ISO 26262
Data Coupling & Control Coupling
Verifying additional code for DO-178C
DO-178C Multicore In-person Training (Fort Worth, TX)
DO-178C Multicore In-person Training (Toulouse)
RapiTest lets you stub (replace or modify) functions in your source code in multiple ways. While these terms may be used differently by various members of the critical software industry, RapiTest supports the following types of behavior:
- Stub – the original function is replaced with a function that returns a fixed value. The inputs of this function can be checked.
- Mock (or spy) – the original function is called, but its inputs and outputs are checked.
- Fake – the original function is replaced with a complex function that imitates the behavior of the replaced function. This can include complex logic.
While RapiTest supports all of these behaviors, it does not make a distinction between them. It stubs functions to represent the behavior specified in test cases.
RapiTest stubs include a wide variety of functionality, including letting you check how many times a stubbed function is called during a test.
Feature applies to:
