First-use walkthrough

From “it seems fine”
to something you can inspect.

Start with one change or a disposable demo. The goal is one useful, evidence-backed result—not an impressive test count.

Option 1: your current change

Ask Jay to test my current change with CARBON. Start with a five-minute risk-based pass, show a live rendered report, verify the most important suspected issue, and propose a regression test. Ask before editing code. Finish with evidence and coverage gaps.

Option 2: a safe demo

Use CARBON to create a fresh disposable TestBucks demo. Do a five-minute first assessment, open the live report as a rendered browser page, and finish with observed results and a proposed regression test. Do not modify my existing project.

The bundled demo intentionally contains defects. Jay must run the checks to establish actual findings; an intentional defect is not evidence that this particular run reproduced it.

What you should see

Jay opens a rendered report during the run and returns to it at the end. If your host cannot open an embedded browser, use the protected local-browser URL while the viewer is active. A stopped viewer does not mean your saved evidence is lost.

Useful is better than “100% confident.”

Look for the tested scope, what actually ran, reproducible failures, unresolved candidates and untested areas. Approve any proposed regression-test changes before they are written. Your existing framework can stay.

Need a property proof or a durable cross-run test inventory? See where Pro adds control. Your free findings are never hidden.