What we deliver
Test strategy
Which requirements are verified at MIL, SIL with virtual ECUs, HIL or vehicle level, with coverage targets matched to ASIL and ASPICE SWE.6 and SYS.5 expectations.
Plant and scenario models
Vehicle, powertrain, battery and sensor models in MATLAB/Simulink or IPG CarMaker, and ADAS scenarios in ASAM OpenSCENARIO, validated for real-time execution.
Bench configuration
I/O mapping, restbus simulation, fault-injection units and bus interfaces for CAN FD, LIN and Automotive Ethernet on HIL rigs.
Test automation
Automated test cases in ecu.test, CANoe test units or Python, run from CI with results traced to requirements.
Diagnostic and network tests
UDS (ISO 14229) and DoIP diagnostic tests, network management, gateway routing and timing checks.
What each X-in-the-loop stage verifies
| Stage | System under test | Typical purpose |
|---|---|---|
| MIL | Control model in Simulink with plant model | Early algorithm verification against requirements |
| SIL | Generated or hand-written code on a PC | Back-to-back testing against the model, code coverage, fast regression |
| PIL | Code on the target processor or evaluation board | Compiler, numeric and timing effects of the target |
| HIL | Real ECU with simulated plant and network in real time | I/O, diagnostics, fault injection and integration before vehicle tests |
How we work
01
Analyse requirements
Review testability, assign each requirement to a test level and agree pass criteria.
02
Build the environment
Set up models, bench configuration and restbus, or adapt your existing HIL rig.
03
Write and automate tests
Specify test cases, implement them in your automation framework and peer-review them.
04
Execute and triage
Run campaigns, analyse failures with developers and track defects to closure.
05
Report and maintain
Publish traceable reports and keep regression suites current as software changes.
What is changing in HIL and SIL validation
Testing is moving earlier. OEMs increasingly ask Tier-1s for virtual ECUs and FMI-based model exchange, so software is tested in SIL and in CI before it reaches a rig and HIL capacity is freed for the tests that need hardware. HIL remains the final gate, because SIL cannot cover interaction with real sensors, actuators and electrical faults. Cloud-connected HIL centres are also appearing, including in India.
Investment in rigs continues alongside virtual validation. One estimate, from Global Market Insights, puts the hardware-in-the-loop testing market at $1.27 billion in 2025, rising to $2.61 billion by 2034; MarketsandMarkets gives a lower estimate of $1.10 billion in 2025 and $1.78 billion by 2030.
ADAS validation is becoming scenario-based. Euro NCAP's 2026 protocols are its biggest overhaul since 2009, adding ADAS robustness, HMI and driver-monitoring tests, and test-equipment maker AB Dynamics reports more than 1,200 ADAS test variations, roughly double the previous cycle. UN Regulation No. 171 on driver control assistance systems (DCAS) entered into force on 22 September 2024, with its 01 series of amendments binding from 26 September 2025. ISO 34502 sets out a scenario-based safety evaluation for automated driving systems, and ASAM OpenSCENARIO describes scenarios in a tool-neutral format that can run in SIL and on HIL.
Where this fits
HIL and SIL work is part of our automotive testing service. Rigs are built and commissioned through HIL test bench setup, and connected to CI through test automation. For the background on rigs and real-time simulation, see the HIL testing glossary entry. ECUs under test often come from our AUTOSAR and EV and BMS work.
Standards
- ASAM OpenSCENARIO
- ASPICE
- AUTOSAR Classic
- ISO 21448 (SOTIF)
- ISO 26262
- ISO 34502
- MISRA C
- UNECE R171
Toolchains our engineers work with
- dSPACE SCALEXIO
- dSPACE VEOS
- ecu.test
- IPG CarMaker
- MATLAB/Simulink
- NI VeriStand
- Python
- Vector CANoe
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
Do you provide HIL rigs or work on ours?
Usually we work on yours or on rigs you procure, because HIL configurations are specific to the ECU, I/O and vehicle network. Our engineers configure, extend and maintain dSPACE SCALEXIO, NI VeriStand and Vector-based benches, and can access them remotely where your IT policy allows. Hardware access is agreed when the engagement is scoped.
Which test automation tools do your engineers use?
The common ones are tracetronic ecu.test, dSPACE AutomationDesk, Vector CANoe test units and vTESTstudio, NI TestStand and Python frameworks such as pytest. We fit into the framework your programme has standardised on and connect it to your CI server and requirements tool.
Can testing run offshore if the HIL rig is in Europe or the US?
Often, yes. Test design, automation and SIL execution run from Bengaluru, and HIL campaigns run remotely on your rig through a secured connection, with local staff handling cabling and hardware changes. Some programmes add a mirrored rig in Bengaluru when remote access becomes the bottleneck.
Do we need HIL if we already run virtual ECUs in CI?
Yes, for most safety-relevant ECUs. Virtual ECUs in SIL give fast, scalable regression and catch most logic errors early, but they do not exercise real I/O, analogue signal conditioning, electrical faults, hardware timing or the production bootloader. A good split runs the bulk of functional regression virtually and keeps HIL for integration, fault injection and release testing.
What structural coverage do you measure in SIL?
Statement, branch and MC/DC coverage, depending on the ASIL. At unit level, ISO 26262-6 (Table 9) highly recommends statement coverage for ASIL A and B, branch coverage for ASIL B to D, and MC/DC for ASIL D. We measure with VectorCAST, Tessy, LDRA or your coverage tool and document justifications for unreachable code.
How do Euro NCAP 2026 changes affect ADAS validation?
Euro NCAP's 2026 protocols add ADAS robustness, HMI and driver-monitoring assessment, and the number of test variations has grown sharply. Running every variation on a track is impractical, so programmes build scenario catalogues, often in ASAM OpenSCENARIO, run them in SIL and on HIL with sensor models, and keep track tests for confirmation. The same scenario approach supports UN R171 DCAS evidence.
How do you test safety mechanisms on HIL?
Through fault injection: shorts to battery and ground, open loads, sensor out-of-range values, lost or corrupted bus messages and timing faults. Each test checks that the ECU detects the fault within the fault tolerant time interval and reaches the safe state defined in the ISO 26262 safety concept.
Can we hire HIL and test engineers directly?
Yes. For contract, contract-to-hire or permanent HIL, SIL and test automation roles, see hire test engineers. Candidates are screened on test design, automation scripting, hands-on rig experience and how they produce test evidence for ISO 26262 and ASPICE.
Tell us your domain, standard and team size — get a scoped brief in 2 minutes.