What we deliver
Test strategy and plans
Test level per requirement across MIL, SIL, HIL and vehicle, coverage targets by ASIL, and ASPICE SWE.4 to SWE.6 and SYS.4 to SYS.5 work products.
MIL, SIL and HIL test suites
Back-to-back MIL/SIL tests, virtual ECU regression in CI and HIL suites with restbus and fault injection. More on HIL/SIL testing.
ADAS scenario catalogues
Logical and concrete scenarios in ASAM OpenSCENARIO with OpenDRIVE road networks, parameter sweeps and Euro NCAP 2026 test cases for SIL and HIL execution.
Network and diagnostic tests
CAN FD, LIN and Automotive Ethernet (SOME/IP, DoIP) communication tests, UDS (ISO 14229) services, DTC handling, network management and gateway routing.
Safety verification evidence
Requirements-based tests, fault-injection results and structural coverage that feed the ISO 26262 safety case and SOTIF validation.
Cybersecurity and OTA tests
Security function tests, fuzzing and penetration tests for R155, and update tests for R156: interrupted downloads, rollback, version checks and RXSWIN records.
How we work
01
Review requirements
Check testability, allocate each requirement to MIL, SIL, HIL or vehicle, and agree pass criteria with your system and safety leads.
02
Set up environments
Configure models, virtual ECUs, restbus and scenario tooling, or adapt your existing HIL rigs and CI runners.
03
Specify and automate
Write test specifications, implement them in ecu.test, vTESTstudio, CANoe or Python, and peer-review them before execution.
04
Execute and triage
Run campaigns per software release, analyse failures with developers and track defects to closure in your ALM.
05
Report for audit
Publish traced results and coverage in the form your ASPICE assessor, safety assessor or type-approval authority expects.
Test areas, standards and evidence
| Test area | Standards and protocols | Typical evidence |
|---|---|---|
| ECU software (MIL/SIL/HIL) | ISO 26262-6, ASPICE SWE.4-SWE.6 | Unit and integration test reports, branch or MC/DC coverage, HIL regression reports |
| ADAS functions | ISO 21448 (SOTIF), ISO 34502, ASAM OpenSCENARIO, UNECE R171, Euro NCAP 2026 protocols | Scenario catalogue, parameter-space coverage, triggering-condition analysis, results per scenario |
| Networks and diagnostics | CAN FD (ISO 11898-1), Automotive Ethernet, UDS (ISO 14229), DoIP (ISO 13400) | Communication matrix tests, diagnostic specification tests, trace logs |
| Cybersecurity | ISO/SAE 21434, UNECE R155 | Cybersecurity test specification, fuzzing and penetration test reports, findings tracked to closure |
| Software updates | UNECE R156 | OTA test results, rollback and recovery tests, configuration and RXSWIN records |
Where this fits
This page covers automotive testing as a whole. HIL test bench setup covers specifying and commissioning rigs, cybersecurity testing covers R155 fuzzing and penetration testing in depth, and test automation covers frameworks and CI. ECUs under test often come from our AUTOSAR, ADAS and sensor fusion and EV and BMS work, and the wider picture is on the testing & validation hub.
Standards
- ASAM OpenSCENARIO
- ASPICE
- AUTOSAR Classic
- ISO 21448 (SOTIF)
- ISO 26262
- ISO 34502
- ISO/SAE 21434
- UNECE R155
- UNECE R156
- UNECE R171
Toolchains our engineers work with
- dSPACE SCALEXIO
- dSPACE VEOS
- ecu.test
- esmini
- IPG CarMaker
- MATLAB/Simulink
- NI VeriStand
- Vector CANoe
- Vector vTESTstudio
- VectorCAST
Related work
Case studies →Fuzz and penetration testing an industrial gateway for the Cyber Resilience Act and IEC 62443-4-2
A recurring security test cycle for an industrial gateway: fuzzing, penetration tests and SBOMs mapped to IEC 62443-4-2 and the CRA.
Planning MIL-STD-810H and MIL-STD-461 pre-compliance for an indigenised rugged subsystem
Tailoring MIL-STD-810H and 461 requirements, writing procedures, running pre-scans and preparing a rugged LRU for its accredited lab campaign.
Closing DO-178C structural coverage with independent verification for a DAL B component
Independent verification closes statement and decision coverage, coupling analysis and tool qualification for a DAL B software component.
Further reading
All insights →Hiring AUTOSAR and SDV engineers in India in 2026–27: skills, notice periods and ramp planning
Where AUTOSAR and SDV engineers are in India, the skills worth screening for, and how to plan around 60–90-day notice periods.
Building an engineering or test team for a mid-market GCC in India
Ramp waves, dedicated team vs Build-Operate-Transfer, governance and the measures that matter for a mid-market GCC's engineering or test team.
Euro NCAP 2026 ADAS Testing: What Changes for SIL/HIL Test Plans and Test Capacity
Euro NCAP 2026 multiplies ADAS test variations. How to restructure SIL/HIL plans around ISO 34502 and OpenSCENARIO, and plan the capacity.
Frequently asked questions
What testing does UNECE R155 type approval require?
R155 requires the manufacturer to show, per vehicle type, that risks identified in the risk assessment are mitigated and that the measures have been tested for effectiveness. In practice this means a cybersecurity test specification, functional tests of security controls, fuzzing and penetration testing of exposed interfaces, and findings tracked to closure. Suppliers provide component evidence under ISO/SAE 21434 that the OEM uses in its type-approval file.
How do Euro NCAP 2026 changes affect ADAS validation?
Euro NCAP's 2026 protocols are its biggest overhaul since 2009, adding ADAS robustness, HMI and driver-monitoring assessments. Test-equipment vendor AB Dynamics reports more than 1,200 ADAS test variations, roughly double the previous cycle. That volume pushes most variants into SIL and HIL scenario testing, with track tests kept for confirmation, so scenario catalogues and simulation capacity need planning early.
Which standards define scenario-based ADAS testing?
ISO 34502:2022 sets out a scenario-based safety evaluation framework for automated driving systems on limited-access highways. ASAM OpenSCENARIO describes the dynamic content of scenarios and ASAM OpenDRIVE the road network, so the same scenario can run in different simulators. ISO 21448 (SOTIF) drives the search for triggering conditions, and UNECE R171 sets requirements for driver control assistance systems.
What structural coverage does ISO 26262 expect at unit level?
ISO 26262-6 highly recommends statement coverage for ASIL A and B, branch coverage for ASIL B to D and MC/DC for ASIL D. Coverage is measured on requirements-based tests, and gaps are analysed: missing tests are added and unreachable or defensive code is justified. VectorCAST, Tessy or LDRA typically produce the reports.
How is OTA update testing done for UNECE R156?
Tests cover the update chain end to end: package signing and verification, preconditions such as battery and vehicle state, interrupted downloads and installs, rollback to the previous version, user notification and correct update of RXSWIN records. Tests run first on HIL or bench setups with the backend simulated, then on vehicles for campaign-level confirmation.
Do you work on our HIL rigs or provide your own?
Usually on yours, because a HIL configuration is specific to the ECU, I/O and vehicle network. Engineers configure, extend and automate dSPACE, NI and Vector benches, on site or remotely where your IT policy allows. If you need a new rig, HIL test bench setup covers specification, integration and commissioning.
Can we hire automotive test engineers instead?
Yes. We recruit HIL, ADAS validation, diagnostics and test automation engineers on contract, contract-to-hire or permanent terms. See automotive engineers and hire test engineers for how candidates are screened on hands-on tool and standards experience.
Tell us your domain, standard and team size — get a scoped brief in 2 minutes.