Skip to main content

Section 8: QA & Testing

Testing your treatments before they go live ensures quality and prevents mistakes. This section covers all QA tools available in Auxia Console.

8.1 Why Test Treatments?​

The Importance of Testing​

Before activating treatments, testing helps you:

  • Verify content appears correctly
  • Check personalization works as expected
  • Validate eligibility rules target right users
  • Prevent errors from reaching real users
  • Build confidence before launch

Testing Philosophy​

PhaseWhat to Test
CreationContent, formatting, images
ConfigurationGuardrails, surfaces
Pre-LaunchEnd-to-end with real app
Post-LaunchMonitor for issues

8.2 Accessing QA Tools​

  1. Click Treatments & Journeys in the sidebar
  2. Select QA & Testing

QA & Testing Overview​

The QA section includes:

  • QA Users - Test accounts for previewing treatments
  • Test Treatments - Trigger treatments for specific users
  • QA Tags - Label and filter test content

8.3 QA Users​

What are QA Users?​

QA Users are special test accounts that can:

  • Receive treatments regardless of normal eligibility
  • Preview treatments before they go live
  • Test on real devices/apps

Setting Up QA Users​

Step 1: Create QA User

  1. Go to QA & Testing > QA Users
  2. Click + Add QA User
  3. Enter user identifier (e.g., email or user ID)
  4. Save

Step 2: Configure Device

  • Log into your app with the QA user account
  • Ensure the app is connected to your Auxia project

Step 3: Test

  • Trigger treatments from Console
  • Verify they appear in the app

QA User Attributes​

You can set attributes on QA users to test guardrails:

AttributeExampleTest Purpose
subscription_tier"Premium"Test premium-only treatments
days_since_signup3Test new user treatments
location"US"Test geo-targeted content

Managing QA Users​

View QA Users:

  • QA Users tab shows all configured users

Edit QA User:

  • Click user to modify attributes

Remove QA User:

  • Delete when no longer needed

8.4 Testing Treatments​

In-Console Preview​

Preview treatments directly in Console:

  1. Open treatment from portfolio
  2. Click Preview
  3. View approximate rendering

Preview Limitations:

  • Shows content structure, not exact app rendering
  • Personalization shows placeholder values
  • Not all interactive elements work

Testing on Real Devices​

For accurate testing:

  1. Set up QA User (see above)
  2. Target treatment to QA user
  3. Open app on test device
  4. Navigate to treatment surface
  5. Verify treatment appears correctly

Force-Sending Treatments​

To test a specific treatment:

  1. Go to QA & Testing
  2. Select "Test Treatment"
  3. Choose treatment to test
  4. Enter QA user ID
  5. Click "Send Test"
  6. Check device for treatment

Testing Checklist​

Before activating any treatment:

  • Content displays correctly
  • Images load properly
  • CTA button works
  • Personalization shows real values
  • Links/deeplinks navigate correctly
  • Treatment dismisses properly
  • Renders correctly on different screen sizes

8.5 Testing Guardrails​

What to Test​

Verify that guardrails:

  • Include intended users
  • Exclude unintended users
  • Handle edge cases correctly

Testing Approach​

Test 1: Positive Case

  • Set QA user with attributes that SHOULD match
  • Verify treatment is delivered

Test 2: Negative Case

  • Set QA user with attributes that SHOULD NOT match
  • Verify treatment is NOT delivered

Test 3: Boundary Cases

  • Test edge values (e.g., exactly 7 days)
  • Verify behavior at boundaries

Example: Testing a Rule​

Rule: Show treatment if days_since_signup < 7

QA User SettingExpected Result
days_since_signup = 3Should see treatment
days_since_signup = 7Should NOT see treatment
days_since_signup = 6Should see treatment

8.6 Testing Personalization​

What is Personalization?​

Personalization inserts user data into treatment content:

Hello `${first_name}`, welcome back!

Becomes:

Hello Sarah, welcome back!

Testing Personalization​

  1. Set QA user with required attributes

    • Example: first_name = "TestUser"

  2. Send treatment to QA user

  3. Verify personalization renders correctly

    • "Hello TestUser, welcome back!"

Common Personalization Issues​

IssueSymptomFix
Missing data fieldShows placeholder or blankEnsure user has attribute
Wrong field nameShows placeholderCheck field name spelling
Format issueUnexpected formattingCheck data type and format

8.7 QA Tags​

What are QA Tags?​

Tags help organize and identify test content.

Using Tags​

Tagging Treatments:

  • Add tags during creation
  • Mark as "QA", "Test", "Draft", etc.

Filtering by Tag:

  • Use tag filters in portfolio
  • Quickly find test content

Removing Tags:

  • Remove tags when going live
  • Keeps portfolio clean

8.8 Testing Workflow​

1. Create Treatment (Draft)
         ↓
2. In-Console Preview
         ↓
3. Set Up QA User
         ↓
4. Test on Device
         ↓
5. Verify All Elements
         ↓
6. Fix Any Issues
         ↓
7. Re-test
         ↓
8. Activate

Pre-Launch Checklist​

Content:

  • Title is correct
  • Body text is accurate
  • No typos or errors
  • Personalization works

Visual:

  • Image loads
  • Layout looks correct
  • Colors are right
  • CTA is visible

Functionality:

  • CTA works correctly
  • Links navigate properly
  • Dismiss works

Configuration:

  • Correct surfaces selected
  • Guardrails are right
  • Journey assignment is correct

8.9 Testing Best Practices​

Test Early and Often​

  • Don't wait until the end to test
  • Test after each significant change
  • Quick tests catch issues early

Use Multiple Test Accounts​

  • Different attribute combinations
  • Different devices/platforms
  • Different app versions

Document Your Tests​

Keep track of:

  • What was tested
  • Test results (pass/fail)
  • Issues found and fixed
  • Who tested and when

Involve Others​

  • Have colleagues review content
  • Get second opinion on appearance
  • Fresh eyes catch issues

Test in Production-Like Environment​

  • Use staging/production app versions
  • Test with realistic data
  • Simulate real user conditions

8.10 Common Testing Issues​

Treatment Not Appearing​

Check:

  1. QA user is set up correctly
  2. User identifier matches
  3. Treatment is targeting right surface
  4. App is connected to correct project
  5. Device has network connectivity

Wrong Content Showing​

Check:

  1. Correct treatment selected
  2. No caching issues (try clearing app cache)
  3. Correct version of treatment

Personalization Not Working​

Check:

  1. QA user has required attributes
  2. Attribute names match exactly
  3. Data types are correct

Treatment Showing to Wrong Users​

Check:

  1. Guardrails are correct
  2. No conflicting rules
  3. Treatment status (is it active?)

8.11 QA Permissions​

Required Permissions​

PermissionAccess
TREATMENT_VIEWView treatments
QA_USER_VIEWView QA users
QA_USER_EDITManage QA users
TREATMENT_TESTSend test treatments

Getting Access​

Contact your admin if you need QA testing permissions.

Next Section​

Continue to Section 9: Configuration for system configuration documentation.