From Resource Flow to Executable Tests: Petri-Net-Guided LLM Test Generation for Concurrent Stateful Rust APIs

Source

• Source name: arXiv
• Source kind: paper
• Authors / organization: Kaiwen Zhang, Guanjun Liu
• Venue: arXiv: cs.SE
• Published: 2026-07-23
• Collected: 2026-07-24
• URL: http://arxiv.org/abs/2607.21530v1
• PDF: https://arxiv.org/pdf/2607.21530v1
• DOI: UNKNOWN

Plain-Language Brief

The paper proposes a methodology using Petri nets to generate tests for concurrent stateful Rust APIs, aiming to address issues with large language models (LLMs) in generating executable tests that may violate API preconditions or reduce concurrency. The method represents API resources and dependencies as tokens and transitions, derives legal scenarios, and uses them for LLM-based code synthesis while preserving the modeled intent during concretization.

What the Document Says

• The paper discusses a methodology using Petri nets to generate tests for concurrent stateful Rust APIs.
• API resources, lifecycle conditions, and causal dependencies are represented as colored tokens and transitions.
• Legal deep-state, near-legal, and partial-order concurrent scenarios are derived.
• These scenarios are used as a constrained intermediate representation for LLM-based code synthesis.
• A local-faithfulness contract and structural repair loop preserve the modeled intent during concretization.
• Petri-guided schedule shaping prioritizes high-conflict concurrency skeletons for systematic exploration.
• A layered semantic oracle distinguishes synthesis failures from violations of the target API's expected behavior.

Key Concepts Mentioned

• Petri nets
• test generation
• concurrent stateful Rust APIs
• large language models (LLMs)

Claims Made by the Document

• The method addresses issues with LLMs in generating executable tests for concurrent stateful Rust APIs.
• The derived scenarios can be used as a constrained intermediate representation for LLM-based code synthesis.
• The local-faithfulness contract and structural repair loop preserve the modeled intent during concretization.
• Petri-guided schedule shaping prioritizes high-conflict concurrency skeletons for systematic exploration.

Evidence Used

• The paper explains the methodology using Petri nets for test generation over concurrent stateful Rust APIs.
• The authors detail how API resources, lifecycle conditions, and causal dependencies are represented as tokens and transitions.

Methods / Approach

UNKNOWN

Limitations Stated by the Authors

UNKNOWN

Limitations Noted by the Agent

Agent interpretation — not from the source.

UNKNOWN

Open Questions

UNKNOWN

Notes for Future Q&A

May include interpretation. Labeled where it does.

UNKNOWN

Raw Abstract / Excerpt

Concurrent stateful library APIs expose behavior through evolving resource ownership, lifecycle states, and competing interleavings. Large language models can synthesize executable Rust tests, but their outputs often violate API preconditions, remain shallow, or reduce concurrency to accidental sequential traces. Conversely, model-based and systematic testing techniques provide semantic control but commonly require substantial handwritten code to turn abstract scenarios into executable tests. This paper addresses the gap between formal scenario design and low-cost test concretization. We present a Petri-net-guided methodology for test generation over concurrent stateful Rust APIs. The method represents API resources, lifecycle conditions, and causal dependencies as colored tokens and transitions; derives legal deep-state, near-legal, and partial-order concurrent scenarios; and uses these scenarios as a constrained intermediate representation for LLM-based code synthesis. A local-faithfulness contract and structural repair loop preserve the modeled intent during concretization, while Petri-guided schedule shaping prioritizes high-conflict concurrency skeletons for systematic exploration. A layered semantic oracle then distinguishes synthesis failures from violations of the target API's expected behavior.