Skip to content

Testing

This page collects local integration and pre-release checks. Complete installation and Quick Start for the target engine, then validate the required business features.

  • The IGP desktop client is installed and can start.
  • The correct appId, environment, and backend application configuration are available.
  • The game’s startup flow explicitly initializes the SDK.
  • Achievement keys, game authorization, compliance, and other backend settings are ready.
  • For room capabilities, launch the game from the IGP desktop client using the integration flow.
  1. Install the main and required optional packages with Unity installation.
  2. Complete Unity Quick Start.
  3. Prepare desktop-client integration in the Editor with Unity debugging.
  4. Verify explicit results for authorization, achievements, and every required optional capability.
  1. Download and extract the GameMaker release.
  2. Open the windows-auth-achievements sample project.
  3. Follow GameMaker Quick Start to verify initialization, authorization, achievements, and compliance state.
  4. Use GameMaker debugging for troubleshooting.
  1. Follow Godot installation to import Core and optional packages matching the exact Godot version.
  2. Complete Godot Quick Start and verify /root/IGP, the Desktop Session, game authorization, and capabilities.
  3. Download the Godot test project from the same SDK release and exact Godot variant.
  4. Import Core, Compliance, and GameKit into the standalone SDKTest/ project, replace appId and environment with the test application values, and run main.tscn.

Minimum Godot acceptance:

  • Initialization succeeds and attached, ready, and authorization reach explicit states.
  • Core, Compliance, and GameKit correctly detect installed modules.
  • Achievements, compliance, user profiles, leaderboards, and sharing return success or explainable business errors.
  • An unavailable desktop client, invalid appId, or missing capability follows a clear failure path.
FeatureCheck page
Startup and connectionStartup and connection
Game authorizationGame authorization
Real-name verification and anti-addictionReal-name verification and anti-addiction
AchievementsAchievements
Multiplayer lobbyMultiplayer lobby
RoomsRooms
Realtime messagingRealtime messaging
State and RPCState and RPC
Mirror transportMirror transport
  • appId, environment, and backend application use production values.
  • Sample keys have been replaced with actual backend achievement keys.
  • Test projects, achievement-clear actions, debug arguments, and temporary settings are absent from production player flows.
  • Failure, detach, authorization failure, and every compliance BLOCK state have game-side handling.
  • SDK initialization has one clear owner, and optional modules and capabilities are checked before use.