To decide which test-setup example makes the most sense for you, you need to know which test type you're looking to run.
First, select New Exploratory Test.
Once selected, you will then choose which type of test you will be running.
Closer Look: Test Types
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.
Rapid tests are fast and can be completed in as little as two hours. They’re designed to catch high-priority bugs. When should you run a rapid test? They’re perfect for when you’re about to launch 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 check.”
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 recently developed a new feature. It’s the best way to find bugs present within new functionality, including edge cases that haven't been considered yet. When you run a focused test, you’re looking for all the potential problems in a specific segment of your software.
The coverage test 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 which device types to test on as well as multiple product areas. It’s a great way to make sure that your software works on a variety of real devices prior to release or following 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, this test gets you 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 an individual feature or of the overall user experience.
This is the most versatile and broadest type of test. It gives you a lot of room for custom requirements and allows you to precisely define your test scope. However, if you have an “unconventional” test setup in mind and are not sure how to go about running it, please contact your Customer Success Manager to work out a solution.
Test Types are important because they dictate what kind test you’ll be running, what the setup will look like, and what kind of results you’ll receive.
We’ve created five test setup examples to help illustrate the differences. Once you know what kind of test you're looking to run, you can use one of the below examples to help guide you in your setup:
- Web/Mobile Web - Rapid Test (Web, Production/Live)
- Web/Mobile Web - Focused Test (Web, Pre-Production/Staging)
- Web/Mobile Web - Coverage Test (Web, Production/Live)
- Mobile App - Focused Test (iOS, Pre-Production/Staging)
- Mobile App - Coverage Test (Android, Pre-Production/Staging)
Note: the above examples are not exhaustive in their product, environment, or test type combinations, but they will serve as a great starting point as you gain familiarity with the test IO platform.