Glossary

Automation run — one CI execution, with its name, source, tags and report files.

Automation test — one automated test with a history, identified by a fingerprint of "<suite> :: <name>" within a project.

Automation test result — one automated test in one run.

Bug — something a person found. Raised in a bug hunt against a test case copy, or in a session. Outlives the hunt that found it.

Bug hunt — a scheduled event where named people execute a chosen set of test cases and record verdicts. Status: Planned, Active, Completed, Archived.

Bug hunt test case — the copy of a test case inside a hunt, carrying its own verdict, step results and bugs. Hidden copies are excluded from history and coverage.

Charter — the goal or scope of an exploratory session; what a session has instead of steps.

Copilot — AI assistance inside the app. Standard plan and above.

Coverage — derived, never stored. Computed on every read from the latest verdict on each linked test case, its open bugs, and the last result of any linked automated test. Worst wins.

Custom step field — an organization-defined extra field on test case steps. Standard plan and above.

Directory — a folder in the test library. Nests; subscriptions cover the whole subtree.

Error — one distinct failure across automation runs, with an occurrence count. Matched on the failure's first line. Business plan.

Guest — the lowest role. Reads, comments, reports bugs, runs what is assigned. Also called a viewer; counted against a separate allowance from seats.

Known issues — what a test case warns you about: a written note, plus every bug still open against the case.

MCP — Model Context Protocol; the standard behind the AI connector.

Organization — the tenant. Owns everything. Nothing is visible across two.

Project — a unit of work inside an organization. Has a per-organization sequential projectId, which is what CI uses.

Requirement — a thin reference row, usually a Jira issue, with no status of its own. Coverage is derived from the test cases linked to it.

Session — timed exploratory testing against a charter. Status: Planned, In progress, Paused, Completed, Archived.

Shared step — a reusable block of steps maintained once and inserted into many test cases.

State (test case) — In progress, Active, Outdated, Archived.

Test case — the written record of one test: fields, plus an ordered list of steps.

Unstable test — a test case a person has flagged as flaky, with a reason. Never inferred from run history.

Verdict — a test case's result in a hunt: Untested, Passed, Failed, Blocked.

Won't fix — the only bug status that requires a reason. The reason is cleared if the bug moves back out of it.