In-house Automotive North America Company newsroom

General Motors

GM must validate and debug vehicle software that affects safety, navigation, entertainment, and core vehicle operations before release, because modern vehicles contain more than 100 million lines of code and the company does not want customers acting as software beta testers.

millions of button pushes and screen taps
more than 100 million lines of software code
more than 300 test benches

Reported impact

Business outcome

GM can run more intelligent software tests every hour of every day, detect bugs earlier in the development cycle, reduce the time required versus physical-only testing, and improve release predictability for safety-critical vehicle software.

  • Productivity Improvement
  • Risk Reduction

Solution

General Motors describes an in-house AI software quality pipeline for vehicle code used in safety, navigation, entertainment, and core driving operations. Engineers feed new vehicle software builds into virtual test environments where Automated testing simulates millions of button pushes and screen taps against dashboard touchscreen and infotainment behavior before a human tester uses the system. After lab simulation, engineers drive vehicles with the newest builds at Milford Proving Ground and other sites, then a custom device in company-owned test vehicles continues Automated testing while the cars are parked. AI and machine learning-powered testing run around the clock on lab benches and parked vehicles, with real-world employee drive data used as a backstop to expose bugs earlier in the development cycle and improve release predictability before software is integrated into production vehicles. The source does not identify a separate storage platform.

Data flow

GM feeds new vehicle software builds into virtual lab tests that simulate touchscreen and infotainment use. Results are reviewed before code is integrated into vehicles. The same builds are then exercised in real test drives at Milford Proving Ground and other sites, and a custom device continues automated tests overnight in parked company vehicles. Real-world drive data backs up the virtual runs so engineers can find and fix defects earlier before release.

Solution architecture

5 components · 2 layers
  1. Compute
    • AI Runs software tests around the clock in GM's software quality workflow.
    • Automated testing Simulates millions of button pushes and screen taps to find software defects before human testing and vehicle integration.
    • machine learning-powered testing Takes over overnight in parked test vehicles to improve predictability at release time.
    • virtual testing Exercises dashboard touchscreen software through simulated everyday use before physical validation.
  2. Uncategorized
    • custom device Runs automated software tests in company-owned vehicles while they are parked overnight.

Architecture clues

  • Engineers test newest software builds at Milford Proving Ground in Michigan and other test sites.
  • GM operates software testing labs in Michigan, California and Ontario, Canada.
  • One Michigan facility has more than 300 test benches focused on dashboard infotainment bugs and malfunctions.
  • Some company-owned vehicles run automated software tests overnight while parked.
  • Virtual testing is backed up by real-world data from GM employees who test-drive vehicles across the U.S.

Evidence from the source

"Automated testing simulates millions of button pushes and screen taps, helping us to refine in-cabin software before a human tester ever encounters it on a touchscreen or dashboard display."
"In one Michigan facility alone, more than 300 test benches are dedicated to finding bugs and malfunctions in dashboard infotainment systems."
"This automated testing helps GM engineers detect software bugs before the code is integrated into vehicles, allowing us to identify issues – and implement solutions earlier in the development cycle."
"We’re using AI to run software tests around the clock."
"When those cars are parked overnight, machine learning-powered testing takes over to help enable a more predictable outcome at the time of release."
"With automation and simulation, we can run these tests in a fraction of the time that physical testing would require."
Transparency Evidence & methodology 75/100 reference value · 92% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value75/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence92%
  • Source authority25/25
    The deployment is described by the adopting organization or a government source.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. General Motors

    General Motors customer story

    First-party
    https://news.gm.com/home.detail.html/Pages/topic/us/en/2024/nov/1120-ai.html
    Source type
    Customer-published story
    Published
    Nov 20, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Nov 20, 2024 · General Motors · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.