QA automation companies, products & suppliers
End-to-end and UI QA automation that uses AI to author or heal journeys. Jobs: journey authoring; self-healing selectors; regression packs.
What is QA automation?
End-to-end and UI QA automation that uses AI to author or heal journeys. Jobs: journey authoring; self-healing selectors; regression packs.
What problems does it solve?
UI journeys break whenever the front end moves.
Typical business use cases
- Journey authoring
- Self-healing selectors
- Regression packs
Important capabilities
- Browser grid
- Healing
- Reporting
What buyers should evaluate
- Selector strategy
- Environment secrets
- Flake rate
Risks and governance considerations
Healed tests that no longer check the original risk.
Procurement checklist
- Human review of heals
- Secret handling
- Environment isolation
Relevant AI Trustmark assurance
AI Trustmark independent findings appear only when an assessment or certificate exists. Category membership does not imply verification.
Companies and providers
Claimed suppliers appear first so buyers can start with listings the company has taken ownership of. Payment does not buy this order.
ACCELQ is the most powerful software testing tool to achieve Codeless test automation and accelerate continuous testing. ACCELQ is used for QA automation work. ACCELQ publishes pro
Autify's AI-powered Quality Engineering Platform provides AI-powered product and quality assurance professionals to streamline your software testing process and boost the prod
Builds, runs, and maintains tests against your live application. Functionize is used for QA automation work. Functionize publishes product information at functionize.com. Functioni
Katalon True Platform unifies test management, automation, execution and production insights. Test web, mobile, API and desktop in one platform. Katalon publishes Katalon Studio as
The #1 agentic testing platform empowering software teams to accelerate releases, ensure software quality, and deliver exceptional user experiences. mabl publishes mabl Generative
Write end-to-end tests for web and mobile in plain English. Momentic runs them everywhere and keeps them up to date. Momentic is used for QA automation work. Momentic publishes pro
Automated software testing for end-to-end test cases using plain English. testRigor is used for QA automation work. testRigor publishes product information at testrigor.com. testRi
Tricentis publishes Tricentis qTest, Tricentis Tosca, and Testim as named AI products. Tricentis is used for Software testing and QA automation work. Tricentis publishes product in
AI-native QA testing software and test automation platform trusted by 100+ enterprises. Write tests in plain English and cut maintenance by 88%. Virtuoso is used for QA automation
Products
Claimed products appear first. Ranking packs and payment do not change this list.
- ACCELQ· ACCELQ
- Autify NoCode· Autify
- Functionize· Functionize
- Katalon Studio· Katalon
- mabl Generative AI Test Automation· mabl
- Momentic· Momentic
- Testim· Tricentis
- testRigor· testRigor
- Tricentis Tosca· Tricentis
- Virtuoso· Virtuoso
Related categories
Relevant procurement and assurance guides
Frequently asked questions
What is QA automation?
End-to-end and UI QA automation that uses AI to author or heal journeys. Jobs: journey authoring; self-healing selectors; regression packs.
What should not be listed as QA automation?
Products whose buyer job is unit-test generation, AppSec testing, or production SRE tools. Those belong on their own category page so search queries are not split.
Has AI Trustmark independently assessed every QA automation supplier?
No. A category listing is descriptive. Independent assessment is shown only on company or product pages that carry Trustmark evidence.
Should coding assistants be allowed to send private source code to third-party models?
That is a buyer policy decision. Procurement should require the default data-use terms, retention, whether snippets leave the organisation, and whether secrets are redacted. A listing under coding assistants does not mean code stays on-premises.
How should prompt injection and tool-output attacks be controlled?
Agents that read untrusted content or tool output can be instructed to exfiltrate data or take writes. Buyers should ask what is treated as untrusted, whether tool output can change the plan, and what tests were run. Scanner marketing is not the same as independent testing.
How can buyers tell whether customer data is used to train models?
Ask whether prompts, files, logs or outputs are used to train, fine-tune or evaluate models, including by subprocessors. Require the contractual default, any opt-out, and whether the setting can be changed silently. Treat marketing 'we do not train' claims as unverified until evidenced.
What model or provider changes should a buyer insist on being told about?
Material change usually includes a new model family, new region, new subprocessor, new write-capable tool, or a change that affects logging, privacy or human oversight. Those changes should trigger evidence refresh rather than a silent release.
How should buyers verify where AI customer data is processed?
Ask for the named processing locations, cloud regions and any subprocessors that see prompts, files or outputs. A directory listing is not evidence of residency. Independent assessment records the locations that were in scope on the assessment date.