Glossary

OttoTester’s vocabulary is small but specific. Each term below has a one-line definition and a link to where it’s explained in full.

• Agent — one of the AI workers that does the testing: the planner, generator, executor, healer, and auditor. See What is OttoTester.
• API token — a personal access token for calling the OttoTester API from automation. See API tokens.
• Application — a product you test. Holds variants and test templates. See Applications.
• Auditor — the agent that scores the quality of the other agents’ work. See What is OttoTester.
• Candidate test — a suggested test scenario the planner draws from. Extracted from reference docs or added by hand. See Candidate tests.
• Executor — the agent that runs the generated test scripts. See What is OttoTester.
• Fixture — a test whose job is to sign in, so the tests after it start authenticated. See Fixtures and test data.
• Fixture plan — the spec for a fixture: which role it signs in as, and how. See Fixtures and test data.
• Generator — the agent that turns a test case into an executable Playwright script. See What is OttoTester.
• Healer — the agent that repairs a failing test by working out what changed and patching the script. See Healing and hints.
• Healing — the run phase in which the healer repairs failures. See Healing and hints.
• Hint — a durable instruction you add to steer how the agents generate or heal tests. See Healing and hints.
• Organization — the top-level account; holds billing, members, and workspaces. See Organizations.
• Planner — the agent that explores an app and decides what to test. See What is OttoTester.
• Reference doc — a file uploaded to an application to give the agents richer context than the Agent Prompt alone. See Reference docs.
• Replay template — a saved configuration for re-running existing tests. See Replay templates.
• Roles — the two-tier permission model: org-tier and workspace-tier. See Roles and permissions.
• Scheduled run — a run set to fire automatically on a cadence. See Schedule recurring runs.
• Test — one test, with two facets: a test case and a test script. See Tests.
• Test Authoring Template — a saved run configuration: which phases to run, how many tests, an optional Agent Prompt. See Test Authoring Templates.
• Test case — the English facet of a test: a plain-language spec of one scenario. See Tests.
• Test data — sets of input values a test runs against. See Fixtures and test data.
• Test run — one execution of a set of tests, with a report. See Test runs and reports.
• Test script — the executable facet of a test: the Playwright code. See Tests.
• Test suite — a named group of tests you run together. See Test suites.
• Variant — one deployment of an application: a URL plus its environment and browser settings. See Variants.
• Version history — the saved history of changes to a test; you can review past versions and roll back. See Tests.
• Workspace — the container for a team’s applications, variants, and runs. See Set up a workspace.