Testing Project Info
- Testers: 10- 30 per release
- Geographic Coverage: US only
- Testing Type: Functional
- App Type: Web
- Duration: Continuous
- Location:Tel Aviv, Israel
- Industry: Financial Services
- Company Size: Startup
- Methodology: All software developed in-house (Java + Python)
Did you know that the average consumer loses over $300 a year from unwanted charges? Wouldn’t it be great if there were a service that alerted you to hidden fees, billing errors, scams and other similar charges? Thanks to the founders of BillGuard – a free service powered by the collective knowledge of millions of people – consumers now have such an option.
Launched in 2011 at TechCrunch Disrupt, co-founders Yaron Samid and Raphael Ouzan attributed much of their early success to the Lean Startup methodology – a process designed to get companies up and running with minimal costs and delays.
As part of this strategy, Raphael (who is also the company’s CTO) knew this would have to include their software testing activities. With that in mind, he began searching for a cost-effective testing solution that could keep up with their rapid pace of innovation.
“Not many companies ship as fast or as often as we do,” explained Raphael. “uTest proved to be very valuable to our business, since it didn’t take long to get started, and once we were up and running, we could test our code on extremely short notice.”
This case study will show how uTest enabled BillGuard to run continuous functional testing of its unique web application as part of its Lean Startup launch schedule.
BillGuard: Testing Goals and Philosophy
With several iterations each week, Raphael and his development team needed a more flexible method of testing their product within a highly agile framework. A bigger challenge, however, was that testing had to be completed with real credit and debit cards. An impossible task for some, but not for uTest and its global community of testers.
“Every bank connection is different, so it was critical that we could test with live data,” said Raphael. “This why our use of uTest was so amazing and unique, because the testers had to use their own credit cards to test the system.”
Two weeks after their first code had been deployed in mid-2011, Raphael and his team were ready to begin their functional test cycle. Starting off with two test cycles a month, their team was able to achieve comprehensive regression testing against new features – a process that created what Raphael called an “early feedback loop.”
“Getting feedback at such an early stage was an enormous benefit for us,” said Raphael. “Establishing a feedback loop like this the number one reason why I recommend uTest to others. As a startup, you don’t want to spend time on things that you can’t measure. You want to make sure the core features of your application are working before moving on to the next sprint, and uTest gives you that assurance.”