Establish the test conditions

Use a game context that you have already prepared online. Finish the current attempt, note the browser or installed icon, then disable connectivity and close the game view. Open it again through that same route. Leaving an already loaded page running is not a launch test.

The installation help’s Ready for offline play message is useful background evidence, but not the acceptance test itself. An empty message is not confirmation, and a successful test in one browser says nothing about another browser’s files.

Check each expected capability

Keep the checks independent. The core game can pass while optional audio fails, and a familiar score only confirms the local record you actually inspected.

  1. Launch: the game opens without a browser connection-error page.
  2. Play: a new run starts, steering changes the curve, and a result appears when the run ends.
  3. Appearance: the menu opens and the unlocked forest you plan to use displays its artwork.
  4. Audio: after a deliberate interaction, check Music and Sounds separately with the intended output device.

Choose the next step from the failed check

If launch fails, reconnect and follow the preparation guide before repeating the test. If only one forest lacks artwork, record which forest and whether it appears online. If only sound fails, use the offline-audio checks; the fallback format may need a connection.

If controls fail both online and offline, investigate focus or an open dialog rather than assuming the cache is responsible. For support, report the failed check and test context. Keep site data intact while investigating. Passing today establishes readiness for that setup now, not a promise that browser-managed files will remain forever.