QA Wolf vs. test IO

QA Wolf is great if you want to automate the building and managing of end-to-end regression style tests. They would not be great for new feature buildouts where the tests need to be done very quickly to ship a feature or if the feature is changing rapidly, as there is at least a couple day lag to when test cases get built out. QA Wolf does not do any manual testing so that is not a good use case for the platform.

I think it's definitely more of an e2e testing tool versus just testing individual components.

Incentivized

• Creates new tests as requested fairly quickly.
• Listening and available at all times.
• Automated testing and the ease of creating tests on their platform with 0 coding experience.

• catch bugs
• test e2e flows
• accurately report bugs with screenshots and videos

Incentivized

• QA Wolf could provide a better feedback loop for when tests are completed in order for us to have even higher confidence they are built and working as intended.
• QA Wolf could do a better job of ensuring that failing test cases are resolved in a timeline manner.

• honestly, nothing comes to mind - I think it's a great tool

Incentivized

The dashboard makes it easy for us to understand what outstanding issues our product has so we can prioritize and assign work quickly to get the fixes shipped.

We chose QA Wolf for the quality of the tests that they write, their flexibility, outstanding customer support, workflow integrations, excellent infrastructure, and competitive pricing. We were not happy with the quality of the tests we were getting with ProdPerfect. We were going to evaluate MuukTest once our proof of concept with QA Wolf was completed, but we were already convinced we had what we wanted, and going with a less capable infrastructure wasn't worth the cost savings.

test IO is MUCH easier to set up test cases and because it uses actual humans, it's a better real life tool. Rainforest was too picky on the test cases and you had to be overly specific.

Incentivized

• While I am not privy to the actual financial numbers associated with our change, I can articulate what we executed. We shifted away from a third-party, off shore partnership who was supplementing our internal QA staff with contractors writing Cypress tests and the management of Cypress Cloud, to eliminating four off-shore positions and terminating our Cypress Cloud subscription in order to keep our internal staff members and partner with QA Wolf. This change has been fiscally positive for our overall business objectives.
• This change also eliminated a time zone delay in communication and oversight between our international personnel maintaining our automation suite and created a more timely update between our staff and our new partners, building confidence that our investment in automation coverage is being managed appropriately.

• Catching bugs before customers do
• Catching bugs during a release

Incentivized