Introduction
Capture a bug, inspect its evidence, and prepare a clean replay.
Reprolane keeps a failure, its source files, and its diagnostic evidence together in a reproduction your team can investigate.
Start with a failing command on your machine. Review what will leave your computer, upload it to your organization, then open the reproduction in the app.
Start with one failure
Follow the quickstart to capture a small command failure. If you need the CLI or organization access first, begin with installation.
Choose your capture
| What you have | Where to start |
|---|---|
| A failing test, build, or script | Command capture |
| A bug you can demonstrate in a local app | Browser capture |
| A repeatable sequence with a specific assertion | Authored scenarios |
Before uploading, review source and evidence. Screenshots and video are excluded by default and need separate review.
Investigate together
Open the reproduction to inspect source and captured evidence. Use a live sandbox and terminal when you need to investigate interactively.
Capture records what happened locally. It does not prove the failure happens in a fresh environment. Verification requests a separate clean replay when the reproduction is eligible.
If a step fails, use troubleshooting.