With the integration of connected services, connected vehicles, autonomous driving, mobile devices and third party app development, along with the distributed nature of an in-vehicle infotainment system, testing such systems face many challenges. These are amplified by the global scale of engineering and development efforts.
KPIT brings to you a series of perspectives on In-Vehicle Infotainment – specifically around testing the embedded software that makes up the heart of this subsystem.
Topic 1: Landscape of Infotainment Testing Challenges
Some of the key challenges in testing Infotainment Systems are :
High level of feature content which could either be embedded or brought in with devices like cell phones, tablets or USB memory sticks
Connectivity based feature content that demands end to end testing requirements
Infotainment system within the vehicle can be highly distributed - including multiple audio zones and multiple UI
Integration sites such as head unit and cluster can present issues when attempting to recreate and verify observed defects
Cybersecurity concerns have increased and have therefore come to the forefront of testing requirements
ADAS/Autonomous vehicle features will interface to the Infotainment system. There can be an increased role in the time to come
Software release cadence is generally faster (shorter time between releases) than the respective OEM's product development process cycle times
Rapid turnaround time required in reporting defects
Talent with multi-domain expertise
Consistency in test definitions across simulator, test bench and vehicle
Desire and ability to collect test data - leverage data analytics in defect analysis
Getting the basics right
  • Build a configurable test system – A crank waveform generator may be present in some configuration, not necessarily in all
  • Test system must be able to manage data logger loading and facilitate analysis – Switched Ethernet with 100MBPS, Surround View, Camera interfaces for analysis
  • Wireless / OTA connections must be facilitated
  • Back office services are available for testing
Configuration & Setup
  • Test system to provide a la carte capability when developing executable test cases
  • Test system must present negligible performance impact on system under test. More important as we see more embedded in-vehicle deployment of Android
  • Support ECU re-flash for software verification and validation + testing re-flash functionality
Democratize secret sauce
  • Test case development can be driven by different models . Have appropriate interfaces and processing. – State transition diagrams, State space models, Golden sample executable models, signal processing algorithms etc.
  • Test case generation usable by SMEs. Not requiring to deeply understand programming test system ( like device drivers, interface to drivers)
  • Make functional limitation of test systems known to all.
"Simply" communicate
  • Traceability built simplistically for people to communicate test strategy and execution effectiveness
  • Real time communication + Aggregation of pass/fail verdicts at various stages of testing
Coming Next : What are the various types of Infotainment Testing? How is KPIT helping global auto OEMs with Infotainment Testing?
Are you in the automotive ecosystems trying to find solutions for Infotainment Testing. Do you have a question or comment -
Write to us.

Terms of Use   Privacy Policy   Cookie Policy   Home   
Copyright © 2017 KPIT® Technologies Ltd.

CIN: L72200PN1990PLC059594