Challenges and Practices in Quantum Software Testing and Debugging: Insights from Practitioners
Jake Zappin, Trevor Stalnaker, Oscar Chaparro, Denys Poshyvanyk

TL;DR
This paper explores the unique challenges faced by quantum software developers in testing and debugging, revealing reliance on classical methods and highlighting the need for specialized tools to improve quantum software quality.
Contribution
It provides empirical insights from practitioners on current testing and debugging practices in quantum software engineering and identifies gaps in existing tools and workflows.
Findings
Most developers use classical testing methods over quantum-specific tools
Debugging relies on classical strategies like print statements and simulators
Bugs mainly stem from classical issues such as library updates and developer errors
Abstract
Quantum software engineering is an emerging discipline with distinct challenges, particularly in testing and debugging. As quantum computing transitions from theory to implementation, developers face issues not present in classical software development, such as probabilistic execution, limited observability, shallow abstractions, and low awareness of quantum-specific tools. To better understand current practices, we surveyed 26 quantum software developers from academia and industry and conducted follow-up interviews focused on testing, debugging, and recurring challenges. All participants reported engaging in testing, with unit testing (88%), regression testing (54%), and acceptance testing (54%) being the most common. However, only 31% reported using quantum-specific testing tools, relying instead on classical and manual methods. Debugging practices were similarly grounded in classical…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
