Core Concepts

Organizations

An organization is the top-level container for all data. Each organization is isolated from every other through PostgreSQL Row-Level Security, so no data can leak between tenants. An organization holds users, projects, roles, and all associated test data. One is created automatically on sign-up.

Projects

A project represents a specific product, service, or repository within an organization. Each project has its own API keys, test runs, test cases, tags, folders, and settings. Data retention is configurable per project — 30, 90, 180, or 365 days — to control how long historical run data is kept.

API Keys

API keys authenticate reporters and external integrations against a project. Each key is scoped to a single project and carries the same permissions as the project itself. Reporters send the key in the X-API-Key header on every ingest request.

Manage keys under Project Settings → API Keys. Keys can be revoked at any time; revoking a key invalidates it immediately for all in-flight reporter runs.

Launches & Runs

A launch (or run) is an automated test execution streamed from a reporter such as Playwright, Jest, or JUnit. Launches follow a simple lifecycle: started → running → completed. Each launch contains suites and individual test results that stream in real time over WebSocket.

Every test result includes its status, duration, error message, steps, and any attachments such as screenshots, videos, traces, or logs.

Test Cases

Test cases are manual test definitions organized into folders and suites. They are distinct from automated test results — cases describe the reusable specification, while automated tests are the executions of that specification. Each case carries steps with expected results, a priority level (P0–P4), a status, tags, and custom fields.

Linking Autotests to Test Cases

M00N Report connects automated test runs to the manual cases they cover so a single case can show its coverage status across every recent automated run. Three independent mechanisms feed the link resolver:

• Reporter annotations — @TestCaseId("...")(Java/JUnit) or { type: 'caseId', description: '...' }(Playwright JS test annotations).
• [TC-N] token in the test title — any [TC-<case-number>] token in a test name is extracted and resolved server-side. Works with any reporter that streams a test title.
• Dashboard auto-link rules — configured per case in the Auto-link autotests panel on the case detail page. The ingest service consults a per-run Redis cache and links any autotest whose title matches a configured rule.

Results from all three mechanisms are merged into the test record. See each reporter's Concepts → Test Case Linking section for language-specific examples.

Test Executions

A test execution is a manual testing session where a team member works through test cases step by step. Executions can be assigned to specific users, and each step is tracked individually as pass, fail, blocked, or skipped. Link executions to releases to measure release readiness.

Releases

Releases group test activity under a milestone. Both automated launches and manual executions can be linked to a release; combined pass rates then serve as a readiness signal. Releases carry version numbers, target dates, and sprint associations.

Tags

Tags are color-coded labels for organizing runs and test cases. Use them to filter launches and cases, and to view usage statistics across projects. Tags are organization-wide and can be associated with individual projects.

Roles & Permissions

Four roles control what each user can do within an organization:

• Admin - full access: manage users, projects, billing, organization settings, and integrations.
• Manager - project management: create and edit projects, manage API keys, and configure notifications.
• User - read and execute: view data, run manual test executions, and manage their own MCP keys.
• Guest - read-only: view projects, runs, and reports without making changes. Guests never consume a billable seat and do not count toward plan limits.