Testery

Overview

Testery is a cloud test orchestration service for teams that already have automated tests and want to connect them to CI/CD. It is best suited to engineering groups that need parallel execution, flaky-test controls, and deployment checks in one workflow. Growth starts free, but its 10-hour monthly allowance and cloud-networking requirements deserve a close look before adoption.

Testery works with a broad set of frameworks, including Playwright, Cypress, Selenium, Robot Framework, Jest, Cucumber/BDD, Postman, JUnit/TestNG, WebdriverIO, Nightwatch.js, SpecFlow, PyTest, and NUnit. It distributes tests across parallel cloud runs and describes scaling to thousands of tests in parallel, which can help teams shorten large suites without replacing their existing frameworks.

Key features

Execution and failure management

Flaky-test detection, quarantine, failure clustering, and rerun policies target a familiar source of CI friction: failures that consume time without reliably identifying a product defect. These controls are useful for teams trying to keep unstable tests from blocking every change, though they do not remove the need to diagnose and repair the underlying tests.

Run evidence can include logs, screenshots, and video, with shareable artifacts for each run. That gives developers concrete context when investigating failures rather than just a pass-or-fail result.

Delivery workflow and integrations

Pull request status checks can gate merges or deployments until tests pass. That makes Testery relevant to teams that want test outcomes to influence release decisions, while integrations with GitHub, Bitbucket, Slack, Microsoft Teams, OpsGenie, and webhooks can route events into existing workflows, including downstream tools such as Zapier.

Local runs, AI, and network access

Local execution runs on the user's hardware, and the user chooses which results sync to the cloud. Testery also offers a Claude Code plugin and an MCP server for compatible assistants to trigger runs, read results, and rerun failures. For cloud tests that need to reach systems behind a firewall, teams must whitelist Testery static IPs or use a tunneling tool such as ngrok; certificate-based authentication is not currently supported. That limitation may rule it out for environments that require certificate-based access.

Pricing

Growth is free, billed $0 for 10 hr/mo then $1.20/hr. It includes 10 test execution hours, 10 parallel test runners, reporting and analytics, test artifacts, CI/CD integration, CLI, test API, and Claude integration. This is the sensible starting point for a small workload, but the hourly charge after the monthly allowance means costs can rise as execution grows.

Team is $500 a month, billed $500/mo, for 500 test execution hours and 30 parallel runners. It adds unlimited users while retaining reporting and analytics, artifacts, CI/CD integration, CLI, and test API. It fits teams with recurring workloads that have outgrown Growth, though the plan still caps execution hours.

Scaling is $950 a month, billed $950/mo, for 1,000 test execution hours and 30 parallel runners, with unlimited users and the same core reporting, artifact, and CI/CD features. It is aimed at higher-volume teams; compared with Team, its added allowance is execution time rather than more parallel runners. Enterprise has custom pricing and offers any number of parallel tests, custom test runners, and advanced workflow capabilities, making it the tier to consider for unusual or larger-scale requirements.

Platforms

Testery supports API, Linux, macOS, self-hosted, web, and Windows environments. Its mix of cloud orchestration and local execution gives teams options, but access to firewalled cloud test targets may require network configuration.

Who it's for

Testery is a strong fit for teams with existing automated suites that need parallel cloud runs, traceable artifacts, and test-based merge or deployment gates. Growth offers a low-cost way to begin, while Team and Scaling give established workloads larger hour allowances and unlimited users. Teams that need certificate-based authentication for cloud access, or that cannot accommodate the firewall workarounds, should look elsewhere.

Pros and cons

• Pros: Broad framework support lets teams orchestrate existing suites rather than start over.
• Pros: Parallel runners, failure clustering, quarantine, and retries address both execution time and noisy failures.
• Pros: Logs, screenshots, video, and shareable run evidence help teams investigate failures and coordinate fixes.
• Pros: Status checks and deployment gates connect test outcomes directly to release decisions.
• Cons: Growth's 10 execution hours are followed by a $1.20/hr charge, so usage requires monitoring.
• Cons: Team and Scaling both provide 30 parallel runners; Scaling raises execution hours but not concurrency.
• Cons: Cloud access behind a firewall requires whitelisting static IPs or tunneling, and certificate-based authentication is unsupported.

Alternatives

For a broader comparison of this category, see Test Flakiness Management Software.

• Captain is a freemium option with a free OSS plan for file-based configuration, parallel suite partitioning, flaky-test tracking and quarantine, and retries; choose it when those core controls are enough.
• Flakiness.io is a freemium, web and self-hosted alternative with a Startup plan at $49 a month; consider it if those deployment options suit your setup.
• Trunk Flaky Tests offers a free plan capped at 5 repo committers and 5M test spans per month, plus a free trial; it may suit teams comparing a bounded free allowance.
• FlakyWatch has a free plan for one repository with classification and cost tracking, GitHub issue creation, 14-day history, and a weekly digest; choose it for that focused workflow.
• Qualflare has a free Starter tier capped at one project, one active user, 200 test cases, and 100 test reports; consider it when those limits fit.
• FlakyTest.dev offers a free OSS plan for personal projects, nonprofits, and open-source projects; it is an option for those uses.
• Flake is a free alternative for Linux, macOS, self-hosted, and Windows environments.
• HyperExecute offers a free plan with 300 testing minutes, up to two concurrent sessions, and Windows or Linux VMs; consider it for that smaller allowance.

Verdict

Choose Testery if your team wants to orchestrate existing tests, control flaky failures, and make CI results part of merge or deployment decisions. Its strongest case is the combination of parallel execution, useful run evidence, and delivery gates; its main cautions are Growth's usage-based overage and the networking work required for firewalled environments.