ConQEC: Concolic Testing for Quantum Error-Correcting Code Implementations

arXiv:2610.31443 · quant-ph, cs.SE · Submitted 2026-10-22 · Read on arXiv

Listen

Radio episode about this paper

Transcript

Introduction to the show: ident: Quantum Radio. Generated commentary on the latest quantum physics and condensed matter papers.

Kai: I'm Kai.

Mira: And I'm Mira, here with Lev.

Kai: We're looking at the paper: "ConQEC: Concolic Testing for Quantum Error-Correcting Code Implementations".

Mira: Here's the gist of the paper. ConQEC presents a concolic testing framework for Quantum Error-Correcting Code (QECC) implementations by combining concrete fault replay with symbolic repairpath constraints to generate tests that expose fault–syndrome–decoder–recovery (FSDR) diagnostics.

Kai: Problem Statement Existing QECC verification techniques prove formal obligations, but developers lack a scalable testing workflow that generates concrete faults and explains where a QECC repair path first diverges.

Mira: For the fault inputs to this pipeline, we focus on Pauli faults because they are the standard discrete abstraction used by QECC decoders and because general quantum errors can be decomposed into Pauli components.

Kai: This creates an implementation gap between the mathematical code and the executable QECC stack.

Title and authors: Kai: So, we're looking at this paper called "ConQEC: Concolic Testing for Quantum Error-Correcting Code Implementations," and it’s by Zihao Li, Ji Guan, and Mingsheng Ying. It sounds like they’re trying to build a way to test these QECC implementations that actually works at scale.

Mira: It focuses on the idea of using concrete fault replay combined with symbolic repair-path constraints. That sounds like they’re moving beyond just checking if the final result is right and trying to find out exactly where things go wrong during the process.

Lev: If you're building something on real hardware, I mean, I need to know how this scales. Because QECCs aren't just simple gates; they involve syndrome measurements, decoders, and recovery actions all happening sequentially.

Kai: Exactly. The authors are targeting Pauli faults because that’s what the decoders actually use for their math. But the paper points out a big gap between the code you write and what actually runs on a quantum processor when you inject those physical errors into it >

Mira: And they call this gap an implementation problem, which is important because formal proofs only tell you if something is theoretically possible, not if your actual software handles it correctly >

Lev: That makes sense. Because if you just look at the final error rate, you don't know *why* it failed; did the decoder pick the wrong fix? Did the recovery step apply something that made things worse? That's where this paper is looking to provide a witness >

The paper's summary: Kai: So, what ConQEC actually does is treat every test as a repair path. They’re not just running a simulation; they’re tracing the fault through syndrome, detector, decoder, recovery actions and finally to the oracle result >

Mira: They introduce this symbolic model for the repair path as S equals hat f phi F sc D R. That compact representation lets them avoid tracking that exponential amplitude level quantum state space that would otherwise explode when you have thousands of physical qubits >

Lev: That’s smart because, if we try to do full quantum state vector reasoning, it just runs out of memory or time way too fast for any real chip we're building today >

Kai: They use coverage objectives to guide the search for faults. Instead of blindly trying random errors, they ask the system where it hasn't seen a certain kind of failure yet, like a specific stabilizer condition or a transition sequence >

Mira: They use SMT queries to find unseen faults that target those specific objectives, and then they materialize that concrete fault F and check it with paired replay to confirm it >

The paper's improvements: Lev: The biggest improvement for me is definitely the localization aspect. They claim this framework localizes seeded QECC repair-path faults by B equals two, and all one hundred ninety-five by B equals four >

Kai: That means if you have a bug, you can find it very quickly in terms of how many physical qubits are involved in the faulty path, which is much better than just saying "it failed somewhere" >

Mira: Also, they show that semantic objectives, like hard stabilizer obligations, are way better than just strong valid-input random testing for finding bugs >

Lev: It also scales reasonably well. They say they can handle thousand-qubit source-level campaigns now, and the next big hurdle is repeated SMT solving because that’s where the computation really gets heavy >

Kai: And they confirmed that you can apply this same evidence contract to public QECC artifacts through detector-adapter execution and decoder regression replay, which means it’s not just for your custom code >

Conclusion: Mira: So, to wrap up, the authors of "ConQEC: Concolic Testing for Quantum Error-Correcting Code Implementations" credit coverage and only report bugs after paired actual and reference replay records the relevant repair-path evidence >

Lev: The point is that this gives you a replay valid, fault localizing FSDR witness for every experimental case, which is a real debugging tool you can actually use on hardware >

Kai: It moves the focus from just getting a final failure to understanding exactly where the implementation first diverges during the correction process >

Mira: The main implication is that this provides a scalable way to debug QECCs without having to deal with exponential quantum state reasoning for every test case >

Lev: I think it’s a big step toward making QECC software development more reliable because it gives developers concrete evidence of the failure mode, rather than just a symptom >

Zihao Li, Ji Guan, Mingsheng Ying

