AUTOSAR Testing with Reactis

Video Description

Automatically generate comprehensive test suites for AUTOSAR components using Reactis. This video demonstrates the complete workflow for testing an AUTOSAR atomic software component through an adaptive cruise control example: import the ARXML model, generate a minimal runtime environment (RTE), create C harnesses for runnables, generate test suites, and execute tests on your C code. For Simulink users, learn how to validate your code against the model through back-to-back testing and debug both simultaneously in lock-step.

Step 1: ARXML Import & Setup

Start by importing the component's ARXML files through the Reactis for C AUTOSAR import tool. Reactis generates a minimal RTE, a Makefile, and C harness files that specify each runnable's inputs, outputs, and configuration variables. The import wizard automatically proposes mappings between engineering objects and C sources, detects runnables, and compiles everything so your component is ready to test.

Step 2: Test Configuration & Generation

Next, open the harness editor to configure your test environment. Review the inferred items: initialization and entry functions, sample period, inputs, outputs, and configuration variables. Set input ranges to guide test generation toward meaningful values, configure error checks and coverage metrics, then generate a comprehensive test suite. Reactis produces compact suites that exercise your coverage targets and runs them in Reactis Simulator to produce detailed reports showing runtime errors, output differences, and when each coverage target was exercised.

Step 3: Back-to-Back Testing (Simulink)

For components modeled in Simulink, use back-to-back testing to validate your implementation. Create matching harnesses for the model in Reactis for Simulink and your C code in Reactis for C, then apply the same test suite to both. Reactis automatically compares actual C outputs against model-derived expected outputs, generating difference reports and plots when mismatches occur.

Step 4: Synchronized Debugging

When differences appear, connect Reactis-for-C and Reactis-for-Simulink for synchronized debugging. Execute both model and code in lock-step: click a model block to highlight the corresponding C code, set synchronized breakpoints, and inspect signals and variables side-by-side. This two-way traceability makes root-cause analysis efficient for diagnosing runtime errors and validating code behavior.

Verifiable Artifacts & Compliance

The workflow produces comprehensive, verifiable artifacts ready for integration, regression testing, and compliance verification. Generated test suites (.rst files) and HTML reports provide audit evidence documenting the absence of runtime errors and coverage achievements across both your model and code.