EatStreet offers on-demand food selection and delivery from a centralized marketplace. The company's goal is to simplify mealtimes by providing users with access to local restaurants for fast and easy ordering, quick delivery, and virtually endless selection. Users can order a snack or full meal at the drop of a hat online or with the iOS and Android apps.
I spoke with Kyle Mundt, Engineering Manager at EatStreet about their development and bug-fixing processes.
Read the whole case study here.
Here are some highlights:
The QA Bottleneck
Kyle told us he and his team, a smaller team of motivated developers intent on moving quickly, couldn’t keep overextending themselves with QA efforts, especially without a formal QA process in place. QA became a large bottleneck on time and resources, across the company, as even marketing was often wrangled into doing manual QA following new releases.
“It’s always better to have actual numbers, as opposed to ‘it’s probably not very good.’”
Criteria for Choosing a QA Solution
When looking for a way to augment their QA resources, EatStreet focused on improving software quality by focusing on:
- Number of bugs in backlog, and how quickly they are sieved through
- Variety of devices and operating systems represented
- Routine testing schedule (tests are run over the weekend, ready for Monday AM)
Interested in learning more about how different companies work with test IO and use crowdtesting? Visit the Customers page for more case studies and stories.