Key Laboratory of System Software, Chinese Academy of Sciences · Institute of Software, Chinese Academy of Sciences · University of Chinese Academy of Sciences · Centre for Quantum Software and Information, University of Technology Sydney

quant-ph, cs.SE

Submitted: 2026-10-22

Updated: 2026-10-22

Comments: 12 pages. Accepted at the 49th IEEE/ACM International Conference on Software Engineering (ICSE 2027)

Code: https://github.com/Hikari-HN/conqec-qse-artifact

License: http://creativecommons.org/licenses/by/4.0/

The gist: The gist: ConQEC presents a concolic testing framework for Quantum Error-Correcting Code (QECC) implementations by combining concrete fault replay with symbolic repairpath constraints to generate

Key concepts

Pauli Faults
These are the standard discrete errors used in QECC decoders. The framework treats these faults symbolically, allowing it to explore potential errors without needing to calculate complex quantum state vectors. This symbolic representation is key to scaling the testing process beyond what is feasible with traditional amplitude-level reasoning.
Repair Path (S)
A repair path is a sequence of steps in the QECC process, including fault injection, syndrome measurement, decoder decision, and recovery action. ConQEC models this path symbolically as S = ⟨ˆf, ΦF, ₛc, D, R⟩. This compact model lets the system search for specific sequences where the implementation deviates from expected behavior.
FSDR Diagnostics
This is the core diagnostic output of ConQEC. It captures the entire error correction process: the injected fault (f), what syndrome was observed (s), which decision was made by the decoder (D), what recovery action was taken (R), and whether the final oracle result matched expectations. This provides a complete, replayable witness for debugging.
Symbolic Repair-Path Constraints
Instead of enumerating every possible quantum state, ConQEC uses symbolic constraints to define relationships between faults, syndromes, and decisions across the repair path. This allows the framework to target specific behaviors—like a decoder misdispatch—without needing exponential state space exploration.

Summary

The gist: ConQEC presents a concolic testing framework for Quantum Error-Correcting Code (QECC) implementations by combining concrete fault replay with symbolic repairpath constraints to generate tests that expose fault–syndrome–decoder–recovery (FSDR) diagnostics.

Problem Statement

Existing QECC verification techniques prove formal obligations, but developers lack a scalable testing workflow that generates concrete faults and explains where a QECC repair path first diverges. For the fault inputs to this pipeline, we focus on Pauli faults because they are the standard discrete abstraction used by QECC decoders and because general quantum errors can be decomposed into Pauli components. This creates an implementation gap between the mathematical code and the executable QECC stack. A useful QECC bug report is not just a failed final assertion; it is a replayable repair-path witness: the concrete fault, observed syndrome, decoder decision, recovery action, oracle result, and earliest divergent stage.

ConQEC Design and Workflow

ConQEC addresses scalability and diagnostic challenges with two design ideas. First, it treats each test as a Fault–Syndrome–Decoder–Recovery (FSDR) repair path and accepts a bug only after actual/reference replay produces a staged witness. Second, ConQEC makes test generation symbolic at the repair-path level: Pauli faults are represented as symbolic variables and propagated through syndrome, detector, stabilizer, decoder, recovery, and oracle predicates. The symbolic repair-path model is defined as S = ⟨ˆf, ΦF, sc, D, R⟩. This compact representation lets ConQEC solve for targeted repair-path behaviors without enumerating the concrete fault space or carrying an amplitude-level quantum state vector.

Objectives and Candidate Generation

ConQEC uses coverage objectives to target measurement outcomes, stabilizer conditions, and transition sequences. These objectives define the search space for candidate faults through constraint queries over S. For instance, a failure-directed objective asks for a stage divergence such as Dimpl(σ) ≠ Dref(σ). The process involves an SMT query that selects an unseen fault targeting the objective. Once a SAT model is found, the concrete fault F is materialized and then validated by paired replay.

Evaluation and Results

ConQEC was evaluated on generated source-level QECC families and public QECC artifacts with up to thousands of qubits. RQ1 demonstrated that ConQEC localizes seeded QECC repair-path faults by B = 2, and all 195 by B = 4. RQ2 showed that semantic objectives improve hard repair-path coverage more effectively than strong valid-input random testing. RQ3 indicated that ConQEC scales to thousand-qubit source-level campaigns; the next scaling boundary is repeated SMT solving, while paired replay remains negligible. RQ4 confirmed that the same evidence contract can be instantiated on public QECC artifacts through detector-adapter execution and wrapper-level decoder-regression replay.

Conclusion

ConQEC credits coverage and reports bugs only after paired actual/reference replay records the relevant repair-path evidence. The remaining results show that semantic objectives improve hard repair-path coverage, paired replay is not the scale bottleneck, and the same evidence contract can be instantiated on public QECC artifacts. This paper presented ConQEC, a concolic testing framework that treats QECC execution as a replay-backed repair path. The authors conclude that ConQEC detects the seeded bug in every experimental case and reports a replay-valid, fault-localizing FSDR witness for each. This framework represents a significant advancement over prior methods by providing developer-facing debugging evidence. The ConQEC source code and experimental artifacts supporting this study are available at https://github.com/Hikari-H N/conqec-qse-artifact.

