QA testing tools in 2026: 35 free and paid tools by category
35 QA testing tools compared by category: test management, automation, mobile, device clouds, API, load, visual, accessibility, security and bug capture.
QA testing tools fall into a handful of categories: test management (planning test cases and tracking runs), test automation (scripts that drive the browser or app), mobile app testing, cross-browser and device clouds (real browsers and phones to test on), API testing, performance and load testing, visual, accessibility and security testing, bug capture (recording evidence when something breaks), and issue tracking (where the fixes are managed). Well-known examples include TestRail, Xray and Qase for test management; Playwright, Cypress and Selenium for web automation; Appium for mobile; BrowserStack and Sauce Labs for device clouds; Postman for APIs; k6 and Apache JMeter for load testing; and Jira, Linear or GitHub Issues for tracking.
Few teams need every category on day one. A typical web team starts with an issue tracker, a way to capture bugs well, and a few automated end-to-end tests for the flows that make money, then adds test management, device coverage and load testing as the product and team grow. Many of the best QA testing tools are free or open source; the table below shows which. The descriptions are based on each tool’s own website as of November 17, 2026. Check the vendor’s pricing page before you buy, because plans change often.
QA testing tools at a glance
| Tool | Category | Free option | Best for |
|---|---|---|---|
| TestRail | Test management | 30-day trial | Established standalone test case management |
| Xray | Test management (Jira app) | Trial; $10/month up to 10 Jira users | Jira teams that need traceability to requirements |
| Zephyr | Test management (Jira app) | Trial; $10/month up to 10 Jira users | Jira teams in the SmartBear ecosystem |
| Qase | Test management | Free plan (up to 4 users) | Small teams that want a modern tool |
| Testiny | Test management | Free plan (up to 3 users) | Small teams that want Jira on a free plan |
| TestLink | Test management | Open source | Self-hosting at no license cost |
| Playwright | Web test automation | Open source | Cross-browser end-to-end tests in code |
| Cypress | Web test automation | Open source runner | Front-end teams that want fast feedback in the browser |
| Selenium | Web test automation | Open source | Many languages, the WebDriver standard |
| WebdriverIO | Web and mobile automation | Open source | JavaScript teams testing web and native apps |
| Katalon | Low-code automation | Free plan | Testers who want record-and-playback plus scripting |
| mabl | AI and low-code automation | Free trial | Teams without many automation engineers |
| Appium | Mobile test automation | Open source | Cross-platform iOS and Android UI tests |
| Espresso | Android UI testing | Free (Android SDK) | Fast in-process Android tests |
| XCUITest | iOS UI testing | Free (Xcode) | Native iPhone and iPad UI tests |
| Maestro | Mobile UI testing | Open source | Simple YAML flows for iOS and Android |
| BrowserStack | Device cloud | Free trial | Real browsers and phones for manual and automated tests |
| Sauce Labs | Device cloud | Free trial | Automated tests on devices, browsers and emulators |
| TestMu AI (formerly LambdaTest) | Device cloud and AI testing | Free plan | Cross-browser testing with AI agents |
| Postman | API testing | Free plan | Building and testing API requests in collections |
| Bruno | API testing | Open source | API collections stored as files in Git |
| Grafana k6 | Load testing | Open source | Load tests written in JavaScript |
| Apache JMeter | Load testing | Open source | Mature, GUI-based load and performance tests |
| Gatling | Load testing | Open source | Load tests as code in CI |
| Locust | Load testing | Open source | Load tests written in Python |
| Percy | Visual testing | Free plan | Screenshot comparisons in pull requests |
| Applitools Eyes | Visual testing | Free trial | AI-based visual checks across browsers |
| axe | Accessibility testing | Open source engine | Automated accessibility checks in tests |
| Lighthouse | Performance and accessibility audits | Free, built into Chrome | Quick page audits |
| ZAP | Security testing | Open source | Scanning web apps for common vulnerabilities |
| Midge | Bug capture | Free | Recordings with console and network logs |
| Jam | Bug capture | Free plan | Bug reports from a browser extension |
| Jira | Issue tracking | Free plan (up to 10 users) | Teams that need workflows and reporting |
| Linear | Issue tracking | Free plan | Fast-moving product teams |
| GitHub Issues | Issue tracking | Free | Teams whose code lives on GitHub |
Test management
Test management tools hold your test cases, group them into test runs for each release, and record what passed and failed. They answer questions like “did we test the refund flow before this release?” and “which tests failed on the last build?”.
- TestRail describes itself as test management software for planning, executing and reporting on testing, connecting manual and automated results, requirements and defects in one place.
- Zephyr, from SmartBear, is a family of test management products that run inside Jira.
- Xray is test management inside Jira, with tests as Jira issues linked to requirements so coverage can be traced.
- Qase brings CI results, automated tests and manual runs into one view, with a free plan for small teams.
- Testiny is a newer standalone tool with a free plan for up to 3 users and a Jira integration on every plan.
- TestLink is an open source, self-hosted test management tool.
When you need one: when your regression checklist no longer fits in a document, when several testers share the work, or when you need a record of what was tested for each release. If your team lives in Jira, a Jira-native option keeps tests next to the stories they cover. Our guide to QA test management software compares these tools, their pricing and their Jira integration in more detail.
Test automation frameworks
Automation frameworks run scripted checks, usually in a real browser, so the same flows are verified on every change without someone clicking through them.
- Playwright is an open source end-to-end testing framework for web apps, developed in the open by Microsoft on GitHub. It drives Chromium, Firefox and WebKit.
- Cypress runs end-to-end tests in a real browser. The test runner is open source, and Cypress Cloud adds hosted features for running and analyzing tests at scale.
- Selenium is a long-established open source project for browser automation built around the W3C WebDriver standard, with bindings for many programming languages.
- WebdriverIO is an open source test framework for Node.js that automates web apps and, through Appium, native mobile apps.
What to automate first: sign-in, sign-up, checkout or payment, and any flow where a regression costs money or trust. Keep the tests few and reliable at first. A small suite that always passes when the product works is worth more than a large one people learn to ignore.
Low-code and AI test automation
Low-code tools let testers build automated tests by recording steps or describing them, instead of writing code. Many now use AI to write tests and repair them when the page changes.
- Katalon is a test automation platform for web, mobile, API and desktop apps, with record-and-playback and scripting, and a free plan.
- mabl is a low-code, AI-driven test automation platform for web, mobile and API tests that runs in the cloud.
- TestMu AI, the new name of LambdaTest since January 2026, positions itself as an agentic AI platform that plans, writes and runs tests, alongside its browser and device cloud.
These tools help teams with few automation engineers get coverage quickly. The trade-off is that tests live in the vendor’s platform rather than in your code repository, so check how you would export them before you commit.
Mobile app testing
Native iPhone and Android apps need their own tools, because browser automation does not reach them.
- Appium is an open source framework for automating native, hybrid and mobile web apps on iOS and Android, built on the WebDriver protocol.
- Espresso is Google’s UI testing framework for Android, part of the Android SDK. Tests run inside the app process, which makes them fast and stable.
- XCUITest is Apple’s UI testing framework, built into Xcode, for iPhone, iPad and Mac apps.
- Maestro is an open source mobile UI testing framework where flows are written as simple YAML files, for iOS, Android and web.
For manual mobile testing, the bug report matters as much as the test: a screen recording with the device model and OS version saves a lot of back and forth. See how to screen record a bug on iPhone and on Android.
Cross-browser and real device clouds
Your users run many browsers, versions, operating systems and phones. Device clouds give you access to them without buying a lab.
- BrowserStack offers instant access to thousands of browsers and real iOS and Android devices, for manual and automated testing.
- Sauce Labs offers testing of web and mobile apps on real devices, browsers and emulators, with test automation.
- TestMu AI (formerly LambdaTest) offers cross-browser testing on browsers and real devices, now combined with its AI testing agents.
These are useful for manual checks of layout bugs on specific devices, and for running your automated suite across several browsers in CI.
API testing
Many bugs are in the API, not the interface. API testing tools let you send requests, check responses and save them as repeatable collections.
- Postman is a widely used API platform for building, sending and testing API requests, organizing them into collections and running them in CI.
- Bruno is an open source API client that stores collections as plain files, so they can be versioned in Git next to the code.
API tests are fast and stable compared to browser tests, so they are a good place to check business rules, permissions and error handling.
Performance and load testing
Load testing tools simulate many users at once to find out how your system behaves under traffic.
- Grafana k6 is an open source load testing tool, with a cloud service, aimed at developers and QA engineers. Tests are written in JavaScript.
- Apache JMeter is an open source, Java-based application designed to load test functional behavior and measure performance.
- Gatling is an open source load testing tool where tests are written as code and run in CI, with an enterprise edition.
- Locust is an open source load testing tool where user behavior is written in plain Python.
Run load tests before launches and large campaigns, and whenever you change something that affects every request, such as authentication or database access.
Visual, accessibility and security testing
Functional tests check that a button works, not that it looks right, that everyone can use it, or that it is safe. Three smaller categories cover those gaps.
- Percy, from BrowserStack, takes screenshots during your tests and highlights visual changes for review in each pull request.
- Applitools Eyes compares screens with AI-based visual checks across browsers and devices.
- axe, from Deque, is an open source accessibility testing engine that runs inside unit and end-to-end tests, with browser extensions for manual checks.
- Lighthouse is built into Chrome DevTools and audits a page for performance, accessibility, SEO and best practices.
- ZAP (formerly OWASP ZAP) is an open source scanner that finds common security problems in web apps, often run in CI.
Bug capture and reporting
When manual or exploratory testing finds a problem, someone has to turn it into a report a developer can act on. That is where bug capture tools come in. They record a screenshot or video and attach technical context such as console logs, network requests and device details, then share the result as a link or send it to the tracker.
- Browser extensions such as Jam, BrowserStack Bug Capture and Midge suit testers and developers who report bugs all day.
- Website feedback widgets such as Marker.io and BugHerd suit client reviews and user acceptance testing with people outside the team.
Our overview of bug reporting tools compares them in more detail, and our bug report template helps whichever tool you use.
Issue tracking
Issue trackers are where bugs are prioritized, assigned and closed. Jira, Linear and GitHub Issues are common choices. QA teams often add a bug template as the default issue description, and link each bug to the test case or story it affects.
Browser developer tools
The most used QA tool is often already installed. The developer tools in Chrome, Firefox, Safari and Edge show console errors, network requests, storage and layout, and can simulate slow networks and mobile screen sizes. Every tester benefits from knowing a few basics:
- How to capture network traffic in Chrome
- How to export console logs in Chrome
- How to get a HAR file, and the free HAR viewer and HAR sanitizer for reading and cleaning them
Free QA testing tools
A complete QA toolset can cost nothing. Open source covers most categories:
- Test management: TestLink (self-hosted), or the free plans of Qase and Testiny for small teams.
- Web automation: Playwright, Cypress, Selenium and WebdriverIO.
- Mobile automation: Appium, Maestro, Espresso and XCUITest.
- API testing: Bruno, and the free plan of Postman.
- Load testing: k6, JMeter, Gatling and Locust.
- Accessibility, performance and security: axe, Lighthouse and ZAP.
- Bug capture: Midge, free with unlimited recordings.
- Issue tracking: GitHub Issues, and the free plans of Jira and Linear.
What you pay for with commercial tools is usually hosting, real devices, reporting and support, not the testing itself.
How the pieces fit together
A typical flow in a growing web team:
- Stories are written in the issue tracker, with acceptance criteria.
- Test cases for the story are added in the test management tool, or in the story itself on smaller teams.
- Developers and testers add automated tests for the critical paths, run in CI on every change, across browsers in a device cloud if needed.
- Testers do exploratory testing on the build. When they find a bug, a bug capture tool records it with console and network data.
- The bug lands in the tracker with a link to the recording, gets fixed, and the tester retests it.
- Before big releases, API, load, accessibility and security checks confirm the system holds up.
Choosing tools for a small team
If you are just starting:
- Start with what you will actually use. An issue tracker and a good bug report template go further than an unused test management license.
- Automate a few critical flows first. Pick one framework the developers are comfortable with.
- Make bug reports cheap to write. The faster a tester can file a complete report, the more bugs get reported instead of mentioned in passing.
- Add test management when the checklist hurts, not before.
- Prefer tools that keep your data portable. Tests in your repository and reports as plain links outlive any single vendor.
Where Midge fits
Midge is a bug capture tool: a free Chrome extension, Mac app and iPhone app for the moment a tester finds a problem. It records the screen or takes an annotated screenshot and attaches the technical context on one timeline. Every browser recording includes console logs, network requests, user actions and device info. Passwords, card numbers, tokens and cookies are redacted in your browser before anything leaves your device. It does not manage test cases or run automated tests. Reports go straight to Jira, Linear, GitHub Issues or Slack, or as a link you paste into your tracker. Read more on Midge for QA teams.
Frequently asked questions
What tools do QA testers use?
Most QA teams combine a test management tool (such as TestRail, Xray or Qase), a test automation framework (such as Playwright, Cypress or Selenium), an API testing tool (such as Postman), a bug capture tool for reports, and an issue tracker such as Jira, Linear or GitHub Issues. Mobile teams add Appium, Espresso or XCUITest, and a device cloud such as BrowserStack.
What is the best QA testing tool?
There is no single best tool, because each covers a different part of testing. For web automation, Playwright is a strong default for new projects. For test management, Xray or Zephyr suit teams on Jira, and Qase or TestRail suit teams that want a standalone tool. For bug reports, pick a capture tool that attaches console and network logs.
Are there free QA testing tools?
Yes. Playwright, Cypress, Selenium, Appium, k6, JMeter, axe, Lighthouse and ZAP are free and open source. Qase, Testiny, Postman, Jira and Linear have free plans for small teams, and Midge is free for bug capture.
What are AI QA testing tools?
AI QA testing tools such as mabl, Katalon and TestMu AI write tests from plain-language descriptions, repair tests when the page changes, and point out likely causes of failures. They reduce the code a team has to write, but the tests usually live in the vendor’s platform.
Do small teams need a test management tool?
Not always. Small teams often start with a checklist in a document or spreadsheet and add a dedicated tool when the number of test cases, testers or releases makes the checklist hard to manage.
Should we automate all our tests?
No. Automate stable, repetitive checks such as sign-in, checkout and critical API contracts. Keep exploratory and usability testing manual, because people find the unexpected problems that scripts are not written for.
Where does a bug reporting tool fit in QA?
It sits between finding a bug and fixing it. When a tester finds a problem, the bug reporter captures the evidence, such as a recording, console logs and network requests, so the developer can reproduce it.