A good bug report requires context, and this is precisely what users are least likely to be able to provide.
We recently had the chance to speak with two of our veteran customers, Blacklane and Touchcast.
Our very own CEO, Phil Soffer, spoke with Matthias Pomm (QA Team Lead at Blacklane) and Dmitry Panin (CTO of Touchcast). They covered a myriad of topics, from the evolution of QA over time, setting internal quality standards, finding impactful bugs, and shaping the software release process.
They also touched upon what it's like testing alongside test IO as well as shared some advice for new or prospective customers.
You can watch key excerpts from the conversation at the links above, or by checking out the test IO YouTube channel here.
Alternatively, you can listen to the conversation in its entirety here.
For existing customers, this discussion will give you ideas on how to adjust your current testing practices. If you're looking to give test IO and crowdtesting and try, you'll learn about how we can work with you to most effectively support your testing processes.
Enjoy!
A good bug report requires context, and this is precisely what users are least likely to be able to provide.
Here’s why every development team needs to integrate test IO’s bug fix confirmation into their workflows.