--- Page 1 ---

ConQEC: Concolic Testing for Quantum Error-Correcting Code Implementations

Zihao Li1,2,3, Ji Guan1,2, Mingsheng Ying4

Key Laboratory of System Software (Chinese Academy of Sciences), Beijing, China

Institute of Software, Chinese Academy of Sciences, Beijing, China

University of Chinese Academy of Sciences, Beijing, China

Centre for Quantum Software and Information, University of Technology Sydney, Sydney Australia

lizh@ios.ac.cn; guanj@ios.ac.cn; Mingsheng Ying@uts.edu.au

Abstract—Quantum error-correcting code (QECC) implementations are hybrid software-control systems: measured syndromes drive decoder dispatch, recovery actions, and logical checks. Existing QECC verification techniques can prove formal obligations, and general quantum testing can expose final failures, but developers still lack a scalable testing workflow that generates concrete faults and explains where a QECC repair path first diverges. This paper presents ConQEC, to our knowledge the first concolic testing framework for QECC implementations. By combining concrete (Pauli) fault replay with symbolic repairpath constraints, ConQEC generates tests that expose not only final logical failures but also fault–syndrome–decoder–recovery (FSDR) diagnostics: the injected fault, observed syndrome, decoder decision, recovery action, oracle result, and earliest divergent stage. Its symbolic encoding of Pauli faults, syndrome predicates, decoder and recovery relations, and oracle checks enables this diagnostic workflow to scale beyond exponentially increasing amplitudelevel quantum-state reasoning. We implemented ConQEC and evaluated it on generated source-level QECC families and public QECC artifacts with up to thousands of qubits. ConQEC detects the seeded bug in every experimental case and reports a replayvalid, fault-localizing FSDR witness for each. Index Terms—quantum software testing, quantum error correction, concolic testing, symbolic execution, automated test generation, debugging, failure witnesses

I. INTRODUCTION

Quantum programs are increasingly becoming components of larger software stacks. Recent work studies coverage criteria and coverage-guided test generation [1]–[3], bug studies and bug benchmarks [4], [5], static analysis [6], runtime assertions [7]–[8], and compiler verification [9]. Together, these efforts show that quantum software increasingly raises familiar software-engineering questions: how to generate effective tests, measure meaningful coverage, and localize implementation failures under quantum-specific semantics. Quantum error-correcting code (QECC) implementations make this need especially acute. QECCs are the basic mechanism by which fault-tolerant quantum computers protect logical quantum information from noisy physical hardware [10]–[16]. Instead of storing information in a single fragile physical qubit (quantum bit), a QECC encodes it into a larger block of physical qubits, repeatedly extracts syndrome information to infer possible faults, and applies recovery operations intended to restore the logical state.

Improvements for AI systems

  1. Scalable repair-path generation allows ConQEC to target thousand-qubit QECC behaviors by encoding Pauli faults, syndrome predicates, decoder/recovery relations, and oracle checks as symbolic constraints instead of amplitude level reasoning. This enables the framework to generate tests that expose fault–syndrome–decoder–recovery (FSDR) diagnostics without being limited by exponentially increasing state space.

  2. ConQEC produces replay-backed FSDR witnesses that localize the earliest divergent stage, such as Decoder misdispatch, allowing developers to pinpoint exactly where an implementation diverges from a reference contract, rather than just reporting a final logical failure.

  3. Semantic coverage objectives allow ConQEC to target hard stabilizer obligations more effectively than random testing by recording not only whether a check fired but also the number of selected fault atoms that touched that check, distinguishing between different fault weights.

  4. The system can evaluate the effectiveness of repair-path semantic guidance over valid-input random testing by demonstrating superior coverage on stabilizer conditions and transition sequences across various qubit scales compared to random sampling.

Abstract

Quantum error-correcting code (QECC) implementations are hybrid software-control systems: measured syndromes drive decoder dispatch, recovery actions, and logical checks. Existing QECC verification techniques can prove formal obligations, and general quantum testing can expose final failures, but developers still lack a scalable testing workflow that generates concrete faults and explains where a QECC repair path first diverges. This paper presents ConQEC, to our knowledge the first concolic testing framework for QECC implementations. By combining concrete (Pauli) fault replay with symbolic repair-path constraints, ConQEC generates tests that expose not only final logical failures but also fault--syndrome--decoder--recovery (FSDR) diagnostics: the injected fault, observed syndrome, decoder decision, recovery action, oracle result, and earliest divergent stage. Its symbolic encoding of Pauli faults, syndrome predicates, decoder and recovery relations, and oracle checks enables this diagnostic workflow to scale beyond exponentially increasing amplitude-level quantum-state reasoning. We implemented ConQEC and evaluated it on generated source-level QECC families and public QECC artifacts with up to thousands of qubits. ConQEC detects the seeded bug in every experimental case and reports a replay-valid, fault-localizing FSDR witness for each.

Sources

Related papers