This article provides an overview of the general workflow and guidelines for HX Testing at Test IO. However, please note that HX Testing can vary significantly from one Test Cycle to another depending on the client’s specific requirements. Always make sure to carefully review the Test Instructions for each cycle to ensure you understand the objectives and expectations.

Before starting HX testing, it’s essential to carefully read and understand the test instructions in advance. This ensures you meet the objectives and deliver accurate results.

Understanding Test Objectives and Requirements:

HX test cycles are structured to guide testers through a series of steps that evaluate specific features, user interactions, and overall experience. Each cycle is carefully designed to ensure testers can assess both physical and digital touchpoints, as well as the emotional impact of the product or service.

The Test Instructions provide a detailed roadmap for the testing process. It is essential to read and understand the entire set of instructions before starting to ensure accurate and complete results.

Test Instructions will also contain a link that will lead you to the Human Experience Space. This space is a dedicated platform for HX testing at Test IO.

Additionally, if you encounter a functional bug and the test instructions permit reporting it, please submit it as a standard functional bug. You can find more details on how to report functional bugs here.

You can join the HX Test IO Space by the link that will be provided in the test instructions of the specific HX cycle.

HX Space has journeys as a task; this means that after you open a link which will be provided in the test instructions, you will see a journey with a description and steps. You can join a journey via the Accept journey button located in the bottom action bar.

Once you accept a journey, it will appear on your Dashboard under the Active journey tab.

You will be able to execute a journey only while the journey itself is running. Journey consists of steps that will be presented in sequential order, with a progress bar so that it is easier for you to track the progress.

In general, steps will include instructions, attachments (if any), and reports. Reports may be required or optional. If the report is required, this means that you must submit it before proceeding to the next step. Similarly, steps may have a specific time request. In both cases, this will be clearly labeled and highlighted.

After completing each step, a tester must mark it as completed.

You will be able to submit a report in two ways. From the specific step itself, or by clicking on the Submit report button in the Action bar.

​NOTE: If you select the "Submit report" button from the action bar, you will need to select a step and report (if multiple are available) in order to access the relevant form.

For each step of the user journey, you may need to assess specific criteria, assign scores, and provide justifications for your evaluations.

Report may have predefined criteria to evaluate, such as ease of use, friendliness, error handling etc. The list of criteria may vary depending on the customer's request.

Assign numerical scores (e.g., 1-5) based on your experience. Be consistent and objective when scoring.

Provide detailed explanations for your scores. For example: