# QA.tech Docs - [AI Agents](https://docs.qa.tech/core-concepts/ai-agent-testing.md): Autonomous AI testing - [Agent Quickstart](https://docs.qa.tech/agent-quickstart.md): Instructions for a coding agent (Claude Code, Cursor, Codex) to sign the user up for QA.tech, connect the QA.tech MCP server, and run the first tests. - [POC Setup Checklist](https://docs.qa.tech/getting-started/poc-setup-checklist.md): Prepare your web application before a Proof of Concept with QA.tech - [POC Mobile Setup Checklist](https://docs.qa.tech/getting-started/poc-mobile-setup-checklist.md): Prepare native iOS and Android apps before a Proof of Concept with QA.tech - [FAQ](https://docs.qa.tech/getting-started/faq.md): When to use AI agents, scripts, and manual QA. - [Projects](https://docs.qa.tech/core-concepts/projects.md): Organize your testing infrastructure with projects, applications, and environments - [Applications & Environments](https://docs.qa.tech/core-concepts/applications-and-environments.md): Set up applications and environments to organize your tests and run them against different deployments - [Test Data](https://docs.qa.tech/core-concepts/test-data.md): How to give tests credentials, emails, and other values without hardcoding them into the steps. - [Test Dependencies](https://docs.qa.tech/core-concepts/dependencies.md): Control test execution order, manage browser isolation, and structure multi-user testing scenarios - [Dependency Output States](https://docs.qa.tech/core-concepts/output-state-optimization.md): Speed up test execution by reusing browser state from recently completed dependency tests - [Environment access](https://docs.qa.tech/configuration/environment-access.md): Reach a site the agent cannot load: identify the bot, allowlist IPs, or open a private network. - [QA.tech Bot](https://docs.qa.tech/bot.md): Identify and verify QA.tech automated testing traffic. - [IP Access](https://docs.qa.tech/configuration/ip-access-control.md): Configure your ingress to allow QA.tech testing traffic - [Vercel Firewall](https://docs.qa.tech/configuration/vercel-firewall.md): Allow QATechBot traffic through the Vercel Firewall with a custom bypass rule - [Vercel Preview](https://docs.qa.tech/configuration/vercel-preview-protection.md): Configure QA.tech to bypass Vercel deployment protection for automated testing - [Netlify Visitor Access](https://docs.qa.tech/configuration/netlify-protection.md): Let QA.tech open a Netlify site that is private or password protected - [Cloudflare WAF & Turnstile](https://docs.qa.tech/configuration/cloudflare-waf-turnstile.md): Allow QA.tech through Cloudflare edge blocking (WAF) and app-embedded Turnstile widgets - [SSH Tunnel Proxy](https://docs.qa.tech/configuration/ssh-tunnel.md): Securely test applications behind firewalls using SSH tunnels - [Organization Access](https://docs.qa.tech/configuration/organization-access.md): Manage who can join your organization and how they sign in — verified domains, auto-join, and SAML SSO - [Roles and Permissions](https://docs.qa.tech/core-concepts/roles-and-permissions.md): Role-based access in QA.tech - [Authentication Settings](https://docs.qa.tech/configuration/authentication.md): Configure authentication for your QA.tech account - [AI Chat Assistant](https://docs.qa.tech/core-concepts/ai-chat-assistant.md): Natural language interface for managing your QA.tech projects - [Knowledge](https://docs.qa.tech/core-concepts/knowledge.md): Manage project knowledge and context for better AI assistance - [Crawling Sessions](https://docs.qa.tech/core-concepts/crawling.md): Learn how crawling sessions help QA.tech understand your application and improve test suggestions - [Knowledge Graph](https://docs.qa.tech/core-concepts/knowledge-graph.md): A knowledge graph is a digital representation of facts and relations. This can be used as an AI agent’s understanding and memory of a website. - [Creating Tests](https://docs.qa.tech/best-practices/creating-tests.md): Learn how to create effective test cases in QA.tech and write tests that the AI agent can execute reliably. - [Test drafts and revisions](https://docs.qa.tech/core-concepts/test-drafts.md): What Active, Draft, and Archived mean for a test case, when new tests start as drafts, and how revisions record changes to a test. - [Revision History](https://docs.qa.tech/test-features/revision-history.md): View and compare previous versions of your test cases - [Troubleshooting](https://docs.qa.tech/best-practices/troubleshooting.md): What can you do to make QA.tech work as well as possible for you? - [Authentication Rate Limits](https://docs.qa.tech/configuration/auth-rate-limits.md): Configure authentication rate limits to prevent issues during parallel testing - [Shared Steps](https://docs.qa.tech/core-concepts/shared-steps.md): Reuse the same sequence of steps across multiple tests using dependencies, agent knowledge, or assistant docs - [Ownership](https://docs.qa.tech/core-concepts/ownership.md): Assign team members to test cases and test plans to organize responsibilities and track your work - [Parallel Tests](https://docs.qa.tech/core-concepts/parallel-test-execution.md): Control how many QA.tech test cases run in parallel. Set per-environment concurrency limits to protect staging servers or maximize throughput on production. - [Agent Cache](https://docs.qa.tech/core-concepts/agent-cache.md): Understand how Agent Cache speeds up your tests and when to disable it - [Session State Lifetime](https://docs.qa.tech/core-concepts/session-state-lifetime.md): Control how long saved browser states from dependency tests remain valid before requiring a fresh run - [Session sync](https://docs.qa.tech/core-concepts/session-sync.md): Keep single-use sign-in tokens in step across tests and crawls that resume the same login - [Limits](https://docs.qa.tech/core-concepts/limits.md): Understanding log limits and how they affect your tests - [Agents](https://docs.qa.tech/build-tests/agents.md): Which agent runs a web, API, or mobile test, and how that choice is resolved. - [Web](https://docs.qa.tech/build-tests/web.md): Web-only test setup: multiple browser sessions and links to email and clipboard flows. - [Testing API Calls](https://docs.qa.tech/test-features/api-calls.md): Configure API endpoints (URL, method, headers, body) to make HTTP requests during test execution - [File Uploads](https://docs.qa.tech/test-features/file-uploads.md): Testing file uploads with default and custom files - [File Downloads](https://docs.qa.tech/test-features/file-downloads.md): Testing to export and download files - [Camera Video](https://docs.qa.tech/test-features/camera-video.md): Show a video on the browser camera to test QR scanning, barcode scanning, and document capture - [Dialog Handling](https://docs.qa.tech/test-features/dialog-handling.md): How QA.tech handles browser dialogs (alerts, confirms, prompts) during automated testing - [Dynamic Navigation](https://docs.qa.tech/test-features/dynamic-navigation.md): How the AI agent navigates to URLs that change during test execution - [Copy and Paste](https://docs.qa.tech/test-features/copy-paste.md): Share clipboard values between web tests in the same Resume From session chain. - [API Testing](https://docs.qa.tech/core-concepts/api-testing.md): Test REST and HTTP APIs with an AI agent that writes and runs validation code in an isolated sandbox - [Creating API Tests](https://docs.qa.tech/best-practices/creating-api-tests.md): Create an API application, configure access, and write focused tests for your HTTP endpoints - [Mobile App Testing](https://docs.qa.tech/test-features/mobile-app-testing.md): Test native iOS and Android apps with AI-powered automation - [Test Data](https://docs.qa.tech/core-concepts/test-data.md): How to give tests credentials, emails, and other values without hardcoding them into the steps. - [Configs](https://docs.qa.tech/core-concepts/configs.md): Manage reusable test variables and data across your tests - [Config Environment Overrides](https://docs.qa.tech/core-concepts/config-environment-overrides.md): How config environment overrides are stored, merged, and resolved at runtime. - [Device Presets](https://docs.qa.tech/test-features/device-presets.md): Configure browser sessions with predefined device settings - [Test Responsiveness](https://docs.qa.tech/test-features/test-responsiveness.md): Verify layouts across viewports and device types with device presets. - [Authentication](https://docs.qa.tech/best-practices/handle-auth.md): Choose how the agent signs in: credentials, email OTP, magic link, TOTP, API key, SMS, or BankID. - [BankID](https://docs.qa.tech/applications/se-bank-id.md): Test BankID login flows by stubbing BankID in your test environment or authenticating manually through the live screen stream. - [Email Inbox](https://docs.qa.tech/test-features/email-inbox.md): Access and manage test emails during automated testing - [SMS Inbox](https://docs.qa.tech/test-features/sms-inbox.md): Receive SMS OTP codes and messages during tests with a leased phone number. - [Cross-Application Tests](https://docs.qa.tech/test-features/cross-application-tests.md): Coordinate tests that span more than one application in the same project. - [PR Testing](https://docs.qa.tech/pr-testing/overview.md): Review a pull request on a preview environment before merge, or against the deployed environment after merge. - [PR Testing](https://docs.qa.tech/best-practices/pr-testing.md): Get better PR reviews by giving the QA.tech agent the context it needs. - [Web pull request testing](https://docs.qa.tech/pr-testing/agents/web.md): How a change review finds the preview URL for a web application. - [Mobile pull request testing](https://docs.qa.tech/pr-testing/agents/mobile.md): Upload each pull request iOS or Android build and review that binary. - [API pull request testing](https://docs.qa.tech/pr-testing/agents/api.md): A change review can run an API application when you pass its preview base URL. - [GitHub pull request testing](https://docs.qa.tech/pr-testing/github.md): Review a GitHub pull request on a preview URL, after merge, or against a mobile build. - [PR triage](https://docs.qa.tech/pr-testing/pr-triage.md): Suggested prompts for skipping pull requests that should not be tested. - [GitHub Deployments](https://docs.qa.tech/configuration/github-deployments.md): Create GitHub deployment records from GitHub Actions so QA.tech can find and test pull request previews - [GitLab pull request testing](https://docs.qa.tech/pr-testing/gitlab.md): Review a GitLab merge request on a preview URL, after merge, or against a mobile build. - [Bitrise pull request testing](https://docs.qa.tech/pr-testing/bitrise.md): Review a mobile pull request build from Bitrise by calling the change review API. - [fastlane pull request testing](https://docs.qa.tech/pr-testing/fastlane.md): Review a mobile pull request build from a fastlane lane by calling the change review API. - [Envoyer pull request testing](https://docs.qa.tech/pr-testing/envoyer.md): Envoyer does not review pull requests. It can only start a test plan after a deploy. - [API pull request testing](https://docs.qa.tech/pr-testing/api.md): Start a pull request review from any CI that can send an HTTP request. - [Regression Testing](https://docs.qa.tech/regression-testing/overview.md): Run a test plan from CI after a deploy, on a schedule, or by hand. - [Regression review agent](https://docs.qa.tech/regression-testing/regression-review-agent.md): How the agent investigates every test plan result, retries suspected flakes, and writes one verdict. - [Test plans](https://docs.qa.tech/core-concepts/test-plans.md): Test Plans allow you to organize and manage groups of test cases that can be executed together as a single unit. - [Running Tests](https://docs.qa.tech/best-practices/running-tests.md): Run tests from the app, as part of a pipeline, or on a schedule. - [How to review test results](https://docs.qa.tech/best-practices/test-results.md): Choose the right testing approach for each stage of your workflow and review the results efficiently. - [Tests and Results](https://docs.qa.tech/core-concepts/tests-and-results.md): Scenarios are groups of test cases that belong together - [Issues](https://docs.qa.tech/core-concepts/issues.md): QA.tech automatically detects issues during test runs, including failed tests, JavaScript console errors, and WCAG accessibility violations. - [Notifications](https://docs.qa.tech/core-concepts/notifications.md): Notify your team when runs complete and send weekly summaries, configured per project, per test plan, or per run. - [Time Saved](https://docs.qa.tech/core-concepts/time-saved.md): How QA.tech estimates the minutes human QA testers would have spent running the same tests. - [Web regression testing](https://docs.qa.tech/regression-testing/agents/web.md): Point a test plan at an environment URL and a device preset for each web application. - [Mobile regression testing](https://docs.qa.tech/regression-testing/agents/mobile.md): Pin a test plan to an uploaded application build instead of a preview URL. - [API regression testing](https://docs.qa.tech/regression-testing/agents/api.md): Run an API application's tests from a test plan against a base URL, with configs for credentials. - [GitHub regression testing](https://docs.qa.tech/regression-testing/github.md): Run a test plan from GitHub Actions after a deploy or as a blocking check. - [GitLab regression testing](https://docs.qa.tech/regression-testing/gitlab.md): Run a test plan from GitLab CI after a deploy or as a blocking job. - [Bitrise regression testing](https://docs.qa.tech/regression-testing/bitrise.md): Run a test plan from Bitrise against an uploaded mobile build or a web URL. - [fastlane regression testing](https://docs.qa.tech/regression-testing/fastlane.md): Add a fastlane lane that uploads each new iOS or Android build and runs a test plan against it. - [Envoyer regression testing](https://docs.qa.tech/regression-testing/envoyer.md): Start a test plan from an Envoyer deployment hook after a PHP deploy. - [API regression testing](https://docs.qa.tech/regression-testing/api.md): Run a test plan from any system that can send an HTTP request, including a CI QA.tech has no plugin for. - [GitHub](https://docs.qa.tech/configuration/github-app.md): Connect the GitHub App for automatic PR reviews, or use GitHub Actions workflows for reviews and test plans. - [GitLab Merge Request Reviews and CI/CD](https://docs.qa.tech/configuration/gitlab.md): Set up automated GitLab merge request reviews and API-driven test runs - [Bitrise](https://docs.qa.tech/configuration/bitrise.md): Trigger QA.tech test runs from Bitrise CI/CD: upload your Android or iOS build and run mobile test plans automatically - [fastlane](https://docs.qa.tech/configuration/fastlane.md): Trigger QA.tech test runs from fastlane: upload your Android or iOS build and test it from a lane - [Envoyer](https://docs.qa.tech/configuration/envoyer.md): Start a QA.tech test plan from an Envoyer deployment hook after each deploy - [API setup for any CI](https://docs.qa.tech/configuration/ci-cd-integration.md): Create an API key, store it in your CI, and find the short IDs a pipeline needs to call QA.tech. - [MCP Server](https://docs.qa.tech/integrations/mcp.md): Connect Claude Code, Cursor, Codex, ChatGPT, Continue, or Linear Agent to QA.tech so your AI assistant can list test cases, start runs, and read results. - [Custom MCP Integrations](https://docs.qa.tech/integrations/custom-mcp.md): Connect your own tools and services to the QA.tech AI chat through MCP servers, with per-tool permissions. - [Slack](https://docs.qa.tech/integrations/slack.md): Send test run notifications to Slack, and optionally let chat read, post, and share images - [Microsoft Teams](https://docs.qa.tech/integrations/microsoft-teams.md): Receive QA.tech notifications in Microsoft Teams channels - [Status Badges](https://docs.qa.tech/integrations/status-badges.md): Visual indicators for your project test status - [Jira](https://docs.qa.tech/integrations/jira.md): Let the QA.tech agent read Jira issues for PR reviews and test planning - [Linear](https://docs.qa.tech/integrations/linear.md): Connect Linear Agent to QA.tech MCP, and let the QA.tech assistant search and create Linear issues - [Trello](https://docs.qa.tech/integrations/trello.md): Export QA.tech-detected issues to Trello - [TestRail](https://docs.qa.tech/integrations/testrail.md): Pull your existing TestRail cases into the QA.tech AI chat and turn them into tests - [Xray](https://docs.qa.tech/integrations/xray.md): Pull your existing Xray (Jira) tests into the QA.tech AI chat and turn them into tests - [API Introduction](https://docs.qa.tech/api-reference/introduction.md): Learn how to interact with QA.tech programmatically using our REST API - [Applications API](https://docs.qa.tech/api-reference/applications.md): List applications and their environments, and set the build a mobile environment uses - [Application Builds API](https://docs.qa.tech/api-reference/application-builds.md): Upload and manage mobile app builds for testing - [Chat API](https://docs.qa.tech/api-reference/chat.md): Interact with the QA.tech AI Chat Assistant programmatically - [Remote Tunnels API](https://docs.qa.tech/api-reference/remote-tunnels.md): Create and manage secure tunnels to expose local environments - [Exporting Test Cases](https://docs.qa.tech/api-reference/exporting-test-cases.md): Export your test case definitions, including steps, via the API or CLI - [List applications](https://docs.qa.tech/api-reference/applications/list-applications.md): Lists the applications under test in the project the API key is bound to. - [Create application](https://docs.qa.tech/api-reference/applications/create-application.md): Create a web or API application and its default environment. - [List application environments](https://docs.qa.tech/api-reference/applications/list-application-environments.md): List environments for a specific application - [Set environment build](https://docs.qa.tech/api-reference/applications/set-environment-build.md): Set the mobile build an environment launches by default, as Settings → Applications & Envs does. - [List application builds](https://docs.qa.tech/api-reference/application-builds/list-application-builds.md): Lists mobile builds that can be used as primary or other apps in environment overrides. - [Create application build](https://docs.qa.tech/api-reference/application-builds/create-application-build.md): Step 2 of 2 for attaching a mobile build: registers a file already uploaded via `application_build_upload_url`. Pass the `buildToken` returned by that tool (after you PUT the file to its `uploadUrl`). Returns `applicationBuildShortId` — use it as `environment.applicationBuildShortId` inside an `appl… - [Get build upload URL](https://docs.qa.tech/api-reference/application-builds/get-build-upload-url.md): Step 1 of 2 for attaching a mobile build (.apk/.ipa) to a run. Returns a presigned `uploadUrl` and a `buildToken`. Next, upload the raw build file to `uploadUrl` with an HTTP PUT request (request body = the raw file bytes, `Content-Type` = the file's MIME type such as `application/octet-stream`; no… - [List automations](https://docs.qa.tech/api-reference/automations/list-automations.md): List the project's automations: "when X, do Y" rules that start a chat-assistant task, a test plan run or a pull request review on a schedule, from an API call or from a GitHub pull request event. Includes each automation's trigger, action, enabled state, and last/next fire time. - [Create automation](https://docs.qa.tech/api-reference/automations/create-automation.md): Create an automation. Triggers: `schedule` (5-field cron evaluated in an IANA timezone, optionally `once`), `api_webhook` (fired only through the trigger endpoint) or `github_event` (pull request opened, labeled, merged and so on in a connected repository, filtered by labels, base branches and repos… - [Delete automation](https://docs.qa.tech/api-reference/automations/delete-automation.md): Permanently delete an automation. Its past runs stay in the project's history. To pause instead, update it with `isEnabled: false`. - [Update automation](https://docs.qa.tech/api-reference/automations/update-automation.md): Update an automation's name, description, enabled state, trigger or action. `trigger` and `action` replace the stored value as a whole. Set `isEnabled` to pause or resume it. - [Trigger automation](https://docs.qa.tech/api-reference/automations/trigger-automation.md): Fire a `schedule` or `api_webhook` automation on demand. Use this from CI, deploy hooks, or monitoring to start the automation's chat-based workflow with your own context. Returns 202 immediately, or 409 when the automation is disabled or its trigger only fires from its own event. - [Get example status badge](https://docs.qa.tech/api-reference/status-badge/get-example-status-badge.md): Get a sample status badge as SVG (no token). For live project badges use GET /v1/badge.svg. - [Get status badge](https://docs.qa.tech/api-reference/status-badge/get-status-badge.md): Get status badge as SVG. Authenticate with the token query parameter (not the API Bearer key). Project is resolved from the token. - [Start chat conversation](https://docs.qa.tech/api-reference/chat/start-chat-conversation.md): Create a new chat conversation and send its first message. - [Start change review chat](https://docs.qa.tech/api-reference/chat/start-change-review-chat.md): Start an autonomous change review from either a PR URL or raw change input. Returns 202 with the review conversation. - [Prepare change review](https://docs.qa.tech/api-reference/chat/prepare-change-review.md): Start a GitHub pull request's change review before its preview is deployed. Call it when the PR opens or gets a new commit. Returns 202 with the review conversation, reused the same way as `POST /chat/change-review`. - [Get chat conversation](https://docs.qa.tech/api-reference/chat/get-chat-conversation.md): Get conversation metadata, associated test runs, and recent messages (newest first). - [Send chat message](https://docs.qa.tech/api-reference/chat/send-chat-message.md): Send a chat message to an existing conversation. - [List features](https://docs.qa.tech/api-reference/features/list-features.md): List features in the project's feature graph. Features are LLM-clustered groupings of related UI actions discovered during crawling, and describe what the product can do. - [Get feature](https://docs.qa.tech/api-reference/features/get-feature.md): Fetch detail for a single feature, including pages it spans and actions that belong to it - [List issues](https://docs.qa.tech/api-reference/issues/list-issues.md): Lists issues QA.tech has found in the project, deduplicated across the runs where they recur and sorted by most recent occurrence (newest first). Defaults to `ACTIVE` issues; filter by `severity`, `status`, or a `since`/`until` window. Each issue includes its severity, status, type, a help URL, time… - [Get issue](https://docs.qa.tech/api-reference/issues/get-issue.md): Fetches a single issue by its short ID, including its tags and the recent run test cases where it was detected (newest first). Use the occurrences' `runTestCaseShortId` with `get_run_test_case` to inspect what the agent saw. - [Update issue status](https://docs.qa.tech/api-reference/issues/update-issue-status.md): Ignores or reopens an issue, the same as the Ignore and Reopen actions in the dashboard. Set `status` to `IGNORED` to dismiss an issue you have triaged or consider a false positive, or `ACTIVE` to put it back in the default list. - [List knowledge items](https://docs.qa.tech/api-reference/knowledge/list-knowledge-items.md): List the project's knowledge base items: text notes, crawled links, uploaded PDFs, agent memories and UI icons. Returns summaries without content; fetch a single item for its full content. - [Create knowledge item](https://docs.qa.tech/api-reference/knowledge/create-knowledge-item.md): Add an item to the project's knowledge base and index it for the QA.tech agents. Use `text` for documentation notes, `link` to crawl and index a URL, or `memory` for agent-maintained observations. PDF and icon items are managed in the dashboard. - [Get knowledge item](https://docs.qa.tech/api-reference/knowledge/get-knowledge-item.md): Fetch a single knowledge item including its full text content - [Delete knowledge item](https://docs.qa.tech/api-reference/knowledge/delete-knowledge-item.md): Delete a knowledge item and remove it from the agents' knowledge index - [Update knowledge item](https://docs.qa.tech/api-reference/knowledge/update-knowledge-item.md): Update a text, link or memory knowledge item. Changing content or url re-indexes the item; pdf and icon items are managed in the dashboard. - [List labels](https://docs.qa.tech/api-reference/labels/list-labels.md): List the project's labels with their colors. Reuse an existing label name when tagging test cases instead of inventing a near-duplicate. - [Create label](https://docs.qa.tech/api-reference/labels/create-label.md): Create a label for organizing test cases. Labels are also created implicitly when a test case is saved with a new label name; use this to pick the color. - [Delete label](https://docs.qa.tech/api-reference/labels/delete-label.md): Delete a label. It is removed from every test case that carries it; the test cases themselves are kept. - [Update label](https://docs.qa.tech/api-reference/labels/update-label.md): Rename a label or change its color. A rename applies to every test case that carries the label. - [Get project metrics](https://docs.qa.tech/api-reference/metrics/get-project-metrics.md): Prometheus text exposition format for the project bound to the API key. - [Get outbound IPs](https://docs.qa.tech/api-reference/infrastructure/get-outbound-ips.md): Get the current outbound IP addresses QA.tech test runners use, for firewall rules and allowlists. No authentication required. - [List projects](https://docs.qa.tech/api-reference/projects/list-projects.md): Lists the projects in the organization the API key belongs to. Organization-scoped keys see every project; project-scoped keys see only their own. Returned `shortId`s can be passed as `projectShortId` to any project-scoped tool to target that project. - [Create project](https://docs.qa.tech/api-reference/projects/create-project.md): Create a new project in the organization the API key belongs to. Requires an organization-scoped API key with write scope. - [List remote tunnels](https://docs.qa.tech/api-reference/remote-tunnels/list-remote-tunnels.md): List remote tunnels for the authenticated project - [Create remote tunnel](https://docs.qa.tech/api-reference/remote-tunnels/create-remote-tunnel.md): Create a new remote tunnel that exposes local ports via Cloudflare. - [Get remote tunnel](https://docs.qa.tech/api-reference/remote-tunnels/get-remote-tunnel.md): Get a remote tunnel by runner ID - [Delete remote tunnel](https://docs.qa.tech/api-reference/remote-tunnels/delete-remote-tunnel.md): Tear down a remote tunnel and its DNS records - [Get remote tunnel status](https://docs.qa.tech/api-reference/remote-tunnels/get-remote-tunnel-status.md): Get the live Cloudflare health status of a remote tunnel - [List rules](https://docs.qa.tech/api-reference/rules/list-rules.md): List the project's rules: standing instructions injected into the QA.tech agents. Filter by consumer to see rules for the chat assistant, the test agent, or PR review. - [Create rule](https://docs.qa.tech/api-reference/rules/create-rule.md): Create a rule: a standing instruction injected into a QA.tech agent's context. Agent rules support filters to target specific applications, labels, scenarios or URL paths. - [Delete rule](https://docs.qa.tech/api-reference/rules/delete-rule.md): Delete a rule so it is no longer injected into the agent's context - [Update rule](https://docs.qa.tech/api-reference/rules/update-rule.md): Update a rule's title, content, filters or sort order. Pass null on a filter field to clear it. - [List runs](https://docs.qa.tech/api-reference/runs/list-runs.md): Lists runs for the project, newest first. With no filters it returns the 20 most recent runs across all time; pass `since`/`until` (ISO 8601) to scope to a window such as the last 24 hours. Returned `shortId`s work directly with `get_run` and `rerun_run`. - [Start test run](https://docs.qa.tech/api-reference/runs/start-test-run.md): Execute a run for a given project. Supports API, GITHUB, or GITLAB trigger. For version-control triggers, provide actor, branch, commitHash, commitMessage, and repository. For GITLAB, also provide repositoryUrl so links work with GitLab.com and self-hosted instances. Use applications to override env… - [Get run test case](https://docs.qa.tech/api-reference/runs/get-run-test-case.md): Fetches a single run test case (one test's execution within a run) by its short ID — the `` in a `/results/test/` URL. Returns the goal and success criteria, the result and error classification, the evaluator's full assessment (verdict summary, expected vs actual behavior, root-cau… - [Get test case history](https://docs.qa.tech/api-reference/runs/get-test-case-history.md): Returns the recent pass/fail history and durations for the test case behind a run test case short ID, across its most recent runs — for flaky-vs-consistent analysis. - [Get run test case logs](https://docs.qa.tech/api-reference/runs/get-run-test-case-logs.md): Returns the telemetry captured while a run test case executed: browser network requests (`network`), browser console output (`console`), or server-side API calls made by API tests (`apiCalls`, with truncated request/response bodies). Filter by URL regex and status to find the failing request behind… - [Get run test case screenshots](https://docs.qa.tech/api-reference/runs/get-run-test-case-screenshots.md): Returns screenshots of selected execution steps of a run test case, so the visible state can be checked directly. Step indices are the 0-based `[step:N]` references and `keyObservations[].stepIndex` from `get_run_test_case`'s assessment. Omit `steps` for the final screenshot. MCP clients receive eac… - [Get run test case trace](https://docs.qa.tech/api-reference/runs/get-run-test-case-trace.md): Returns the agent's step-by-step action trace for a run test case: per step the reasoning, the tools it called with their arguments, the observed result, and a screenshot. Paginated via `limit`/`offset` so large traces don't overflow token limits. - [Get run](https://docs.qa.tech/api-reference/runs/get-run.md): Fetches a run by its short ID. Pass `testCases: "all"` or `"failed"` to include nested test-case results, and `issues` to include detected issues (`all` or a category such as `accessibility`; omitted by default). Use `get_run_issues` to fetch only the issues. - [Rerun run](https://docs.qa.tech/api-reference/runs/rerun-run.md): Reruns a previous run. Pass `failedOnly: true` to rerun only failed/skipped/errored cases, or `projectTestCaseIds` to rerun a specific subset. - [Cancel run](https://docs.qa.tech/api-reference/runs/cancel-run.md): Stops a run that is still `INITIATED` or `RUNNING`, the same as the Stop button in the dashboard. Tests that have not finished are cancelled and this cannot be undone; start a new run with `rerun_run`. Returns 409 if the run has already finished. - [Get run issues](https://docs.qa.tech/api-reference/runs/get-run-issues.md): Lists issues detected during a run, deduplicated and aggregated across its test cases. Returns every issue type by default; pass `issueType` to filter to one category (e.g. `accessibility`). Each issue includes its type, severity, tags, a help URL, and the test cases where it was found. - [Export run test record](https://docs.qa.tech/api-reference/runs/export-run-test-record.md): Start building a test record archive for a finished run: a zip with a README in a regulatory test record layout (EU MDR, IEC 62304, ISO 13485, ISO/IEC/IEEE 29119-3), every test step and action with screenshots and recordings, the raw logs, JUnit XML and a manifest with the SHA-256 of every file. The… - [Get run export](https://docs.qa.tech/api-reference/runs/get-run-export.md): Fetch a run export. Once `status` is `completed` the response carries a `downloadUrl` valid for one hour; fetch the export again for a fresh one. - [List test cases](https://docs.qa.tech/api-reference/test-cases/list-test-cases.md): Lists test cases for the project, optionally filtered by application, labels, enabled state, or scenario. - [Create test case](https://docs.qa.tech/api-reference/test-cases/create-test-case.md): Create a test case in the project. It is created in draft and a burn-in run starts automatically against the application's default environment, or against `environment` when given (e.g. a preview deployment or remote tunnel URL). - [Get test case](https://docs.qa.tech/api-reference/test-cases/get-test-case.md): Fetches a test case's authored configuration by its ID (UUID, as returned by `list_test_cases`): goal, expected result, steps, start URL path, dependencies, labels, enabled state, and scenario. This is the authored config the agent executes — for a specific run's outcome use `get_run_test_case` inst… - [Update test case](https://docs.qa.tech/api-reference/test-cases/update-test-case.md): Updates a test case's authored configuration. Patch semantics: only the fields you provide change; pass `null` on nullable fields (`startUrlPath`, `scenarioShortId`, `resumeFromDependencyProjectTestCaseId`) to clear them. - [List test plans](https://docs.qa.tech/api-reference/test-plans/list-test-plans.md): List the project's test plans: named sets of test cases that run together. Returned `shortId`s can be passed to `start_run_with_test_plan`. - [Create test plan](https://docs.qa.tech/api-reference/test-plans/create-test-plan.md): Create a test plan, optionally with test cases. Returns the plan with its `shortId`, which can be passed to `start_run_with_test_plan`. - [Get test plan](https://docs.qa.tech/api-reference/test-plans/get-test-plan.md): Fetch a test plan with the test cases it contains - [Delete test plan](https://docs.qa.tech/api-reference/test-plans/delete-test-plan.md): Delete a test plan and its run schedules. Test cases and past runs are kept. Automations that run this plan will fail until they are pointed at another plan. - [Update test plan](https://docs.qa.tech/api-reference/test-plans/update-test-plan.md): Update a test plan's name, description or review instructions, and add or remove test cases in the same call. Returns the updated plan. - [List todos](https://docs.qa.tech/api-reference/todos/list-todos.md): Lists todos for the project. With no status and no query, returns open todos. A query with no status searches every status. Pass a returned shortId to fetch one todo. - [Create todo](https://docs.qa.tech/api-reference/todos/create-todo.md): Creates a new open todo. This always inserts; it does not match or reopen an existing todo. Use the MCP `manage_todos` create action when an agent should attach to an existing need instead. - [Get todo](https://docs.qa.tech/api-reference/todos/get-todo.md): Fetches one todo by short ID, including recent occurrences. A UUID is also accepted. - [Update todo](https://docs.qa.tech/api-reference/todos/update-todo.md): Updates a todo. Only the fields you pass change. Set status to `resolved` or `rejected` to close it. Rejecting requires `rejectedReason`. There is no delete: rejected todos are kept so they are not filed again. - [CLI Overview](https://docs.qa.tech/cli/overview.md): Run QA.tech tests, inspect results, expose local servers, and chat with the QA.tech agent from the terminal. - [qatech configure](https://docs.qa.tech/cli/commands/configure.md): Set up and inspect your QA.tech CLI credentials. - [qatech test-cases](https://docs.qa.tech/cli/commands/test-cases.md): List and search test cases in your project. - [qatech applications](https://docs.qa.tech/cli/commands/applications.md): List the applications in your QA.tech project. - [qatech environments](https://docs.qa.tech/cli/commands/environments.md): List the environments configured for an application. - [qatech run](https://docs.qa.tech/cli/commands/run.md): Start a test run by test plan or individual test cases. - [qatech status](https://docs.qa.tech/cli/commands/status.md): Check or wait for the result of a test run. - [qatech chat](https://docs.qa.tech/cli/commands/chat.md): Talk to the QA.tech agent - get test IDs, ask about coverage, and run tests against custom URLs. - [qatech tunnel](https://docs.qa.tech/cli/commands/tunnel.md): Expose local ports to QA.tech and run tests against your dev server. - [qatech init](https://docs.qa.tech/cli/commands/init.md): Generate Claude Code subagent and skill files for the QA.tech CLI. ## OpenAPI Specs - [api](/api-reference/api.json) - [package](/package.json) ## Optional - [Blog](https://qa.tech/blog/) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.