Test your game
Run a draft preview, test every player path, and validate the campaign before launch.
In this article, you'll test a game before launch using draft preview, device checks, and a short validation pass.
What draft testing means
A game inside a draft campaign is not publicly live. Use Preview while you are still building. Use Share, final URLs, and production QR codes only after the campaign is published.
Test workflow
Open a draft preview
From the campaign or the game you want to check, open Preview to generate a draft test link. Use the desktop preview first, then scan the preview QR code to continue on a real phone.
Play every relevant outcome path
Run the player paths that matter for this game:
- winner
- loser
- eligible-for-draw
- limit-reached or unavailable states when restrictions apply
For luck-based games, confirm the displayed reward or draw message matches the configured outcome. For skill-based games, confirm the score flow, completion state, and post-game message.
Test the surrounding player journey
If the campaign uses opt-in, complete the consent step. If it uses a participation form, submit it. If the game is usually entered from a landing page, test that route as well as the direct game entry point.
Check desktop and mobile
Review layout, crop, button placement, and readability on both desktop and mobile. If the game is mainly shared through QR or social channels, test on the exact device types your audience will use most.
Confirm follow-up actions
If notifications are enabled, send at least one real test email and check the inbox and spam folder. If the reward uses redemption or coupon steps, confirm the winner journey still makes sense after the win.
Run validation before publish
Open Publish to review the validation modal. Fix every error, review warnings, save your changes, then rerun the test paths that were affected.
Suggested checklist
- the game loads without broken assets
- winner, loser, and eligible states are correct when those states apply
- translated text is present in every active language
- opt-in, participation form, and notification behavior all work when enabled
- mobile and desktop behavior match the intended distribution plan
- direct game entry and landing-page entry both work when relevant