CARBON — Engineering ConfidenceUser Guide
CHAPTER 48 / 60 Pro

/carbon-tests

Create, review, edit, duplicate, activate, archive, delete, import, convert, bake in, repair, export, and visually manage project-local CARBON AI-intent tests.

Jay · Your AI test managerTesting operations

When to use it

You want reusable test intent rather than one-off chat findings.

Before you start

Import or create cases with preconditions, steps and expected outcomes. Review converted cases, execute a bake when authorized, and distinguish active definitions from observed passing runs.

Try this in your coding agent.

/carbon-tests Show the saved regression tests for checkout and identify missing cases.

Replace sample paths with your project. Slash names are shorthand; your host may use a plugin prefix or a skill picker. Invocation help →

ILLUSTRATIVE WALKTHROUGH

Saved regression inventory

An expanded teaching example, not a recorded or live execution. The report stays visible while the replay explains how to read it.

  1. 01Read context
  2. 02Analyze
  3. 03Show evidence
  4. 04Report

Coding-agent conversation

Read context

I’m reviewing saved regression inventory. I’ll keep the scope and permissions explicit.

Analyze

Analyze: Show the saved regression tests for checkout and identify missing cases.

Show evidence

Here is the evidence trail to inspect: Inventory → test status → last evidence → source revision → missing recovery case.

Report

A checkout regression has no linked evidence for the current revision. Saved history is not a fresh test run.

CARBON

Example report

Illustration
Project → decisions → retained evidence
Project → decisions → retained evidence — TestBucks teaching screen

TestBucks course screen with illustrative analysis. The screenshot supplies context; the demo does not establish a newly observed bug.

  1. TestBucks project
  2. Command action
  3. Reviewable output

Illustrated outcome

A checkout regression has no linked evidence for the current revision.

Evidence to inspect

Inventory → test status → last evidence → source revision → missing recovery case.

Still untested / not established

Saved history is not a fresh test run.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For saved regression inventory, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

Inventory → test status → last evidence → source revision → missing recovery case. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

Saved history is not a fresh test run.

The next decision

Decide whether the evidence calls for a focused check, a reviewed fix or more context. Do not convert a plausible example into a verified finding.

Adapt the example to your project

  1. Replace saved regression inventory with a real feature, path or decision in your project.
  2. State the expected rule and its source. Include safe fixtures, constraints and a budget where appropriate.
  3. Ask for exact evidence and remaining gaps. Approve consequential actions separately.
/jay Review the /carbon-tests result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-generate →/ai-upgrade →

Content checked against the local command definition: skills/carbon-tests/SKILL.md. Examples adapted from the homepage’s TestBucks walkthroughs. Availability is edition- and host-dependent.