Gazelle
Testing Project Info
- Testers: 15-20 testers per release
- Testing Type: Functional, Exploratory
- App Type: Web
- Browsers: Multiple
- OS: Windows
Customer Spotlight
- Location: Brighton, MA.
- Industry: Consumer Electronics
- Company Size: 40 employees; part-time QA manager
- Methodology: Agile

As the operator of a “re-commerce” site for people to sell and recycle their old consumer electronics, Gazelle (formerly known as Second Rotation) is keeping its promise to change the world “one cell phone, one laptop, one iPod at a time." As the business and software expanded, CTO James McElhiney realized that his defacto QA team - through no fault of its own - was not keeping up with the fast pace of development, and began searching for a more agile testing solution.
It’s a common problem within agile shops, explained McElhiney, and the answer has never been easy to come by. James understood that with the increased flexibility of agile development, QA had to play an active role throughout the process, not just a day before launch. And so after debating whether to hire internally or sign an outsourcing contract, James finally made his decision: neither.
Having learned of uTest through an associate, James signed up in April of 2008 to see how agile the global community really was. Within a matter of hours, he had assembled a diverse team of QA professionals for functional and exploratory testing, and received a detailed bug report on their web app. It wasn’t long after their first release when James (and the newly hired QA manager) realized they’d found a quick, accurate solution to their agile testing problem.
Interested in learning more about how uTest can complement your existing QA efforts? Here are a few relevant links to get you started:
In their own words...
On testing in an agile environment:
“uTest works really well with the fast pace of Agile. We never lose a step, since we release when we leave for the weekend and results are waiting for us when we come back in on Monday.”>
On cost and quality:
“uTest has allowed us to increase testing coverage and find more bugs, while decreasing the amount of manpower, time and money spent on testing.”
On prior testing methods:
"We had no dedicated QA team in place. The Product Manager would test each release, and would grab whoever was available to help out. Needless to say, uTest is a much better option"
- James McElhiney, CTO, Gazelle










