Testing on edugames.dev
edugames.dev is the developer sandbox: it runs your uploaded game package exactly as the edu.games player will, with a live conformance-checked statement feed beside the game. Use it to verify your xAPI instrumentation before submitting for review.
- Upload your game zip in the dev portal (a draft is enough — no review needed).
- On the game’s Analytics Readiness page, choose a test persona and press Open in sandbox.
- A session opens on edugames.dev with your game on the left and the live statement feed on the right. Play — every statement your game sends appears within seconds, annotated pass / warn / fail against the emission profile.
- Real launch context. The sandbox injects the same
EDUGAMES_LAUNCHglobals and postMessage the production player uses — the SDK picks them up with no code changes. - Test personas. Sessions run as fake students (Alex, Billie, Casey, Devon), so you can exercise identity handling without real accounts.
- Isolated data. Sandbox statements are stored under a dedicated sandbox credential and never reach teacher or platform analytics.
- Conformance checking. The same checker that powers your Analytics Readiness badges annotates each statement live.
edugames.dev has no login. Every session URL contains a signed, single-session token minted by your dev-portal account and expires after two hours. When a session expires, just open a new one — nothing is lost, statements stay in your inspector.
https://edugames.dev/run/v1.eyJjcmVkIjoi... ← signed launch token (2h)Instrument with the SDK → upload a fresh zip → Open in sandbox → play until the feed shows no warnings → check Analytics Readiness for your conformance level and unlocked presets → submit for review. Warnings in the feed link the exact profile rule being violated, so fixes are usually one-liners.