What I like best about testRigor is how easy it is to create and maintain automated tests using plain English. It allows us to build complex end-to-end scenarios without writing a lot of code, which makes test development much faster. Reusable rules are also very helpful for reducing duplication and keeping our test cases easier to maintain. Additionally, testRigor enables us to cover a wide range of real user workflows and run our regression tests regularly with relatively little maintenance effort. testRigor provides good value for the cost. It helps us reduce repetitive manual regression testing, increase our automation coverage, and save significant time. While there is still room for improvement in execution stability and debugging, the overall value it provides to our QA process is strong. Review collected by and hosted on G2.com.

One of the main challenges with testRigor is test stability. We occasionally experience false positives or flaky failures, especially when the application or test environment is slow. Sometimes elements are visible but not immediately clickable, or actions fail because of timing issues, which requires additional waits or workarounds. Debugging failed tests can also be difficult in some cases, as the error message does not always clearly indicate the root cause. Improving execution stability and providing more detailed debugging information would make the overall experience much better. Review collected by and hosted on G2.com.