Parasoft Logo

WEBINAR

Watch Modernizing Software Testing for Embedded Systems in SDVs

Cars are no longer defined by engines and steel but by the intelligence of their software. As vehicles evolve into software-defined systems, testing must evolve too, becoming continuous, automated, and intelligent to meet modern safety and compliance demands.

Key Takeaways

  • Shift testing left to catch defects early using static analysis and automated unit testing.
  • Build safety, security, and compliance into your CI/CD-driven development workflow.
  • Leverage AI and machine learning to prioritize issues, recommend intelligent fixes, and simplify compliance reporting.
  • Extend open-source frameworks like GoogleTest for safety-critical verification and validation.

As Cars Evolve, Testing Must Too

The biggest shift in automotive engineering is the move to software-defined vehicles. Cars are no longer just mechanical systems, they’re powered by millions of lines of code connecting ADAS, powertrain, and infotainment into one dynamic ecosystem. This complexity creates enormous testing challenges that traditional methods can’t handle.

Modern vehicles demand testing that’s automated, continuous, and intelligent to keep pace with constant updates and evolving software. With AI and machine learning now driving critical functions, verification must ensure predictable, safe behavior. Combined with strict standards like ISO 26262 for safety and ISO 21434 for cybersecurity, testing can’t be a final step, it must be a continuous, lifecycle process that even extends beyond the showroom through over-the-air updates.

Embracing Modern Testing Practices

Modern testing for software-defined vehicles starts with a “shift left” approach, finding issues early with static analysis and automated unit testing. Tools like C/C++test CT help verify code as it’s written, ensuring safety and reliability from the start. Tests can also be generated automatically, linked to requirements, and checked for coverage.

With CI/CD automation and AI-powered insights, testing is now continuous and intelligent. Every code change is analyzed instantly, compliance stays up to date, and AI helps prioritize fixes—keeping pace with the speed and complexity of modern automotive software.

Breaking Down Silos with Agile and DevOps

Modern testing thrives in environments that encourage collaboration and transparency. Frameworks like Scrum keep teams aligned and adaptable, while DevOps pipelines automate builds, tests, and analysis in a continuous loop.

DevOps workflows and CI/CD pipelines ensure quality is verified continuously, from code commit to deployment, breaking down silos between development, QA, and compliance. The result is a unified, data-driven workflow that boosts productivity, reduces risk, and accelerates innovation.

Core Testing Methods for Quality

Several core testing methods are crucial for ensuring code quality:

  • Static Analysis: This is the first line of defense, finding coding defects, security vulnerabilities, and compliance issues before code runs. For automotive, using both MISRA C++ 2023 and AUTOSAR C++ 14 together is recommended. Standards like CWE also help find security weaknesses early.
  • Unit Testing, Integration Testing, System Testing, and Regression Testing: These methods, performed continuously, verify functionality and stability at different development stages.
  • Code Coverage Measurement: Tools measure statement, branch, and MCDC coverage, depending on the system’s safety requirements.
  • Reporting and Analytics Dashboards: These consolidate results from all testing activities, providing a real-time view of software quality, compliance status, and release readiness.

Extending GoogleTest for Safety-Critical Development

GoogleTest is a favorite among C++ developers for its simplicity, but on its own, it falls short of safety-critical requirements. Parasoft C/C++test CT bridges that gap by integrating with GoogleTest to meet the rigorous demands, of ISO 26262.

Here’s how it works:

  1. Automated Coverage Metrics: C/C++test CT collects detailed coverage metrics (line, branch, MC/DC, and more) from GoogleTest executions.
  2. Requirement Traceability: It automatically links test cases to requirements in ALM tools (like Doors Next, Jira, Polarion), eliminating manual tracking.
  3. CI/CD Integration: Testing and code coverage are integrated into CI/CD pipelines, catching regressions early.
  4. Automated Compliance Reporting: C/C++test CT generates documentation for test executions, coverage, and traceability, saving hours of manual work during audits.

This transforms unit testing from a simple task into a strategic activity that supports safety and compliance goals. Using GoogleTest as an open-source framework means you’re not locked into proprietary tools, offering flexibility while still meeting safety-critical requirements with integrated solutions. Parasoft is also working on offering fully certified tools for safety-critical development soon.

The Role of AI in Testing

AI is making testing smarter, faster, and more efficient. Here are some key ways they’re being used:

  • Prioritization: ML models analyze historical project data (like past defects, code complexity, and violation types) to predict which violations are most likely to cause critical defects or safety risks.
  • Auto-Fix Suggestions: AI can analyze code violations, explain its reasoning, and suggest corrections directly within the editor.
  • AI-Powered User Support: An AI assistant, similar to ChatGPT, provides contextual answers to user questions directly within the IDE.
  • AI-agents and MCP servers: Empower AI-agents to autonomously or assistively analyze and act on code quality issues.

AI in Automotive Systems

AI is making vehicles smarter, with features like lane keeping, adaptive cruise control, and even autonomous driving. However, deploying AI in cars comes with challenges, such as the “blackbox dilemma” that makes ISO 26262 compliance difficult, and the need for AI to run on embedded hardware with limited resources.

To address this, AI models are being compressed (e.g., from 32-bit to 4-bit precision) and optimized for specialized hardware. Standards like ISO/PAS 8800 guide the development of safe and certifiable AI for vehicles. Verification is crucial, involving model optimization, rigorous testing, and robust system design. Optimized AI models are often “frozen” to ensure consistent behavior, paired with rule-based guardrails to prevent unsafe actions, and use redundancy systems for resilience. Platforms like Nvidia’s Drive are enabling deterministic AI behavior in production vehicles, used by major automotive OEMs.

Best Practices for Safety and Security

Building safe and secure SDVs means combining proven methodologies with modern automation. ISO 26262 guides hazard and risk analyses, while UN R155 and R156 set cybersecurity assurance frameworks. ISO 21434’s TARA techniques, backed by tools like MITRE’s TARA, map vulnerabilities, identify threats, and define mitigations across the vehicle lifecycle.

By embedding safety and security into every stage of the V-Model, teams ensure that SDVs remain both functionally safe and cyber-resilient from design through deployment.