Testing Project Info
- Testers: 15- 30 per release
- Geographic Coverage: Global
- Testing Type: Exploratory
- App Type: Mobile, Web
- Duration: Weekly cycles
- Location: Hollywood, CA.
- Industry: Social Networking
- Company Size: 100+ employees
- Methodology: Agile (releases run every week)
With thousands of users around the globe, Blendr offers a social networking experience unlike any other. Since 2009, the company has been connecting members of its community based on shared interests via an assortment of applications for iPhone, Android and Facebook.
Among those thousands of users is an active, eager beta community. As the company’s testing challenges grew, VP of Technology Aaron Judd began searching for a way to combine what he liked best about the beta community (real-world feedback) with professional testing. Having worked with uTest at a previous company, Aaron was already sold on the concept of in-the-wild testing, making his choice all the more easy.
"We were trying to find a balance between what our beta community does well and what our in house QA team does," said Aaron. "uTest was a perfect fit, since they would give us real-world testing like our beta community, but they would report bugs into a dedicated platform, making it easier for us to sort through and analyze."
This brief case study will highlight how Blendr was able achieve in-the-wild testing of their nine different products. Along the way, we’ll cover the basics of defining a testing scope, analyzing bug reports, working with a project management team and other aspects of the uTest experience.
Blendr: Setup, Scope and Tester Selection
Of course, detailed bug reporting wasn’t the only reason Aaron decided to leverage uTest. Other factors included speed, ease-of-use, device coverage and perhaps most important of all, location.
“We asked (uTest) for more aggressive testing in our target areas, which happen to be London and Australia,” said Aaron, who noted that his criteria was easily met with the help of his dedicated uTest project manager.