List all qTest projects the authenticated user can access. Returns id, name and status for each. Use this first to discover the projectId required by most other tools.

Fetch a single qTest project by its numeric ID.

List Test Design modules (folders). With no parentId, returns root modules. Provide parentId to list child modules. Provide search to filter by name (case-insensitive substring).

Create a Test Design module (folder). Omit parentId to create at the root, or supply parentId to nest it under an existing module.

Update a module's name, description, or custom fields. Provide fields as a map of fieldId -> value.

List test cases in a project, optionally scoped to a module via parentId. Supports client-side filtering by name substring.

Fetch a single test case by ID, including its test steps and properties.

Create a test case inside a module. You can include ordered test steps and custom field values (fieldId -> value map).

Update a test case's name, description, precondition, or custom fields. Creates a new version in qTest.

Append a single test step (action + expected result) to an existing test case.

List requirements in a project, optionally scoped to a parent module. Supports client-side filtering by name substring.

Fetch a single requirement by ID.

Create a requirement under a module. Supply parentId for the containing module and optional custom fields (fieldId -> value).

Update a requirement's name, description, or custom fields. Optionally move it to a different parent module.

Create coverage links between a requirement and one or more test cases. This is the primary traceability action: it marks the listed test cases as covering the requirement. IDs are numeric test case IDs (use qtest_list_test_cases to find them).

Remove coverage links between a requirement and one or more test cases.

List the test cases currently linked to (covering) a requirement.

Generic object-linking between any two qTest artifact types. Link the source object (objectType/objectId) to the given target IDs of linkType. Example: link a 'test-cases' object to 'defects'. Supported types: test-cases, requirements, defects, test-runs.

Retrieve the requirement traceability matrix report: requirements with their covering test cases. Useful for coverage audits.

List test cycles. With no parentId, returns root-level cycles. Provide parentId (and the matching parentType) to list children. Supports name filtering.

Create a test cycle. Omit parentId for a root cycle, or nest under a release or another cycle by supplying parentId and parentType.

List test suites under a test cycle (or release). Provide parentId and parentType.

Create a test suite under a test cycle (or release). Test runs are added to suites.

Create test runs inside a test suite from a list of test case IDs. Each run represents one executable instance of a test case. Use qtest_list_test_cases to find test case IDs.

List test runs under a parent (test suite or test cycle). Provide parentId and parentType.

Fetch a single test run by ID, including its latest status.

Record an execution result (test log) against a test run. Provide a status such as 'Passed', 'Failed', 'Blocked', or 'Incomplete'. Optionally include a note and execution start/end timestamps (ISO 8601).

Search a project's artifacts using qTest Query Language (QQL). Example queries: "Name ~ 'login'", "Status = 'Approved'", "'Automation' = 'Yes' and Priority = 'High'". Specify the artifact type to search.

List the system and custom fields (with their numeric IDs and allowed values) for an artifact type in a project. Use this to discover field IDs needed by the 'fields' parameter on create/update tools.

Return the profile of the authenticated qTest user. Useful for verifying connectivity and permissions.

Attach a file (provided as base64 content) to a qTest artifact such as a test case, requirement, defect, or test log.