llms.txt
Compare with other sites' llms.txt files →# QA.tech
> QA.tech is an AI testing platform for web and mobile applications. Autonomous QA agents explore your product the way a user does, then run regression, exploratory and end-to-end tests on every pull request and release, without hand-written selectors or test scripts to maintain.
Vision-based agents interact with the real UI, so tests survive markup and layout changes. Tests are described in plain English; the agent works out the steps and reports what broke. Runs happen on every pull request and on a schedule, posting results into GitHub, GitLab, Slack and Jira. Coverage spans web apps, mobile apps on iOS and Android, and API-backed flows including authenticated journeys. Teams using QA.tech include Pricer, Upsales, Strise, Virtusize, 4C Strategies and Airpelago.
Pricing: Starter is $89 a month with 50 credits included (web, exploratory and pull-request testing, up to 10 users). Growth and Enterprise add mobile, API and voice testing and are priced to volume. Details: https://qa.tech/pricing
Every indexable page has a markdown twin. Append `.md` to any path (for example https://qa.tech/blog/what-is-agentic-testing.md), or request the normal URL with an `Accept: text/markdown` header and the markdown version is returned. Each HTML page also advertises its twin via `<link rel="alternate" type="text/markdown">`.
The REST API and the MCP server share the same tokens and the same base host, https://api.qa.tech. Error responses from QA.tech endpoints are JSON with a stable `code`, a human `message`, a resolution `hint` and a `docs` link.
## Start here
- [Product documentation](https://docs.qa.tech): how the product works, setup guides, API reference.
- [Sitemap](https://qa.tech/sitemap.xml): every indexable page on qa.tech.
- [App login](https://app.qa.tech): the QA.tech application.
- [Crawler policy and content signals](https://qa.tech/robots.txt): robots directives for this site.
## Developer resources (API, MCP, auth, webhooks)
- [QA.tech developer hub](https://qa.tech/developers): one page listing the API docs, OpenAPI spec, auth, MCP server, webhooks and CLI by name.
- [QA.tech API documentation](https://docs.qa.tech/api-reference/introduction): REST API reference – runs, test cases, issues, applications, mobile builds and tunnels.
- [QA.tech OpenAPI specification](https://docs.qa.tech/api-reference/api.json): machine-readable OpenAPI 3 document, including security schemes and server base URL.
- [QA.tech API authentication](https://docs.qa.tech/api-reference/introduction#authentication): bearer API keys (org- or project-scoped, read or write) and OAuth sign-in for interactive clients.
- [QA.tech MCP server](https://qa.tech/product/mcp): endpoint https://api.qa.tech/v1/mcp, streamable HTTP, OAuth sign-in or bearer API key.
- [QA.tech MCP setup guide](https://docs.qa.tech/integrations/mcp): client configuration for Cursor, Claude Code, Claude Desktop, Codex and Continue.
- [QA.tech MCP server card](https://qa.tech/.well-known/mcp/server-card.json): machine-readable MCP descriptor (endpoint, transport, auth methods, tools).
- [QA.tech API authentication doc](https://qa.tech/.well-known/auth.md): markdown summary of bearer keys, OAuth sign-in and the JSON error shape.
- [QA.tech agent skills](https://qa.tech/.well-known/agent-skills.json): machine-readable list of what agents can do on qa.tech and through the API.
- [QA.tech API catalog](https://qa.tech/.well-known/api-catalog): RFC 9727 linkset pointing at the OpenAPI document and API docs.
- [QA.tech webhooks and integrations](https://docs.qa.tech/integrations/webhooks): run-completed and issue events delivered to your endpoint; GitHub, GitLab, Slack and Jira integrations.
- [QA.tech CLI](https://www.npmjs.com/package/@qadottech/cli): `npx @qadottech/cli mcp configure` wires the MCP server into supported clients.
## Product
- [Web testing](https://qa.tech/product/web-testing): Autonomous agents run end-to-end tests on web apps without scripted selectors.
- [Mobile testing](https://qa.tech/product/mobile-testing): Agentic testing for iOS and Android apps on real device configurations.
- [Voice testing](https://qa.tech/product/voice-testing): Agents speak into your app's microphone input and verify the transcript, action or request.
- [API testing](https://qa.tech/product/api-testing): An AI agent turns plain-language goals into HTTP requests and validation code, then proves the contract.
- [Pull request testing](https://qa.tech/product/pr-testing): Every PR gets exploratory and regression runs, with results posted back to GitHub or GitLab.
- [MCP server](https://qa.tech/product/mcp): Connect QA.tech to coding agents and IDEs over the Model Context Protocol.
- [AI QA testing](https://qa.tech/ai-qa-testing): How AI-driven QA differs from scripted automation and manual testing.
- [Product quality audit](https://qa.tech/product-quality-audit): An agent-run audit of your product's current quality and coverage gaps.
- [Pricing](https://qa.tech/pricing): Plans and what is included in each.
## Solutions and industries
- [For CTOs and engineering leaders](https://qa.tech/solutions/ctos): Ship faster without growing a manual QA team.
- [For QA engineers](https://qa.tech/solutions/qa-testers): Hand repetitive regression work to agents and focus on hard test design.
- [For SaaS teams](https://qa.tech/saas): Continuous coverage for fast-moving SaaS products.
- [For e-commerce](https://qa.tech/industries/ecommerce): Checkout, payment and catalogue flows tested on every release.
## Company
- [About QA.tech](https://qa.tech/about-us): Who we are and why we build autonomous QA agents.
- [Vision](https://qa.tech/vision): Where we think software testing is heading.
- [Press](https://qa.tech/press): Press releases and media coverage.
- [Events](https://qa.tech/events): Webinars, meetups and conference appearances.
- [Partnerships](https://qa.tech/partnerships): Agency, reseller and technology partnerships.
- [Contact](https://qa.tech/contact): Get in touch with the team.
- [Book a demo](https://qa.tech/demo): See agentic QA running against your own product.
- [Privacy policy](https://qa.tech/privacy-policy): How we handle customer and test data.
## Resources
- [Blog](https://qa.tech/blog): Guides and analysis on AI testing, QA strategy and release quality.
- [Case studies](https://qa.tech/case-studies): How teams like Pricer, Upsales and Strise run QA with agents.
- [Changelog](https://qa.tech/changelog): Product updates, shipped weekly.
- [Comparisons](https://qa.tech/compare): QA.tech against Playwright, Cypress, mabl, QA Wolf and others.
- [Ebook: Past the bottleneck](https://qa.tech/ebooks/past-the-bottleneck): A practical guide to removing QA as a release bottleneck.
- [Ebook: Adopting agentic testing](https://qa.tech/ebooks/adopting-agentic-testing): How to roll out AI QA agents across an engineering org.
## Comparisons
- [BrowserStack Alternatives in 2026: Every Grid Changes the Bill, Not the Suite](https://qa.tech/compare/browserstack-alternatives): Looking for a BrowserStack alternative? What the grid market actually costs, checked 6 Oct 2026, what every one of them still leaves you maintaining, and QA.te…
- [Playwright Alternatives in 2026: The AI Tools That Still Write Playwright, and the One That Doesn't](https://qa.tech/compare/playwright-alternatives): Looking for a Playwright alternative? Most AI testing tools generate more Playwright for you to maintain. QA.tech runs plain-language goals with no suite file…
- [Selenium Alternatives in 2026: Six Frameworks That Keep the Scripts, and the One That Doesn't](https://qa.tech/compare/selenium-alternatives): Leaving Selenium? Six frameworks compared on what each fixes and what it still leaves you maintaining, and QA.tech, the alternative with no scripts at all. Che…
- [TestSprite Alternatives in 2026: Six Agentic Testing Tools, and What Each One Leaves in Your Repo](https://qa.tech/compare/testsprite-alternatives): Weighing TestSprite alternatives? TestSprite leaves a Python Playwright suite in your repo and its PR integration only replays it. Six tools compared with pric…
- [CodeRabbit Alternatives in 2026: What People Switch To, and What None of Them Change](https://qa.tech/compare/coderabbit-alternatives): Looking for a CodeRabbit alternative? Here are the six tools teams move to, what each costs today, and the one thing every AI code reviewer still skips: runnin…
- [Cursor Bugbot Alternatives in 2026: For Teams Not Fully on Cursor, and the Check Bugbot Can't Do](https://qa.tech/compare/cursor-bugbot-alternatives): Need a Cursor Bugbot alternative because half your team isn't on Cursor, or the per-run bill is unpredictable? Five reviewers compared with current pricing, an…
- [GitHub Copilot Code Review Alternatives in 2026: When to Replace It, When to Add to It](https://qa.tech/compare/github-copilot-code-review-alternatives): Copilot code review is the default for GitHub teams, and if you're searching for an alternative you may not need to replace it. Five reviewers compared with cu…
- [Greptile Alternatives in 2026: Five Reviewers Compared, and Why Sandbox Tests Aren't the Same as Running Your Product](https://qa.tech/compare/greptile-alternatives): Looking at Greptile alternatives over credit overages or early noise? Five reviewers with current pricing, what Greptile's TREX sandbox mode does and doesn't r…
- [Qodo Alternatives in 2026: Five Reviewers to Compare, and the Half of Qodo That Went Away](https://qa.tech/compare/qodo-alternatives): Comparing Qodo Merge alternatives? Five reviewers with current pricing, what happened to Qodo's test generation, and why swapping reviewers never gets you a to…
- [QA.tech vs. Claude + Playwright](https://qa.tech/compare/qa-tech-vs-claude-playwright): Claude + Playwright makes test generation cheap. It doesn't make tests reliable, maintainable, or strategic. See how QA.tech's AI agents compare – and when eac…
- [QA.tech vs. Cypress (2026): Honest Comparison](https://qa.tech/compare/qa-tech-vs-cypress): QA.tech vs. Cypress in 2026 – a side-by-side breakdown of test maintenance, speed, coverage, and total cost. When Cypress fits, when it doesn't, and when to ru…
- [QA.tech vs. Mabl (2026): Honest Comparison](https://qa.tech/compare/qa-tech-vs-mabl): QA.tech vs. Mabl in 2026 – an honest breakdown of low-code vs. [agentic testing](/blog/what-is-agentic-testing), maintenance cost, and which approach scales wi…
- [QA.tech vs. Playwright (2026): Honest Comparison](https://qa.tech/compare/qa-tech-vs-playwright): QA.tech vs. Playwright in 2026 – maintenance tax, AI agents, CI integration, and 36-month cost. When to pick each, when to run both.
- [QA.tech vs. QA Wolf (2026): Honest Comparison](https://qa.tech/compare/qa-tech-vs-qa-wolf): QA.tech vs. QA Wolf in 2026 – AI agents vs. managed services. Speed, control, coverage, and 36-month cost compared. Which fits your team.
## Customer case studies
- [4C Strategies scales testing with AI automation](https://qa.tech/case-studies/4c-strategies-replaces-manual-testing-with-ai): 4C Strategies overcame massive testing bottlenecks by using QA.tech's AI agents to read dense user manuals and autonomously test highly customized workflows.
- [Bizbrains automates UI testing for continuous delivery](https://qa.tech/case-studies/bizbrains-ui-testing-automation): Bizbrains replaced brittle test scripts with AI agents, automating complex UI testing and enabling reliable continuous delivery through Azure DevOps integratio…
- [How Crystal Intelligence cut regression from weeks to hours](https://qa.tech/case-studies/crystal-intelligence-speeds-up-regression-testing): Crystal Intelligence automated complex canvas UI testing with AI, cutting regression from weeks to hours and enabling fast, reliable releases in CI/CD.
- [How JOIN automated QA with AI agents](https://qa.tech/case-studies/how-join-automated-qa-with-ai-agents): JOIN Solutions eliminated a severe QA bottleneck by transforming week-long manual regression testing into a automated test runs using QA.tech's AI agents.
- [Smartlinx replaced legacy QA processes with AI agents](https://qa.tech/case-studies/smartlinx-ai-qa-replacement): Smartlinx replaced a brittle legacy test framework with AI agents, rebuilding regression testing to improve reliability and reduce reliance on manual QA effort…
- [Airpelago – Scaling Drone Operations with Reliable End-to-End Testing](https://qa.tech/case-studies/airpelago---scaling-drone-operations-with-reliable-end-to-end-testing): Power-line drone ops needed stable map UI tests where Playwright flaked–Airpelago now runs agentic E2E on their top journeys several times a day and ships with…
- [How Upsales Replaced 320h of Manual Testing with Agents](https://qa.tech/case-studies/how-upsales-replaced-320h-of-manual-testing-with-agents): Upsales replaced 320+ hours of manual regression a month with QA.tech agents–keeping their sales CRM stable without scaling a dedicated manual QA team.
- [How AI Agents Saved Pricer’s QA Process](https://qa.tech/case-studies/how-pricer-transform-qa-with-qa-tech): From eight QA engineers to two, Pricer still grew ESL coverage with AI agents–fewer production bugs, faster releases, and about 390 hours of testing saved ever…
## Latest blog posts
- [The 18 Best Agentic QA Tools in 2026](https://qa.tech/blog/best-agentic-qa-tools-in-2026): Eighteen agentic QA tools, sorted on one question: does the tool replay a script, or does it decide what to test from the change in front of it? Updated Novemb…
- [Vercel deployment_status vs repository_dispatch: Triggering Tests on a Preview](https://qa.tech/blog/vercel-deployment-status-repository-dispatch): Vercel now recommends repository_dispatch over deployment_status for GitHub Actions. What changes for tests on preview deployments, and which event to use for…
- [One Pull Request, Four Vercel Previews: Which One Gets Tested?](https://qa.tech/blog/vercel-preview-multiple-deployments): Monorepos on Vercel get a preview per project on every pull request. How to make sure tests run against the app and not Storybook, and what to do with on-deman…
- [Vercel Protection Bypass for Automation: Six Ways It Breaks in Testing](https://qa.tech/blog/vercel-protection-bypass-automated-testing): Protection Bypass for Automation gets tests past Vercel's login page. Six failures that show up after you enable it, from new previews to auth redirects and th…
- [How to Increase Developer Velocity When AI Writes the Code](https://qa.tech/blog/how-to-increase-developer-velocity): Seven practices that raise developer velocity on AI-assisted teams, starting with testing every pull request on its own preview environment before merge.
- [Proof-Carrying Pull Requests Need a Verifier That Didn't Write the Code](https://qa.tech/blog/agent-proof-pull-requests): Teams now ask coding agents to attach proof to every PR. Screenshots from the agent that wrote the change are a self-report. What real proof looks like.
- [Dependabot Auto-Merge: What to Merge and What to Test First](https://qa.tech/blog/dependabot-auto-merge): A policy for Dependabot and Renovate PRs: auto-merge the safe updates, run end-to-end checks on framework and UI upgrades, and keep security patches fast.
- [DORA Metrics in the AI Era: What to Track When Agents Write the Code](https://qa.tech/blog/dora-metrics-ai-era): The five DORA metrics, why DORA paused its annual survey, and which numbers to trust when AI agents write a large share of your code.
- [Risk-Based Testing for Pull Requests: Skip, Test or Escalate](https://qa.tech/blog/risk-based-testing-pull-requests): Risk-based testing applied per pull request: which changes to skip, which to test lightly, and which deserve a full run and two reviewers.
- [Test Impact Analysis: Running Only the Tests a Change Can Break](https://qa.tech/blog/test-impact-analysis): What test impact analysis is, how predictive test selection works at Meta, Microsoft and Gradle, the main TIA tools, and where it struggles with end-to-end tes…
- [What are the 7 top QA automation tools in 2026?](https://qa.tech/blog/top-qa-automation-tools): Today, nobody wants to deal with manual testing because it could be time-wasting, energy-sapping, and more
- [What is functional testing?](https://qa.tech/blog/what-is-functional-testing): Functional testing checks that software does what it should. The standards definitions, functional vs non-functional, the types, and worked examples.
- [Automated exploratory testing: what agents can explore, and what they can't](https://qa.tech/blog/automated-exploratory-testing): What exploratory testing means, what changes when an AI agent does the exploring, five tools that try it, and the parts of the job no agent does yet.
- [Passing tests are not proof that the product works](https://qa.tech/blog/passing-tests-are-not-proof): A green suite says the assertions someone wrote still hold. It does not say the app works. What Meta, Cursor, Cloudflare and the METR study each show about the…
- [The Testing Pyramid in the Age of Agentic AI](https://qa.tech/blog/the-testing-pyramid-age-agentic-ai): The testing pyramid assumed E2E tests were expensive to keep. Agentic AI broke that assumption. Here is what replaces it: a lean regression suite plus dynamic…
- [Agents Already Gate the Merge. Nobody Agrees What Counts as Proof.](https://qa.tech/blog/who-gates-the-merge): Agents already decide which pull requests reach a human. What nobody has settled is what counts as evidence, and very little of it comes from the running produ…
- [AI testing strategy for SaaS teams: what to gate, schedule, and explore](https://qa.tech/blog/ai-testing-strategy-saas-teams): A placement-based AI testing strategy for SaaS: scoped checks on every PR, a small scheduled insurance suite, and exploratory testing for the rest.
- [QA tools for coding agents: 10 ways to check what Claude Code, Cursor and Codex ship](https://qa.tech/blog/qa-tools-for-coding-agents): Ten QA tools that check what Claude Code, Cursor and Codex ship, compared on who writes the tests, where they live and whether anything opens the running app.
- [Regression testing in the pull request: catching regressions before merge](https://qa.tech/blog/regression-testing-in-pull-requests): What regression testing in a pull request means, how it differs from the nightly suite on build, scope and verdict, and what to ask before gating a merge on it.
- [The Tokenburner: how teams burn budgets testing with Claude and Playwright without a harness](https://qa.tech/blog/tokenburner): Where the tokens go when a coding agent drives a browser, why cheaper models don't fix it, and the suite-scale arithmetic a harness amortizes.
- [Product quality in the AI SDLC: why the auditor cannot be the creator](https://qa.tech/blog/product-quality-ai-sdlc): When agents write the code, the constraint moves to verifying it. Why scripted tests and self-grading agents miss the same bugs, and what replaces them.
- [Agent evals vs testing what the agent shipped](https://qa.tech/blog/agent-evals-vs-testing): Evals grade a coding agent's output. They say nothing about whether the product it changed still works. The difference, with the reward-hacking evidence.
- [What is an AI software factory, and where does verification sit in it?](https://qa.tech/blog/ai-software-factory-verification): An AI software factory is a delivery system where agents build, test and ship code and humans design it. Gartner, BCG, Stripe and OpenAI describe one; none spe…
- [Playwright vs Selenium in 2026: a neutral comparison](https://qa.tech/blog/playwright-vs-selenium): Playwright vs Selenium on architecture, browser coverage, languages, waiting, parallel runs and debugging, with versions checked 12 October 2026, and which one…
- [Spec-driven development needs spec-driven verification](https://qa.tech/blog/spec-driven-development-verification): Spec-driven development makes the spec the source of truth for the bu