Skip to main content

Testing your game

There are four primary ways to test your Jest SDK integration:

  • Testing locally with mocks

    • Best for day-to-day local development; no platform required.
    • Use the JestSDK debug menu to adjust player state and simulate platform responses

  • Testing with the hosted emulator

    • Load your local dev server inside the live Jest.com platform shell by appending ?host=http://localhost:3000 to the game URL.
    • Useful for testing the real platform integration without uploading a new build

  • Sandbox users

    • Test an uploaded build on Jest.com using a logged-in sandbox account.
    • Useful for end-to-end validation of platform-backed features (notifications, payments, persistence) and for inspecting/resetting user state in the Developer Console

  • The Simulator

    • Run an uploaded build or a local URL inside the Developer Console with a mocked SDK host.
    • Primary use case: record a self-review attached to a version for moderators to watch during review. Also includes a quality checklist.

In practice, most teams iterate locally in mock mode, optionally use the hosted emulator for integration testing, validate an uploaded build with sandbox users, and record a self-review in the Simulator before submitting for review.

Developers can also preview a specific uploaded build using their own account via the version preview link before releasing.