Speak to an expert
Thanks for your interest in Digivante. Arrange a call with one of our QA & testing experts who will seek to understand your business goals – whether from a development or a marketing perspective.
Request a call with an expert
During the ‘discovery call’ we’ll talk you through similar customer success stories and suggest possible solutions to your specific requirements. The call lasts around 15 minutes.
What makes Digivante’s website testing services industry-leading?
- A fully managed & bespoke programme of professional testing and digital performance solutions
- A community of thousands of people, in over 149 countries, who are carefully managed and trained as professional testers
- 300+ real browser & device combinations tested
- Digivante’s customer portal: a single location to access your defects and issues, presented with images, video evidence and steps to recreate
- Integrations with JIRA or other test management tools
- 24/7 365-day testing
Frequently asked questions
- Become a tester
- Company information
- Crowdsourced testing
- Digivante portal
- Manual testing
- Software development lifecycle
- Team augmentation
- Test automation
If you augment your team with a Digivante QA expert, they’ll:
- conduct static (requirement) reviews
- conduct Sprint (scope) reviews
- write test cases
- write Gherkin
- manage functional testing
- manage system integration testing
- manage crowd-testing
- identify process improvements
At Digivante, we can get a project set up in a matter of hours for subscription customers. For one-off projects we can usually get started within 24-48 hours.
We use the secure Digivante platform for all our testing data and reporting. Our testers are vetted and verified. We’ve worked with leading household names, from Microsoft and Metro Bank to Audi and Specsavers. They trust us to keep their testing secure and confidential. Talk to us about your specific needs and we’ll work with you to build a testing plan that meets all your security requirements.
Forgive us if we say that’s a short-sighted attitude. Testing will become a very high priority for your business if you release software and digital products that frustrate customers and constrain their engagement and spending. Put QA into your software development lifecycle early so you’ll catch issues when they’re easy to resolve out of the customer and boardroom spotlight. You’ll avoid major reputational headaches for the business and safeguard your customers’ loyalty.
An overstretched development team can be prone to making more mistakes, which incur costs and lead to even more testing. In our approach to QA, we seek to improve your capacity for dealing with software issues. The test cases we write are clear and simple to follow, even for non-tech people, so it’s easier to prioritise issues and deal with them quickly.
Even if you don’t release new features often, the digital access points that people use to experience your website or app are constantly evolving. You need to be sure that everything works when a new browser update goes live or a new mobile OS is released. You need to know how your digital products respond on new devices when they launch.
Our web development partner handles all our testing – why do I need to consider a separate testing provider?
There’s a risk when you allow developers to ‘mark their own homework’. A fresh set of eyes will catch errors that the web developers won’t see. Independent testing gives you peace of mind that nothing’s been overlooked or hidden.
Our crowdtesting community is thoroughly vetted for technical knowledge and communication skills. Community testers record the issues they find in videos, screenshots and detailed notes, so that faults can easily be recreated and resolved. All issues raised by the crowd testers are verified by senior Digivante testers.
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.
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.
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.
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.
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.
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.
Every major digital project is different. So there’s no universal pricing. You can request a quote from us on our Pricing page – we’ll make sure it’s clear and transparent so you can see the cost clearly and know exactly what it covers.
Each tester can raise defects on a defect report page on our central test reporting platform. This includes screenshots and video evidence, along with steps to reproduce the defect. Testers check that the defect hasn’t already been reported, so we don’t receive duplicate defect reports. Our QA managers double check the reports before releasing them to our clients.
Our community is truly global, with testers based in 149 different countries around the world.
It depends on the project and client requirements, but typically it ranges from as few as 20 testers to as many as 200.
We value quality a lot in our testing community. Before we accept them, testers take an exam to check their English language skills and assess their testing competency.
Our test community gives our clients access to thousands of professional testers in 149 different countries. That means we can deliver very rapidly – reducing days’ worth of conventional testing to a few hours when we mobilise our people all over the world.
No. We use crowdsourced testing for some services, like exploratory testing, executing test cases and accessibility testing. We combine human testing with automated testing, depending on the specific need. But we also support clients with usability testing, test strategy and planning through our team augmentation service. And we provide people to augment client teams, both short-term and long-term.
We know that confidentiality is a real concern when using remote testers. Our business depends on making our testing service secure so you can be certain we take the greatest care to provide exceptionally secure systems and services. We use three-way contractual protection between the customer, the testing organisation and the testers themselves. We’ve worked with leading household names, from Microsoft and Metro Bank to Audi and Specsavers. They trust us to keep their testing secure and confidential.
Crowdtesting means using our community (or crowd) of vetted testers for rapid, large-scale testing on a range of devices and platforms. We use crowdtesting for exploratory testing and executing test cases. Our central teams manage quality control to make sure defects are reported clearly, with all duplicates compiled into a single report, and that defects can be reproduced.
Our testing capabilities are listed here. We cover a broad range including regression testing, accessibility testing, test automation, usability testing and more. We provide consultancy, service management and team augmentation. We deliver crowdtesting through our global Digivante professional tester community.
No. We think automation brings benefits specifically in unit testing, integration and where continuous improvement/ continuous development (CI/CD) is used.
We recommend only automating stable areas that are easy to maintain.
Automation is just one weapon in the QA armory. We recommend a nuanced approach: supplement automated testing with other QA approaches including planning, manual and crowd testing, user and accessibility testing. We recommend looking at the whole, not just focusing on automation alone.
No. Only automate stable entities with repeatable actions. Choose cases where there isn’t much change, to avoid higher maintenance costs and gaps in automation coverage.
No. We recommend fully integrating them with the whole QA team. Ideally, use the same team for automation and crowd testing, so they’re governed by one QA process.
Yes. As well as knowing what’s being automated, you need to know the coverage achieved. That way you can identify what you need to test by other means.
My test automation framework is getting overengineered. How should I identify when to automate and when not to?
At Digivante we create the very best manual test cases and coverage. They form the building blocks for good automation. These will show clearly whether it’s beneficial to automate or not.
I have a consultant building automation for me so why would I need to use an outsourced testing company?
It depends how thorough the consultant can be. Just one person can’t usually do it all! At Digivante we’re transparent on the framework we use and how we build the scripts. We make clear which tests are automated, crowd or manual. We provide clear documentation and training for internal staff.
Triage is key. It’s one of our key strengths. We look at failed builds then run any failed automation test cases in our community, clearly highlighting false positives/negatives and explaining issues. Then you can prioritise effective fixes.
Browse our latest blogs for news about testing, accessibility, usability and more.