Skip to main content

Understanding the Payout and Reimbursement System for HX Testing

Be aware of the rules for payouts and reimbursements.

Yauheni Liashko avatar
Written by Yauheni Liashko
Updated over 4 months ago

Motivation

HX Testing at Test IO is a rewarding process, both in terms of the value you bring as a tester and the compensation you receive for your time, effort, and expenses. This article explains how payouts and reimbursements work for HX Test Cycles, including key details about the process and policies.

How Testers Are Compensated

For HX test cycles, the payout structure is designed to reward testers for both their testing efforts and their completion of the entire User Journey. Here's how it works:

Payout Components:

  1. Regular Payout for Reports submitted in test (both Functional Bugs and Custom reports):
    Testers are compensated for submitting reports such as Functional bugs or Custom Reports in line with the Test Instructions. Each valid bug report is reviewed and rewarded based on its type and severity.

  2. Additional Payout for Completing the User Journey:
    HX tests require testers to complete the entire User Journey and submit all required deliverables. This includes:

    • Filling in custom test reports for each Experience Step.

    • Completing any required surveys (e.g., Typeform surveys).

    • Providing detailed feedback and artifacts (e.g., screenshots, videos).

  3. Reimbursement for Necessary Expenses:
    If the User Journey involves spending money — such as purchasing a product or ordering a service — Test IO reimburses these expenses (details below). This ensures testers are not out of pocket for costs incurred during testing.

Please note that in HX testing, there is no competition between testers for Custom Reports. Each tester participates individually, and their reports are unique and valuable. Testers do not interfere with one another, and every tester receives a guaranteed payout for submitted reports, provided the entire end-to-end journey is completed and all required artifacts (e.g., attachments, mandatory reports, surveys) are included.

However, for Functional Bugs, standard competition rules apply.

How Reimbursements for Physical Touchpoints Are Processed

Certain HX test cycles may require testers to interact with physical touchpoints, such as purchasing a product, using a service, or visiting a location. In such cases, reimbursement is provided to cover the necessary expenses.

How It Works:

  • Reimbursement Information in Test Instructions:
    If a test cycle involves spending money, the Test Instructions will specify:

    • The amount eligible for reimbursement (e.g., up to $50 for a product purchase).

    • The type of expenses covered (e.g., product cost, shipping fees).

    • Any additional conditions or limitations (e.g., specific brands or services to purchase).

  • Submitting Proof for Reimbursement:
    To receive reimbursement, testers must provide valid proof of purchase. This typically includes:

    • A receipt or invoice showing the purchase details (e.g., product name, price, and date).

    • Any additional documentation requested in the Test Instructions (e.g., a photo of the product or packaging).

  • Reimbursement Processing Time:
    Once the required proof is submitted, reimbursements are processed according to Test IO’s standard timelines. Testers are notified once the reimbursement is approved and paid.

Common Reimbursement Policies and Requirements

To ensure your reimbursement request is processed smoothly, it’s important to follow these guidelines:

What is Reimbursed:

  • Eligible Expenses:

    • Product or service costs explicitly required for the test.

    • Shipping fees, if applicable and mentioned in the Test Instructions.

    • Taxes or other fees directly related to the purchase.

  • Spending Limits:
    The Test Instructions will specify a maximum reimbursement amount. Any expenses above this limit will not be covered unless explicitly approved in advance.

What is NOT Reimbursed:

  • Purchases or services not mentioned in the Test Instructions.

  • Personal expenses unrelated to the test (e.g., buying additional items not required for testing).

  • Expenses incurred without valid proof of purchase (e.g., missing receipts).

Requirements to Get Reimbursed:

  1. Follow the Test Instructions:
    Only purchase or order what is explicitly required in the User Journey.

  2. Submit Valid Proof:
    Ensure your receipt or invoice is clear and includes all necessary details (e.g., item name, price, date).

  3. Meet Deadlines:
    Submit your reimbursement request within the timeframe specified in the Test Instructions. Late requests may not be processed.

If you’re unsure about any aspect of the reimbursement process, consult the Team Lead (TL) in the chat before making a purchase.

Additional Tips for Testers

  • Double-Check Instructions:
    Always read the Test Instructions carefully to understand the payout structure and reimbursement rules before starting the test.

  • Keep All Documentation:
    Save receipts, screenshots, and any other proof of purchase until your reimbursement is confirmed.

  • Ask for Clarification:
    If you have questions about eligible expenses or reimbursement policies, reach out to the TL for guidance.

Did this answer your question?