Testing Project Info
- Testers: 35-40 per release
- Geographic Coverage: North America
- Testing Type: Functional, Exploratory
- App Type: Web
- Browser/OS: All major versions
- Location:Waltham, Mass.
- Industry: Online Video Production
- Company Size: 8 Employees
- Methodology: Kanban combined with Agile/SCRUM
There was a time when customized video was reserved for the big players, with big marketing budgets. Today, that’s no longer the case. In fact, video is now considered an essential component to any company’s marketing strategy, regardless of size. With that trend in mind, Craig Daniel co-founded VisibleGains.
Based in Waltham, Massachusetts, VisibleGains helps companies of all sizes – from all over the globe – produce and track custom videos with a unique online platform. But before this technology could be deployed, it would first have to be tested across all major browsers and operating systems. Since Craig had been the lone tester up until that time, he knew that a more scalable solution was in order.
“Software testing is always one of the biggest pains, especially for a company our size,” said Daniel, Co-founder and VP of Product. “There’s always one more regression test, one more task that is needed – and that’s why uTest was such a great move for us.”
This case study will highlight how VisibleGains leveraged the uTest community to test their product before going into a public beta. Along the way, we’ll cover the challenges of testing scope, the test cycle execution and their overall results.
Set-Up, Scope, Deadlines and Deliverables
After more than four months of development, Daniel and his team were nearly ready to release their product into public beta. But fearing that they could have missed rare browser combinations and other odd edge cases, Daniel decided to run a simple functional test with the uTest community. To do that, he would call on his uTest project manager to get the release started off in the right direction.
“uTest really helped us get on board quickly,” said Daniel. “They advised us on the test case we created, which took the testers through our entire platform – things like creating videos, deploying videos and measuring analytics. I thought this would be difficult considering that it involved a lot of moving parts, but uTest handled it perfectly.”
Less than 24 hours after opening the test cycle, Daniel was able to review bugs and feedback from more than 35 individual testers, who had submitted close to 120 unique bugs – a few which were considered to be “showstoppers” (bugs in need of immediate attention).