Establishment of a CT Factory Based on HIL Farm
Hyundai Mobis – Costumer Success Story
SDV Verification and Test Automation
Providing a Continuous Testing (CT) environment that simultaneously ensures quality and speed through a CI/CD-based automated evaluation system and large-scale HIL parallel verification.
CI/CD-Driven Automated Evaluation
A fully automated evaluation framework was established to trigger testing for every software build. This enables earlier issue detection and significantly shortens feedback loops in the development process.Centralized Test Data Management
Test history, execution time, and evaluation results are systematically structured and centrally managed, allowing test strategies to evolve based on data rather than intuition.Scalable Parallel HIL Validation
A pool-based resource model enables parallel execution of HIL tests, increasing throughput and providing the flexibility required to handle growing test cases and expanding system domains.
About Hyundai Mobis
As a global auto parts vendor, we focus on autonomous driving, connectivity and electrification to be a leader in the era of smart mobility. Based on three modular auto components (i.e. chassis, cockpit and front-end), we work to make driving safer and easier and also offer service parts that can best serve the purpose.
Our vision is to be a provider of differentiated mobility solutions that combine software and hardware in the upcoming mobility industry. To make this vision a reality, we have expanded our business areas to include smart mobility, UAM and robotics based on our R&D capability and production capacity.
Why is a Continuous Testing (CT) environment necessary?
As vehicle software and electronic systems become increasingly complex in the SDV era, development organizations must meet shorter release cycles while maintaining higher quality standards.
Continuous Testing (CT) addresses this challenge by embedding validation directly into the development pipeline, transforming testing from a downstream activity into an integral part of daily development.
Challenges in the Field
- Rapid growth in product variants (OEMs, regions, vehicle models, powertrains)
- Compressed validation schedules due to shorter software release cycles
- Constant trade-offs between test duration and test coverage
What Is a CT Factory?
A CT Factory is an integrated, automated, and intelligent testing environment designed to support continuous software validation.
It connects multiple test domains and tools into a unified system and links them directly to the CI/CD pipeline, enabling immediate evaluation(Build → Test → Report) after every build.
Before Implementation
- Testing performed mainly upon explicit validation requests
- Partial automation existed, but operations remained largely manual
- Test results and operational data were scattered and difficult to reuse
After Implementation
- Automated evaluation executed for every software build
- Increased test frequency enabling earlier detection of defects
- Centralized data supporting strategic optimization of testing operations
The Role of the Vector HIL Farm
The Vector HIL Farm serves as the core hardware validation hub of the CT Factory:
- Automated HIL testing based on real ECUs
- Pool-based resource management enabling large-scale parallel validation
- A scalable infrastructure that supports domain expansion and long-term growth
Design Principle: Full Automation
From pipeline trigger to final reporting, human intervention was minimized by design. Decision points previously handled manually were transformed into structured data and system logic.
Standardization
Clear design principles for test cases enable reuse and consistency.
Structuring
Test assets – models, configurations, and reports – are organized according to unified rules, reducing operational complexity.
Automation
CI/CD integration enables a seamless flow from trigger to execution, data collection, and reporting.
Practical Challenges and Solutions
Integration of Legacy Tools
Some legacy tools lacked external control interfaces. Where possible, CLI- and REST-API-based control mechanisms were extended to integrate them into the CT environment.
Hardware Resource Constraints
A pool-based operating model minimized resource conflicts and maximized parallel execution efficiency.
Operational Impact
- Faster and more flexible test strategy execution through automation and integration
- Shortened test cycles driven by increased test frequency and earlier issue detection
- Clearer role separation and improved collaboration following DevOps principles
