List test cases for a project.

Search test cases by AQL query.

Get a test case by ID.

Create a new test case. payload.projectId defaults to ALLURE_PROJECT_ID env when omitted. payload.precondition (string) is the preconditions field — always use this for preconditions/prerequisites text, NOT payload.description. payload.description (string) is the general test case description — always populate this with a meaningful summary of what the test case verifies. payload.customFields supports values like { customField: { id }, id, name }. payload.steps is an optional array of step objects with { name (step text), expectedResult (optional expected result text) } — steps are created after the test case. When a step has multiple expected results, list them in expectedResult separated by semicolons (e.g. "Result A; Result B") or as a bullet list (lines starting with -, *, or a number).

Update a test case step by ID. Supports updating body text and/or expectedResult. If expectedResult is provided, the expected result node is created automatically if it does not exist yet.

Update an existing test case. payload.customFields supports values like { customField: { id }, id, name }.

Delete a test case by ID.

Add one or multiple tags to one or multiple test cases using bulk API.

Remove one or multiple tags from one or multiple test cases using bulk API.

Add one or multiple external links to one or multiple test cases using bulk API.

Get test case overview data.

Get test case run history.

Get scenario for a test case.

Get manual scenario steps for a test case. Returns a normalized scenario with root step and a flat map of all steps (scenarioSteps), where each step contains body, expectedResult, children IDs, and optional sharedStepId.

Get tags assigned to a test case.

Set tags for a test case.

Get linked issues for a test case.

Set linked issues for a test case.

Restore a deleted test case.

List custom fields configured for a project.

List values for a custom field in a project.

Get custom field values for a test case.

Add custom field values for a test case via bulk API. Supports grouped values [{ customField: { id }, values: [{ id|name }] }] and flat values [{ id|name, customField: { id } }].

List attachments for a test case.

Upload a file attachment to a test case. Provide file content as a base64-encoded string.

Delete an attachment from a test case by attachment ID.

Download the binary content of a test case attachment. Returns base64-encoded content with its MIME type.

List launches for a project.

Search launches by AQL query.

Get a launch by ID.

Create a new launch. payload.projectId defaults to ALLURE_PROJECT_ID env when omitted.

Update an existing launch.

Delete a launch by ID.

Close an open launch.

Reopen a closed launch.

Get launch statistics.

Get launch progress widget data.

Add test cases to a launch.

Add a test plan to a launch.

List test results for a launch.

Search test results by AQL query. The 'id' field in returned results is an integer — pass it as a number (not a string) to get_test_result or get_test_result_retries.

Get a test result by ID.

Create a new test result.

Update an existing test result.

Get history for a test result.

Assign a test result. payload must include username.

Resolve a test result. payload must include status.

Get the retry history for a test result. Returns the list of previous attempts for the same test in the same launch. Key tool for flaky test detection: if a test failed on attempt 1 but passed on attempt 2, it is a flaky test, not a real failure. Check status across retries to assess reliability.

List attachments (screenshots, logs, HAR files, etc.) for a test result. Returns attachment metadata: id, name, contentType, size. Use this to discover what evidence is available before calling get_test_result_attachment_content.

Download the binary content of a test result attachment. Returns base64-encoded content with its MIME type. Use attachment ID from list_test_result_attachments. For text-based attachments (logs, JSON, XML): decode base64 to read the content. For images (screenshots): the base64 PNG/JPEG can be rendered directly.

List test plans for a project.

Get a test plan by ID.

Create a new test plan. payload.projectId defaults to ALLURE_PROJECT_ID env when omitted.

Update an existing test plan.

Delete a test plan by ID.

Run a test plan by ID.

Get automation trend chart data for a project (test automation coverage over time).

Get test case counts grouped by automation status for a project.

Get test case counts grouped by status for a project.

Get histogram of launch durations for a project.

Get trend of muted test cases over time for a project.

Get test result statistic trend over time for a project.

Get last test result for each test case in a project.

Get test case success rate analytics over time for a project.

List all dashboards for a project.

Create a new dashboard in a project.

Get a dashboard by ID.

Update dashboard fields (name, shared status, etc.).

