Use case · regression testing
A useful bug fix should leave a repeatable check behind. Ask the agent to explain the failing behavior, write a regression test, and show which commands passed.
Beeplane provides access to the local agent conversation. Your test runner and repository remain the evidence for a fix; review the test itself to ensure it would fail on the original bug.
Include a minimal reproduction, expected behavior, and relevant error output. Remove secrets and private customer data before adding logs to a prompt.
Have the agent identify the right test layer and add a case that captures the bug before changing production code.
Use Beeplane to check progress or answer a question. On the host, confirm the new test fails for the old behavior and passes after the fix.
Run focused tests and relevant broader checks, then inspect the diff for unrelated changes. Record any test gaps the agent could not cover.
A reproducible bug where you can confirm the new test fails before the fix.
A test that only snapshots implementation details or cannot reproduce the original behavior.
The coding agent may run local commands; Beeplane displays session conversation. Use the host or CI to confirm actual results.
For a regression test, verify that it reproduces the original problem and passes with the change.
You can follow the session and read available transcript context; detailed code and test review is best done on the host.
Free to download. Works with Claude Code, Codex, OpenCode, and other agents on macOS or Linux.