As a very small business, we have very limited resources for dedicated E2E test engineers and infrastructure. We backed ourselves into a corner of putting off the need for a long time, and never being able to prioritize setting up our own infrastructure. Working with QAWolf took that load off our plate: They were able to work with non-technical members of our team to glean enough information to define core pathway tests across our apps, and established strong baseline coverage.
They've been attentive learning the specifics of our app and subject domain. They write good tests, and their presence in our Slack and integration with JIRA means their day-to-day test runs are first-class parts of our team's workflow.
They are also really attentive: Their amazing customer success folk are in regular contact, actually push us to make sure we meet regularly and are getting the good value from their service. They let us know when we've got unused test budget in our account, and seek out ways to have their team define new tests on their own. They've been receptive to technical requests and integration ideas we want to pursue. Review collected by and hosted on G2.com.
It's important to think of a service like QAWolf as a multiplier, rather than a magic-bullet. You do need to be able to support them with infrastructure access, insight into your product updates, and work with them to debug test failures — they can't do it all! You're getting an amazing team in support of your work, you do need to support them just as you would anyone who works for you. That's perhaps less of a “dislike” about them so much as realistic framing for what you can expect based on what your team can support. Review collected by and hosted on G2.com.
