AI & ML
In the Driver's Seat: A Multi-Company Study on the Reality of Autonomous Driving System Testing
arXiv cs.SE0 views
arXiv:2607.15820v2 Announce Type: replace Abstract: Autonomous driving systems (ADS) are increasingly deployed in complex real-world environments, creating strong demands for rigorous testing to establish their functionality and safety. However, ADS testing remains difficult because practitioners must determine not only what and how to test, but also whether the resulting evidence is sufficient to support progression and release decisions. To understand how this is handled in practice, we conducted semi-structured interviews with experts involved in ADS development and testing across nine companies in six countries. Through thematic analysis, we examined how practitioners organize ADS testing to produce and assess evidence, and what limits confidence in that evidence. Our findings show that industrial ADS testing can be understood as an evidence-building process involving three recurring activities: planning what evidence is needed, producing and evaluating evidence across complementary testing environments, and deciding when testing is sufficient. We further identified recurring limitations concerning scenario adequacy, simulation and deployment fidelity, test execution and observability, and assurance and decision sufficiency. Practitioners reported several approaches for addressing these limitations, although important gaps remain. Based on these findings, we propose an evidence-centered closed-loop testing framework that connects testing intent, scenario selection, evidence production, acceptance decisions, and operational feedback. The study provides an industry-grounded account of how ADS testing is organized, where confidence in current testing breaks down, and how testing processes can be structured more systematically.
Source:https://arxiv.org/abs/2607.15820PreviousCompaction as Epistemic Failure: How Agentic LLM Tools Fabricate Confirmed Results from Killed ProcessesNextChange2Task: From Repository Changes to Executable Coding Agent Tasks and Environments
Related posts

What Arconatese 3-4 Pontedera tells us about Serie D - Girone D
0dev.to Watercooler
Your AI agent got an HTTP error. Should it retry?
0dev.to Discuss
Is AI dangerous, or just misunderstood?
0dev.to Discuss
Why we price a developer tool per fix instead of per seat
0dev.to Productivity
My LLM-Powered Sidekick for Painless PR Descriptions
0dev.to Productivity
Reward-Adaptive Backtracking GFlowNet: A Technique Worth Understanding
0dev.to Productivity