Skip to main content

Testing cycle

Note: Changes made during testing are permanent unless reset. Always use dedicated test users. A typical testing iteration takes 5-10 minutes.

Setup (One-time)​

  1. Create your engagement strategy (points, behaviors, rewards)
  2. Create a descriptively named test user (e.g., "test-rewards-basic")

Testing cycle​

  1. Open the test user from the users page
  2. Click Log Activity (keyboard shortcut: L) to open the activity panel and submit an activity
  3. The user details view auto-refreshes. Review the results across the relevant tabs:
    • Activity
    • KPIs
    • Points
    • Rewards
    • Coupons
  4. Use the Request log footer to inspect the request/response payload if something doesn't behave as expected
  5. Adjust strategy based on findings
  6. Reset the user (where supported) for a clean state if needed

Best Practices​

  • Test edge cases (minimum/maximum values)
  • Verify behaviour across different time periods
  • Document test scenarios and results
  • Use the auto-refreshing user details view to see updates without leaving the page

Troubleshooting​

  • Activities not appearing: Verify activity triggers and user eligibility
  • Points not accumulating: Check point rules and activity mapping
  • Rewards not triggering: Review threshold settings and user qualification conditions
  • State persisting after reset: Clear browser cache or create new test user

For setup guidance, refer to the quick start guide.