Delete a dashboard by ID.

Copy an existing dashboard to the same or another project.

Get data for a specific dashboard widget.

List defect records for a project. Defects group similar test result failures by root cause. Each defect has a name, status (open/closed), and optional matcher rules. Use this as the entry point for failure pattern analysis: 'what are the top open defects in this project right now?'

Get a defect by ID. Returns the defect name, status, description, and matcher configuration.

Create a new defect record to group a novel failure pattern. payload must include: name (string), projectId (number). Optional: description (string).

Update defect name, description, or status.

Get the test results grouped under a specific defect. Use this to see how many failures belong to this defect and in which launches they appeared.

Get the test cases affected by a specific defect. Use this to understand which test scenarios are impacted by the failure pattern.

Get launches in which a specific defect has appeared. Use this to understand the blast radius: is this defect appearing in every run or only in specific environments?

Get all defects present in a specific launch. This is the fastest way to get a defect summary for a launch: 'what are all the distinct failure patterns in this test run?'

Find test results that match a defect pattern within a launch. Use this to detect flaky tests and group failures by root cause: pass launchId to scope the search, optionally pass a defectId to check match against a specific defect. Returns test results that are candidates for linking to the defect.

Link one or multiple test results to a defect record (bulk API). payload must include: defectId (number) and testResultIds (array of numbers).

Close multiple defects at once — mark them as resolved after a fix is confirmed. payload must include: ids (array of defect IDs).

Reopen multiple closed defects — use when a regression is detected after a fix was marked complete. payload must include: ids (array of defect IDs).

Link an external issue (Jira, GitHub, etc.) to a defect record. payload must include: url (string) and name (string). Use this to associate a tracker ticket with a failure pattern.

Remove the external issue link from a defect record.

Apply all configured defect matcher rules to a launch. This auto-triages unresolved test results by matching them to existing defect records based on error message patterns. Run this after a launch completes to auto-group failures.

List shared steps (reusable step library) for a project. Shared steps are referenced from test case scenarios via sharedStepId. Use this to discover the available shared step library before reading test case steps.

Get a shared step by ID. Returns metadata: name, project, archived status.

Get the full normalized scenario (list of steps) inside a shared step. This is the key tool for resolving sharedStepId references in test case scenarios: when get_test_case_steps returns a step with sharedStepId, call this tool to inline the actual step content. Returns the same NormalizedScenarioDto format as get_test_case_steps.

Get the list of test cases that use a specific shared step. Use this for impact analysis before editing or archiving a shared step: shows which test cases would be affected.

Create a new shared step in a project. payload must include at minimum: name (string) and projectId (number). Use this to extract repeated test steps into a reusable library.

Update shared step metadata (name, etc.) by ID.

Archive a shared step to retire it from active use. Archived steps remain readable but are hidden from the active library. Run get_shared_step_usage first to check impact before archiving.

Restore an archived shared step back to active status.

List all environment variable definitions (keys) available in the system. Environment variables track test configuration context: browser, OS, environment name, build number, etc. Use this to discover what ev[] keys are available before constructing AQL filters like ev["browser"] = "Chrome" or ev["os"] = "Linux" in search_test_results or search_launches.

Search environment variable definitions by name. Returns matching env var keys with their IDs. Use this to find the exact name of an env var key before querying values.

List environment variable schema definitions for a project. Schemas define which env var keys are tracked and displayed for launches in this project. Use this to understand what configuration context is captured per launch in a given project.

List all recorded values for a specific environment variable key. Returns the distinct values that have been used across test runs (e.g. all browser versions recorded). Use envVarId from list_env_vars. Useful for building precise AQL filters: know that ev["browser"] has values ["Chrome 123", "Firefox 115"].

Search for recorded environment variable values by partial text. Optionally scope by envVarId, projectId, or launchId. Use this to autocomplete valid values for AQL ev[] filters before running a search.

Get the environment variable values recorded for a specific test result. Shows what configuration context (browser, OS, env name, build) this result ran against. Use this when investigating a failure to understand if the environment is a factor: e.g. 'does this only fail on Chrome 124 but not on Firefox?'