SnagBadgerA little help for every snag.
Small snag. Big adventure.

Catch the snag.
Keep the story.

Bug reports, test plans, and evidence that travel together.

Oops? We got this.

Catch the snag. Keep the evidence.#

SnagBadger connects bug reporting, test planning, agent-driven testing, and regression work. Describe the behavior you expect, record what actually happened, and keep the useful evidence with the result.

Start with a small, inspectable workflow. The current repository supplies portable report APIs, Markdown test catalogs, runtime-driven execution, and reviewed local exports. The reporting interface is an experimental demonstration; live browser capture and tracker submission are separate work.

Pick your starting point#

From a problem to a useful record#

A successful save message is not enough if the old value returns. SnagBadger keeps the expectation, actual behavior, attempted actions, and supporting evidence distinct. A failed test can become an editable bug report; a problem discovered during a passing test can too.

An export is a reviewed derivative of an identified report revision. It can be opened locally and inspected as structured data without an external tracker or server. See how the pieces fit together.

Know what you are trying#

The examples intentionally include failures and simulated recording. The catalog describes tests to run; its existence does not prove that every test has been executed. Read project status before treating a demo as a production integration.

These pages describe the current repository version. The public API reference links supported entries; GitHub issues hold the canonical product decisions.

License#

SnagBadger is source available under PolyForm Shield 1.0.0. It permits noncompeting commercial uses and restricts providing competing products or services using the software. See the licensing notes and full license for its conditions and exceptions. Third-party components retain their respective licenses.