Services
Unit Testing for Safety-Critical Software.
Our engineers design and run unit tests for embedded software in automotive, aerospace, railway, medical and industrial programmes, mostly with VectorCAST. Tests come from the design, coverage meets the level the standard sets, and every result is traced in your ALM. We support teams in Belgium, the Benelux, across Europe and beyond.
How We Test
Test Strategy
A design-based test method, a test harness, a stub library for the basic software, and coverage targets set by the integrity level of each unit.
Test Design
Test cases derived from the detailed design, so that each test checks what the unit is meant to do.
Automation
Unit tests run in the CI/CD pipeline on every change, next to static analysis, and a merge gate blocks a change whose tests fail or whose coverage falls short.
Coverage Analysis
Statement and branch coverage at the lower levels, MC/DC where the standard requires it. Each unit is judged against its own level, so an average never hides a shortfall.
Evidence
Results written into your ALM, whichever you use, and linked to the design element each test verifies, ready for the assessment.
For legacy code without a detailed design, we review each unit and either accept it on its existing evidence or reverse-engineer the design and test it like new code.
VectorCAST, and the Tools You Already Use
Most of our unit testing is done in VectorCAST: harness generation, stubbing, coverage up to MC/DC and regression runs in the pipeline. When your project is built on another tool, we work in that tool.
Main tool. VectorCAST. Also. LDRA, Parasoft, Tessy, TPT, GoogleTest. Pipelines. Jenkins, GitLab CI, GitHub Actions. Static analysis. MISRA C/C++, Coverity. ALM. Polarion, Codebeamer, IBM DOORS, Jama Connect, Jira.
What Each Standard Asks For
- Automotive
ISO 26262-6, ASPICE SWE.4 - Software unit verification by ASIL, with structural coverage up to MC/DC at ASIL D, and the unit verification evidence an ASPICE assessor reviews.
- Aerospace
DO-178C - Requirements-based tests with structural coverage by software level, up to MC/DC for DAL A.
- Railway
EN 50716, EN 50128 - Component testing with the test coverage the standard sets for each software safety integrity level, strictest at SIL 4.
- Medical and industrial
IEC 62304, IEC 61508-3 - Unit verification for class B and C medical device software, and module testing by SIL for industrial safety functions.
Case Studies
Design-to-Test Traceability Between Enterprise Architect and Codebeamer
Unit tests derived from the design, with a regression suite that grows with each change request, as evidence for ASPICE SWE.4 and ISO 26262-6.
Read the case studyCI/CD Pipelines for Embedded Software
Static analysis, unit tests and integration tests run the same way at every stage, with results traceable in the ALM.
Read the case studyUnit testing is one stage of the XWARE Software Factory, which connects it to the design, the pipelines and the quality gates.
