← Latest papers
💻 computer science

From Research to Practice: An Interactive Rapid Review of Autonomous Driving System Testing in Industry

This paper presents a practitioner-driven rapid review of autonomous driving system testing that, through collaboration with 21 industry experts, identifies critical challenges regarding End-to-End ADS testing and evaluates the practical applicability of 17 relevant research studies to bridge the gap between academic advances and industrial needs.

Original authors: Qunying Song, Ali Nouri, Håkan Sivencrona, Federica Sarro

Published 2026-05-04
📖 5 min read🧠 Deep dive

Original authors: Qunying Song, Ali Nouri, Håkan Sivencrona, Federica Sarro

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are trying to teach a robot to drive a car perfectly. You want it to handle everything: rain, snow, confused pedestrians, and weird construction zones. The problem is, the real world is huge, messy, and unpredictable. You can't possibly drive every single possible road in the world to prove the robot is safe.

This paper is like a bridge built between two groups of people who speak different languages:

  1. The Academics: Scientists in universities who write fancy papers about new ways to test these robots.
  2. The Practitioners: The actual engineers at a major car company (Volvo) who have to make sure the cars are safe enough to put on the road.

The researchers wanted to know: "Are the cool new testing ideas from the scientists actually useful for the engineers, or are they just theoretical toys?"

Here is how they did it and what they found, explained simply:

The "Speed-Date" Method

Instead of just reading papers in a quiet library (which takes forever), the researchers used a method called an "Interactive Rapid Review." Think of this like a speed-dating event for ideas.

  • They gathered 21 engineers from the car company.
  • They asked the engineers: "What are your biggest headaches when testing these self-driving cars?"
  • The engineers voted on their top problems. The two biggest winners were:
    1. How do we test "End-to-End" systems? (Imagine the car's brain is one giant, black-box AI that sees the road and steers the wheel all at once, rather than having separate parts for "seeing" and "steering." It's harder to test because you can't peek inside the black box easily.)
    2. How do we know we've tested enough? (How do you prove you haven't missed a dangerous situation?)

The Search for Solutions

Once they knew the top problems, the researchers went on a treasure hunt. They scanned 1,389 academic papers and picked the 17 best ones that tried to solve those specific problems.

They then brought these 17 "treasures" back to the engineers and asked, "Does this actually work in your garage?"

What the "Treasures" Were (The 17 Papers)

Almost all the papers they found were about generating "Critical Scenarios."
Think of this like a video game designer trying to create the hardest possible level to break a player. The scientists were inventing ways to automatically create the most dangerous, tricky, or weird driving situations to see if the car would crash.

They found four main "flavors" of these scenario generators:

  1. The Rule-Followers: Computers that follow strict math rules to find the edge of safety (like finding the exact speed where a car starts to skid).
  2. The Gamers: Computers that use "Reinforcement Learning" (like training a dog with treats) to learn how to make the car crash by trying millions of different moves.
  3. The Artists: Computers using "Generative AI" (like the tools that make AI art) to create fake but realistic images of dangerous roads.
  4. The Pranksters: Computers that take a normal video and subtly tweak the pixels (like changing the color of a pedestrian's shirt) to trick the car's camera.

The Verdict: Cool Ideas, But Hard to Use

When the engineers looked at these 17 ideas, they said: "These are fascinating, but..."

  • The Good: Many ideas were very relevant. The engineers liked that the scientists were trying to find "long-tail" scenarios (the rare, weird accidents that happen once in a million miles).
  • The Bad (The Reality Check):
    • Too Complicated: Many of these tools are like a Swiss Army knife made of 50 different gadgets. The engineers' current tools are simple screwdrivers. They can't easily plug these complex new systems into their existing workflow.
    • Too Fake: Some of the "dangerous scenarios" created by the AI looked weird or unrealistic to the engineers. If the simulation doesn't look like the real world, the test doesn't count.
    • The "Black Box" Problem: For the "End-to-End" cars, it's very hard to know why the car failed. The scientists' tests often just say "It crashed," but not "It crashed because it confused a stop sign with a cloud."

The Big Takeaway

The paper concludes that there is a gap.

  • Scientists are building high-tech, futuristic testing labs.
  • Engineers are working with practical, existing tools and need things that fit right now.

The researchers say we need to stop just making "cool" tests and start making context-aware tests. This means the scientists need to understand the messy reality of the car company's garage and build tools that fit there, rather than expecting the engineers to rebuild their whole factory to fit the new tools.

In short: The scientists have the blueprints for a Ferrari, but the engineers are trying to fix a delivery truck. They need to work together to build a vehicle that actually drives on the road.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →