Step 1 - Test Environment

The first step in test IO's Test Wizard setup.

test IO Customer Success avatar
Written by test IO Customer Success
Updated over a week ago

Step 1 

First, you will select the Test Type you will be running (in this case, Rapid).

Once you select which type of test you're running, you need to specify the Test Environment. This is where you choose the environment that you want the testers to evaluate and specify the particulars of accessing it.

Next, you select which bug severities to allow.

Closer Look: Bug Severities

Different test types include different severity levels in the test scope. Sometimes the bug severities you define internally may vary from test IO's default guidelines. To make sure our views on severity are in line, here’s how we classify bugs and issues. 

Functional Bugs

Critical - Preventing a function of the app or website, causes a potential loss of income for the company running the app or website - i.e. an app crash or "not able to login."

High - Serious impact on user experience but doesn’t prevent the function of the app or website.

Low - Minimal impact on user experience.

Non-Functional Bugs

Usability - suggested improvements to existing features and functions that would make the product easier and more intuitive to use.

Visual - The user can accomplish a task, but the interface looks wrong, typically because of responsive design, CSS, HTML, or layout framework problems.

Content - Bugs relate to missing data, images, or broken links.

Note: Non-Functional Bugs are classified as low-severity bugs by definition.

Did this answer your question?