Agents Lookup

Use cases / Software development

Reproduce a reported bug before attempting a fix

An agent writes a failing script or test that shows the bug in a sandbox, then fixes it and shows the test now passes.

DifficultyIntermediate
Setup timeHalf a day
CategorySoftware development

The use case

Many bug reports never get reproduced, so fixes are guesses. Open-source agents such as SWE-agent and OpenHands work through a GitHub issue in a sandbox: they explore the repo, write a small script or test that triggers the bug, change code, and rerun until the reproduction passes. Having the failing test first gives the reviewer evidence that the fix addresses the reported behavior. Maintainers still check the reproduction actually matches the report, review the patch for side effects, and keep the new test in the suite so the bug stays fixed.

Example workflow

  1. Give the agent the issue text and repository
  2. Agent writes a reproduction script or failing test
  3. Agent edits code until the reproduction passes
  4. Reviewer checks the reproduction matches the report
  5. Merge the fix with the new test

Tools

Risks and guardrails

Sources

Written by Agents Lookup. Credits and official pages for the tools this use case names: