G2

Gulin C.

Staff QA Engineer

Computer & Network Security

Small-Business (50 or fewer emp.)

9/2/2026

"Helps Us Keep Up With Fast Release Cycles"

4/5

What do you like best about testRigor?

One of the things I really appreciate about testRigor is how much faster it makes our testing process. I often use the plain English approach to create tests quickly, but I also like having the flexibility to use different selectors when needed. Being able to choose the best approach depending on the test is really useful. For a company like ours, where we release every two weeks, speed is especially important. testRigor helps us create, run, and maintain tests faster, which makes it much easier to keep up with our release cycle without spending too much time on repetitive testing work. Review collected by and hosted on G2.com.

What do you dislike about testRigor?

Sometimes updates can change existing behavior and affect tests that were working before. We’ve also experienced occasional access issues, which can be frustrating, especially when we’re close to a release. I also think the CI/CD integration could be more flexible. It works well for triggering and managing test runs, but having more granular options to retrieve specific data and manage or create test cases programmatically would make it much easier to integrate testRigor into our existing workflows. The plain English approach also doesn’t cover every scenario, so sometimes I need to use selectors to target elements more precisely. It’s not a major issue, but these are a few areas where I think the product could still improve. Review collected by and hosted on G2.com.

What problems is testRigor solving and how is that benefiting you?

testRigor helps us reduce the time and effort we spend creating, running, and maintaining automated tests. Since we release every two weeks, having a faster testing process is really important for us. It allows us to build tests quickly using plain English when it makes sense, while still giving us the flexibility to use selectors for more specific scenarios. This helps us cover different use cases without spending too much time on repetitive test maintenance. Overall, it helps us keep up with our release cycle, catch issues earlier, and spend more time focusing on product quality instead of maintaining test scripts. Review collected by and hosted on G2.com.