testRigor review

testRigor turns plain-English instructions into executable automated tests. The product says it covers web, mobile, native desktop, APIs, email, SMS, phone calls, 2FA and mainframe applications. It also offers features for testing AI-based apps, including chatbots and generated content.

Tests can be created and edited in natural language. The product also lists test generation in testRigor or through Claude Code using MCP and Skills, plus integrations with Jira, Jenkins, GitHub Actions, Zephyr and TestRail.

The appeal is clear: teams can write tests without starting from a conventional coded automation framework. But plain English does not remove the need to check whether tests handle your application’s less-standard behavior. A Reddit discussion comparing testRigor with Playwright includes both a commenter who recommends no-code tools for nontechnical testers and commenters who favor coded tests for greater customization.

testRigor’s broad platform coverage is its clearest selling point. The product lists web, iOS, Android, native Windows and mainframe testing, alongside API, email, SMS, phone-call and 2FA scenarios. That range may suit teams trying to cover several application types without stitching together separate tools.

Other points worth considering:

• Tests use plain-English instructions, and the product also offers test generation in testRigor or through Claude Code using MCP and Skills.
• Its AI-app testing features target chatbots and generated summaries, pictures, charts and diagrams.
• It lists integrations with Jira, Jenkins, GitHub Actions, Zephyr and TestRail.
• The FREE - PUBLIC plan costs $0 per month for public open-source projects. It includes one user and one parallel run, with Ubuntu-based browsers.

The free plan gives teams a way to assess the product, but its public-test terms make it a poor fit for private application coverage. In one Reddit discussion, a user described the tool as easy and flexible, while another said they struggled with the UX. Those are individual reports, not a guarantee of how it will fit your team.

The free plan has firm limits: one user, one parallel run, Ubuntu-based browsers only, and tests and results are public under The Unlicense. That is for public open-source projects, not private company testing.

Private pricing is the bigger switching question. The published pricing information lists Pay As You Go for private cross-platform testing, with unlimited users and test executions, but does not publish a monthly or annual price. It says billing is based on parallel infrastructure, not per user. Enterprise pricing is custom. The listed free trial is 14 days, so get a quote that reflects your required parallel capacity before comparing costs.

There are also trade-offs with no-code testing. In a Reddit thread, commenters criticized locator flexibility, code review and handling unusual application behavior; one commenter also reported the interface slowing down. These are user reports, not verified product-wide findings, but they point to questions to check in a trial. A commenter in the Playwright discussion argued that coded tests offer more customization for complex business logic. If that matters to your team, compare a representative test before switching.

testRigor lists one $0 plan: FREE - PUBLIC. It is limited to one user and one parallel run, with Ubuntu-based browsers only. Tests and results are public and shared under The Unlicense, so it is not a private-team starter tier. The pricing details also list a 14-day free trial, but do not explain how it relates to the public plan.

The next option, Pay As You Go (Private Complete), has no published monthly or annual price. It includes unlimited users and test executions, plus cross-platform testing across Ubuntu, Windows, Mac, Android, iOS and Windows Native. The billing gotcha: charges are based on parallel infrastructure, not per user, and the price depends on that infrastructure. Enterprise pricing is also custom and unpublished; it adds options such as SSO, support and on-premise deployment.

That makes the jump from free to private hard to budget. The pricing details list no add-ons, but they do not publish a calculator or rates for parallel infrastructure. Get a quote before planning a switch.

Treat migration as a test-design project, not a simple import. testRigor accepts plain-English instructions and lists integrations with Jira, Jenkins, GitHub Actions, Zephyr and TestRail, but the published materials do not document test import, export or conversion paths. Ask the vendor how existing cases, results and reusable test data move before you commit. Also trial your hardest workflows: the platform covers several application types, but the published material does not establish how much control you have when a test needs custom code.

Lock-in is difficult to assess without published export details. The free plan has an extra constraint: tests and results are public and shared under The Unlicense, so avoid it for private work. Private pricing is unpublished, which can also make a move harder to justify.

We can’t responsibly name reasons people leave based on Reddit: no Reddit posts or comments were included in the published material. Ask for a data-export answer and a quote, then compare both with your current tool before switching.