
The entire team is very quick to respond and attentive to our needs. Their tests are great for finding critical issues before we merge PRs and have helped us identify critical issues that would have otherwise negatively impacted our customers.
Unfortunately, integration with Linear has not been easy due to our internal security requirements, so we don't get as many benefits out of the bug reporting as we could. If there were a way to have bi-directional communication between the QA Wolf tickets and bugs created in Linear without granting QA Wolf access to our Linear space, that would be a useful feature.
The UI is easy to use and the bug report recordings are very useful for diagnostics. The tests seem to run reasonably fast. The main bottleneck is our own sandbox infrastructure, not so much the tests. Review collected by and hosted on G2.com.
It can be challenging for dev teams to know that their changes will break QA Wolf tests since they're not part of the standard suite of tests. This separation can become a bit of a maintenance burden for the dev teams.
We also explored using QA Wolf for E2E testing on our mobile apps, but the cost was prohibitive. The amount of time our devs spent on dealing with the tests themselves was ultimately cheaper than handing it off to QA Wolf. We would have liked to offload that effort to a third party like QA Wolf, but the ROI wasn't there for a single mobile dev team. For QA Wolf to be cost effective, they need to be writing tests for multiple teams of devs. Review collected by and hosted on G2.com.