Get one Xray Test with its type, steps / Gherkin / unstructured definition, folder and Jira fields.

Search Xray Tests by JQL, keys, project, test type or Test Repository folder (paginated).

Get a Test with 'Call Test' steps expanded inline into the steps of the called tests.

List the versions of a Test (ids for the version_id parameters of the other tools; paginated).

Get the datasets (parameters and rows) of data-driven Tests, optionally as overridden on Test Plans / Executions.

Create an Xray Test issue (manual steps, Gherkin or unstructured definition).

Delete a Test issue permanently (Jira issue included).

Change the test type of a Test (e.g. Manual -> Cucumber).

Replace the Gherkin or unstructured definition of a Test. Use the step tools for manual tests.

Append a step to a manual Test.

Update action, data and/or expected result of a manual test step.

Remove one step from a manual Test.

Remove all steps from a manual Test.

Link one Test to Preconditions, Test Sets, Test Plans and/or Test Executions.

Unlink one Test from Preconditions, Test Sets, Test Plans and/or Test Executions.

Get a Precondition with its type, definition, folder and the Tests it is linked to.

Search Preconditions by JQL, keys, project or type (paginated).

Create a Precondition issue, optionally linked to Tests.

Update type, definition and/or folder of a Precondition.

Delete a Precondition issue permanently.

Link Tests to a Precondition.

Unlink Tests from a Precondition.

Get a Test Set with the Tests it contains.

Search Test Sets by JQL, keys or project (paginated).

Create a Test Set issue, optionally with Tests.

Delete a Test Set issue permanently (the Tests are kept).

Add Tests to a Test Set.

Remove Tests from a Test Set.

Get a Test Plan with its Tests, Test Executions and folder structure.

Search Test Plans by JQL, keys or project (paginated).

Create a Test Plan issue, optionally with Tests (e.g. fixVersions via extra_fields).

Delete a Test Plan issue permanently.

Add Tests to a Test Plan.

Remove Tests from a Test Plan.

Associate Test Executions with a Test Plan.

Remove Test Executions from a Test Plan.

Get a Test Execution with environments, Test Plans and its test runs (test + status).

Search Test Executions by JQL, keys or project (paginated).

Create a Test Execution issue with Tests (one test run per Test). Link it to a plan via the test_plans tools.

Delete a Test Execution issue permanently, including its test runs.

Add Tests to a Test Execution (creates a test run per Test).

Remove Tests from a Test Execution, deleting their test runs.

Add Test Environments to a Test Execution; unknown environments are created.

Remove Test Environments from a Test Execution.

Get one test run in full detail (steps, evidence, defects, examples, iterations), by id or by Test + Test Execution.

Search test runs by Tests, Test Executions, Test Plans, assignees or statuses (paginated).

Count the Tests of a Test Plan or Test Execution per status, e.g. to answer 'how far along is it?'.

Update a test run: status, comment, timestamps, assignee, executor and custom fields.

Reset a test run to its initial state, discarding status, comments, evidence and step results.

Start, pause or reset the execution timer of a test run.

Link and/or unlink defects on a test run.

Attach evidence files (base64 or uploaded attachment ids) to a test run.

Remove evidence from a test run by id and/or filename.

Record the result of one test run step: status, comment, actual result, defects and evidence.

Set the status of one iteration of a data-driven test run.

Set the status of one Cucumber Scenario Outline example in a test run.

Get a folder with its counts and complete subfolder tree. Use xray_get_tests(folder_path=...) for its Tests.

Create a folder in a project's Test Repository or in a Test Plan, optionally with Tests.

Rename a folder.

Move a folder (with its content) below another folder.

Delete a folder and its subfolders. The Test / Precondition issues in it are not deleted.

Move Tests (and, in the Test Repository, Preconditions) into a folder.

Take Tests / Preconditions out of their folder. The issues themselves are not deleted.

Get the coverage status of a requirement / story and the Tests covering it.

Search coverable issues (requirements, stories...) with their coverage status (paginated).

Get the Xray change history of an issue: who changed what (steps, definition, links...) and when (paginated).

List the test run statuses and step statuses available (globally or for a project).

List the Jira issue link types known to Xray (used for requirement coverage).

Get Xray project settings: test types, test environments, coverage, step fields, test run custom fields.

Search the reusable manual or BDD (Gherkin) step library.

Get status, progress and per-test results/errors of a bulk test import job.

Export Cucumber Tests as .feature files; returns each file's name and content.

Import JSON test results into Xray, creating or updating a Test Execution.

Xray JSON can target an existing execution via "testExecutionKey" or describe a new one in "info". Pass test_execution_info to control all Jira fields of the created Test Execution (multipart import).

Import an XML test report (JUnit, TestNG, NUnit, xUnit, Robot Framework) into Xray.

Either use the simple parameters (project_key, test_execution_key, ...), or pass test_execution_info / test_info for full control over the created issues (multipart import).

Start an asynchronous bulk import of Tests. Poll xray_get_import_tests_status with the returned jobId.

Create or update Cucumber Tests and Preconditions from .feature files (single file or zip).

Download an attachment or evidence file; text files come back as text, others as base64.

Upload a file; the returned id can be used as attachment_id in evidence / step attachments.

Look up the Xray GraphQL schema: signatures and field docs of queries, mutations and types.

Run a read-only Xray GraphQL query. Entities are addressed by issue id; every list needs limit (max 100).

Run an Xray GraphQL mutation not covered by a dedicated tool.

List all Xray toolsets (read and write halves), which tools are enabled, and whether the server is read-only.