Choosing the right kind of test for your software

October 26, 2018
Powen Shiah
Powen Shiah

Focus Test

When executing a focus test, test IO's software testers delve deep into a specific feature or a section of a website or a mobile app. It’s the equivalent of putting a part of your software under the microscope. Often,  teams choose to run focus 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 choose to run a focus test, you’re looking for all the potential problems in a segment of your software.

Coverage Test

The coverage test is deals with one of the main challenges of software development: will your app 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. It’s a great way to make sure that your software will work on a variety of real-world devices 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.

Usability Test

From early-stage feedback to pre-release testing to finding usability issues in production products, the usability 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 of your website or mobile app.

Rapid Test

Rapid tests are fast and can finish in as soon as an hour. They’re designed to catch absolutely critical, high-priority bugs, the kinds of bugs you shouldn't publish a release with. 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 or website does what it’s intended 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.”

Rapid tests are available in test IO's professional and elite packages.

Custom Test

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.


Have more questions about the kinds of QA tests you can run on test IO? Get in touch for a demo

Read More

January 17, 2020
QA Squads: a new offering from test IO, amplified by EPAM

Going beyond software  Customers come to test IO for many different reasons. Sometimes, an internal product or QA team needs a force multiplier for real-world testing – to extend the existing QA team’s processes and activities beyond their internal team. Other times, it’s crisis mode – perhaps QA leadership has left the company, or there is a critical product release upcoming that […]

November 25, 2019
iOS testing: TestFlight or Resigner

Here's our guide to which method you should use you to distribute your IOS app to the crowd.

November 15, 2019
Exploratory Testing vs. Test Case Testing

Exploratory testing emphasizes creativity and learning. Test Case testing emphasizes planning and execution. Which one is right for you?

Ship Faster, Sleep Better

Get a Demo
twitterfacebooklinkedin