testRigor review

testRigor is a test automation platform, not a language-specific testing library or a conventional test runner that you install into an application repository. Teams create tests in its platform using plain-English instructions; testRigor translates them into actions and executes them across supported environments. The vendor also says tests can be generated from imported or pasted manual cases, or created through Claude Code using MCP and Skills.

It sits alongside an application and its existing delivery stack: the test describes user behavior, while testRigor runs the workflow and checks results. Its stated coverage includes web, native and hybrid mobile, native Windows, mainframe, APIs, email, SMS, phone calls and 2FA. The vendor lists on-premise deployment options for ENTERPRISE, but does not publish enough detail to treat every deployment as self-hosted. That distinction matters: the platform's broad workflow coverage does not make it a drop-in replacement for a code-first test framework or an in-repository test suite.

The main authoring surface is testRigor's platform, where tests use plain-English commands such as entering text, pressing a key and clicking an element. The vendor says you can create tests directly, paste or import manual cases, and generate tests with Claude Code through MCP and Skills. It also describes using Claude Code's /goal feature to generate and fix application code until tests pass.

The product can invoke APIs, retrieve values, validate return codes and save results. That is test-side API coverage, not documentation of a public testRigor REST API. The homepage names no SDK languages or CLI. It does list direct Twilio integration for SMS and calls, and integrations with LambdaTest or BrowserStack for more mobile test devices. Documentation, tutorials and an integrations resource are linked from the site. Before adopting it in a codebase, confirm SDK support, test definition versioning, CI integration details and the supported commands in the vendor's docs. The available integration surfaces named here are MCP and Skills, test commands, API invocation within tests, and the listed service integrations.

FREE - PUBLIC (Public Open Source) costs $0 per month. It includes one user and one parallel run, supports Ubuntu-based browsers only, and makes tests and results public. The vendor's listing says the free plan is free forever. That is useful for public projects or evaluation, but the public-results condition rules it out for confidential test data.

Pay As You Go (Private Complete) is billed by parallel server. It lists unlimited users and test executions, Ubuntu, Windows, Mac, Android, iOS and Windows Native, plus all AI capabilities. The price per parallel server is not published, so teams cannot calculate a private production bill from the listed terms alone. ENTERPRISE has custom pricing and lists SSO, dedicated customer success and Slack support, custom SLAs, and on-premise deployment options. No add-ons are listed. The pricing information also lists a 14-day free trial; confirm which plan it applies to and what happens when it ends. Ask sales for the parallel-server rate and any capacity or deployment charges before estimating total cost.

The FREE - PUBLIC plan's label includes “Public Open Source,” but its listed terms say tests and results are public. That does not establish that the testRigor platform itself is open source. The software licence and source availability are not published on the vendor's site terms, so teams should ask the vendor for the licence and whether test definitions can be used outside the platform.

The vendor lists on-premise deployment options for ENTERPRISE; that is not the same as a generally available self-hosted edition, and the deployment details are not published. Data export formats and procedures are also not published. Plain-English test steps may be easier to read than code written for a proprietary runner, but commands, execution behavior and maintenance features can still tie tests to the platform. Before committing, confirm export rights, how test assets and results can be retrieved, and what continues to work if the subscription ends.

The free plan's one parallel run is a clear scaling limit; the private plan instead bills by parallel server and lists unlimited test executions. The vendor does not publish a paid concurrency ceiling, rate limits, uptime commitment for non-enterprise plans, or detailed security controls in the published plan terms. ENTERPRISE lists SSO, custom SLAs and on-premise deployment options. The homepage also links to 21 CFR Part 11 compliance information, but teams should verify the applicable controls and evidence with the vendor before relying on it.

Reddit reports are mixed and anecdotal. Some users describe the tool as easy and flexible; others report difficulty with dynamic text, locators, test maintenance and the interface. One commenter reports that the platform UI became slow during the middle of the day, while another describes a poor support experience. These accounts are not service-level measurements, but they are reasons to test representative workflows, failure diagnosis, review practices and support response times before moving a critical regression suite.