Structured Bug Testing
In the digital world there is no room for errors. If software has functionality issues, users will switch to the other alternatives available. Put the quality of your software to the test with structured test cases – manually with the crowd or automated with our Device Cloud!
STRUCTURED BUG TESTING – YOUR ADVANTAGES
A crowd of over 300,000 registered testers with over 500,000 devices
Detailed error documentation including screenshots and screencasts
Endless combinations of operating systems and devices in the cloud
Live tracking and exporting bug lists using JIRA
Experienced project managers to assist the quality assurance process
Take the quality of your applications to the next level!
The challenge: Maintaining flawless functionality after the integration of new features
From the beta phase until after your software is released, there are always certain bugs you’d like to test on specific devices so that you can further optimise your software. Perhaps you’re planning on integrating a new feature and want to check the functionality of the software before releasing the modified product to the market. Or maybe you already know which areas you would like to test, but you are lacking a suitable testing environment, testers and certain devices.
The solution: Evaluate your core functions with Structured Bug Testing
When using a structured bug testing approach, there are two options that can be used depending on your requirements: manual and automated testing. The first consists of a crowd that works through specific and detailed test cases. Almost every click they perform is planned and the focus is on the documentation of every action the testers take.
Automated testing takes place in the cloud and requires specific testing scripts, which can be created using Selenium, Appium or HP QTP. The test is carried out with the help of virtual machines that are able to virtualise all combinations of operating systems, browsers, add-ons and custom software. Test automation is especially useful when a test needs to be performed on multiple browsers and devices and when it needs to be regularly repeated.
How it looks in practice
Manual Testing: The provider of a cloud storage platform wants to release a new product. Before doing so, they decide to perform a test that makes sure all core functions can be used by customers without encountering errors. A group of 24 testers perform detailed test cases on their own devices and under real world conditions. These consist of common functions such as uploading and saving data, creating new folders in the cloud and sharing with other users. The results show that moving files from one folder to another within the cloud is not possible on certain browsers.
Automated Testing: A complex website integrates new features at a high frequency. The development department, however, wants to test prior to release whether core features still function correctly on all devices. To do so, they use our Device Cloud, which performs an automated over-night test on all kinds of devices using test scripts (created e.g. with Selenium). In the morning the report shows which errors appeared on which devices. Integrating into a CI environment such as Jenkins is also easy to do.
Three Bug Tests for High-class Media Centres
“The tester feedback was very useful for us. They discovered indeed a few critical bugs. But it’s always better the testers encounter the bugs, and not the end-users.(…) We could export the bug list from the platform very easily and pass it on to our developers. That way we know exactly when and on which devices the bugs occurred”
Urszula Styrczula, Customer Care Manager at nexx.tv
Start your first test now
Test and optimise your websites, apps, games, chatbots and Internet of things applications with the help of our innovative services