Step 2 - Features

The second 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 2

To begin Step 2, you select which Features we are testing. These are the features you want to get covered in this test cycle. At least one feature should be in-scope to be able to run a test.

  • In the above example, we've only allowed High and Critical bugs and have selected the following Features to be tested: Cart, Checkout Process - Production, Checkout Process - Staging, and Registration.

Note: Make sure that you’ve checked the feature box for features you wish to include in your test.

Closer Look: Features 

Managing Features

A well-written Feature will yield higher quality results for your tests. All bugs found will be assigned to a respective Feature. When describing how to find the part of the app, explain it as if describing it to someone who has never seen the product before. The Feature description is the only way for testers to know how to navigate your product in search of issues that are relevant to you, especially when it comes to non-obvious functionalities, where a certain level of user adoption is needed. 

Features may include:

  • where a given feature can be found

  • what is the expected behavior/user flow to be tested

  • what is out of scope within this feature/user flow

  • known issues 

  • acceptance criteria and other relevant information

  • user stories to verify. More on how to work with user stories can be found here

Different sections don’t have to mirror the described Features of an app. They can also be areas that are present in different processes or “parts” of the product. For example, sharing, filtering, or search might be present in different parts of the software, but all share a common code base. 

You can also use Features to define user-scenarios or flows to be tested. Including your internal acceptance criteria (if available) might also be a way to structure your test setup. To find more information on this, follow to the User Story Guide

General recommendations setting up Features:

  • Ideally, one Feature should be broad enough to allow you to run a test (but is by no means the average for our customers).

  • Features should be reusable for future test cycles of a given product. However, you can always edit a Feature on the Managed Features page, so the Feature content doesn't have be final.

Editing Features:

You can only edit Features on the Manage Features page. In other words, you can’t edit the Features on any test wizard page. The best practice would be to edit Features on the Manage Features page before creating a new test cycle.

If you need to make a change to a Feature while in the test wizard, follow the appropriate steps below:

There are three possible pages in the test setup wizard. Each can be identified by the call to action button in the bottom left of the wizard. (left column in the table)

Did this answer your question?