test IO offers several types of functional tests, as well as usability testing, all carried out by carefully selected and trained human testers. These tests are designed to get you the kinds of results you need, in the time frame that you need them in.
The “best” test type for you may change depending on the given situation. The effectiveness of a test varies based upon your goals.
Rapid tests are fast and can finish in as soon as an hour. They’re designed to catch high-priority bugs. When should you run a rapid test? They’re perfect for when you’re about to commit a new build or make a pull request. Rapid tests give you the peace of mind that your app does what it’s supposed to and that it works on the devices it’s been tested on. When you run a rapid test, you’re looking for a green light or a “sanity test.”
When performing a focused test, testers delve deep into a specific feature or a section of your app. It’s the equivalent of putting a part of your software under the microscope. Many teams choose to run focused tests when they’ve developed a new feature. It’s the way to find bugs big and small in new functionality, including edge cases no one has considered yet. When you run a focused test, you’re looking for all the potential problems in a segment of your software.
The coverage test is deals with one of the main challenges of software development: whether your app will work on phones and tablets of varying screen sizes, different browsers, on multiple versions of iOS, or on different flavors of Android. You can specify what types of devices to test on and multiple product sections. It’s a great way to make sure that your software will work on a variety of real devices before release or after major changes. In particular, it comes in handy when most of your developers work on a single platform like Chrome or the latest version of iOS.
From early-stage feedback to pre-release testing to finding usability issues in production products, this test gets you timely and useful feedback from a diverse group of usability testers. For better results and more useful suggestions, we recommend adding user stories or scenarios, though you can also request an evaluation of the overall user experience.
A custom test follows the testing specifications you determine when you set up the test. You can specify the length of the test, the devices and OS versions it should be run on, and what parts of your product to check. It can be a broad-spectrum test or focus on a narrow scope of your software. Our testers are experienced, so you can explain what you want in plain language.