FAQs Archive - Page 28 of 32

Q: Why should I outsource testing when I have a QA team in house?

Outsourcing your testing can bring economies of scale, efficiency and speed. It gives you access to a large variety of testing techniques and resources. If you have a small internal team you may not be able to do the breadth or depth of testing you really need before releasing a digital product. Outsourcing your test may save you money because you can apply the right type of testing at exactly the time you need it, without holding up development. You may be able to perform the testing earlier in the software development lifecycle too. Recruiting experienced testers can be hard. Outsourcing your testing takes that headache away.

Q: What is ‘push and pray’ and what are the risks of the approach?

Push and pray means a software development team rushes to release a digital product without doing enough testing. They make the product live and hope for the best. The risks are significant. If you don’t look for issues or errors before customers find them, you’ll create a lot of dissatisfaction and potentially lose customers and revenue.

Q: What does augmented teams mean in relation to QA?

Team augmentation in QA means supplementing your team with Digivante people led by a Digivante senior tester. You’ll increase capacity and quickly get the advantage of an experienced group of testers. The augmented team members embed themselves into your software development lifecycle and the wider businesses. They bring expertise in QA strategy and execution and can call on all Digivante resources to support your project.

Q: Will website testing disrupt my release schedule?

Not with Digivante. We work with you to understand your deadlines and constraints and plan our services to meet your targets. Crowdsourced testing can be delivered overnight and at weekends. With our large testing community and efficient techniques, we can carry out extensive testing in a shorter time. It’s not unusual for us to carry out 90 workdays of testing in 3 days, or 5 days of regression testing using traditional testing methods to just 5 hours.

Q: How do testers access my website environment?

That depends if you’re testing in live or pre-production test or staging environments. For live testing, testers receive the URL and can get to work straight away. For testing behind a firewall or in pre-production, we recommend using a Virtual Private Network (VPN). This allows multiple testers to access your securely; we can track them under a single IP address.

Q: How will external testers know how to test my website?

We always provide a clear brief before testing starts, so testers don’t need their own domain knowledge. We specify key focus areas and out of scope areas. We give testers guidance on the type of test. In exploratory testing, website testers have personal freedom to test any areas in scope. Or we can specify a more prescriptive approach, so testers execute specific steps within a test case. A Digivante delivery team member takes responsibility for the test scope and team and manages the quality and outputs.