Establish the test record
Write down host, provider, exact title, game ID if shown, device, browser, date and demo mode. Capture the information panel before changing stake or feature settings.
A useful demo test checks the paytable, stake controls, reel changes and feature instructions in a fixed order. Short sessions reveal usability and rules, not the mathematical return of the game.
Map the base-game state
Observe minimum and maximum reel heights, displayed ways, stake controls, wild and scatter behaviour, cascade order and balance updates across a small fixed session.
Inspect feature rules first
Read free-spin trigger, retrigger, multiplier, bonus-buy, gamble and maximum-win provisions before trying to observe them. Do not infer rules from animation alone.
Test responsive controls
Check portrait and landscape layout, paytable access, mute, fullscreen, responsible-play message and exit. Record clipped buttons, focus traps or redirects as usability findings.
Write bounded conclusions
Report what the rules and interface showed, distinguish unobserved features, and avoid hit-rate or strategy claims from a short sample. Link every real-money CTA through a separately verified route.
A demo session is a usability test
It cannot validate RNG fairness, long-run RTP, feature probability or operator cash-out performance without the appropriate independent evidence.
Testing checklist questions
How many spins are enough to test RTP?
A short manual session is not suitable for validating long-run RTP; use it for controls and rules.
What should I screenshot?
Capture provider/title identity, information panel and any reproducible interface issue without personal data.
Can I compare two demos?
Yes for declared rules and usability when the versions are documented, not as proof one will pay more next time.