Key concepts
The core BugBrain vocabulary — workspace, project, test run, test case, test plan, issue, and the AI agent — and how they fit together.
A quick tour of the words you'll see throughout BugBrain and the docs. Each links to its full guide.
The building blocks#
| Concept | What it is |
|---|---|
| Workspace | Your organization. Holds your team, billing, and all projects. |
| Project | One application under test — its URL, credentials, and configuration. |
| Test run | A single execution against a project. Either an exploratory run (open-ended) or an execution of specific test cases / a plan. |
| Test case | A saved, repeatable check written as plain-English steps (semantic intent, not brittle selectors). |
| Test plan | An ordered group of test cases and suites you run together, with a parallelism setting. |
| Issue | A problem BugBrain found — with a screenshot, repro steps, category, severity, and a confidence score. |
| AI agent | The autonomous engine that explores, authors test cases, runs them, and heals them as your app changes. |
How they fit together#
A project frames the work
Everything — runs, cases, issues — belongs to a project, which knows your app's URL and how to sign in.Runs produce issues
Whether exploratory or case-driven, a run drives a real browser through your app and emits issues with evidence.Test cases make checks repeatable
Promote an important flow into a test case so it's checked the same way every time — on a schedule, or on every pull request.Plans organize execution
Group related cases into a plan to run them together with controlled parallelism.The agent ties it together
It maps your app, suggests and authors cases, prioritizes what to run after a change, and heals cases when the UI shifts.
A few terms worth knowing early#
- Exploratory run — an open-ended run where the AI decides what to test. Best for discovery and broad coverage.
- Verdict — the outcome of a check:
PASS,FAIL, orINCONCLUSIVE. The last is used honestly when BugBrain can't be sure, and never counts as a pass. See test-run scoring. - Signature — a fingerprint BugBrain computes for each issue so the same bug seen across runs is deduplicated into one issue. See issue confidence & dedup.
- Add-on — a metered capability (API testing, load testing, AI-app testing, PR automation) enabled per workspace.
Next steps#
Frequently asked questions
What's the difference between a test run and a test case?
A test case is a saved, repeatable check (e.g. "user can complete checkout"). A test run is one execution against your app — it can be an open-ended exploratory run, or the execution of specific test cases or a test plan.
What's the difference between a workspace and a project?
A workspace is your whole organization (team, billing, all projects). A project points at one app. Most companies have one workspace and several projects.
What does INCONCLUSIVE mean on a result?
It means BugBrain couldn't confidently determine pass or fail — for example the page didn't load, or the flow was blocked. It's deliberately not counted as a pass. See Test-run scoring for details.