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.
Before testing
Section titled “Before testing”- 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.
- Install the main and required optional packages with Unity installation.
- Complete Unity Quick Start.
- Prepare desktop-client integration in the Editor with Unity debugging.
- Verify explicit results for authorization, achievements, and every required optional capability.
GameMaker
Section titled “GameMaker”- Download and extract the GameMaker release.
- Open the
windows-auth-achievementssample project. - Follow GameMaker Quick Start to verify initialization, authorization, achievements, and compliance state.
- Use GameMaker debugging for troubleshooting.
- Follow Godot installation to import Core and optional packages matching the exact Godot version.
- Complete Godot Quick Start and verify
/root/IGP, the Desktop Session, game authorization, and capabilities. - Download the Godot test project from the same SDK release and exact Godot variant.
- Import Core, Compliance, and GameKit into the standalone
SDKTest/project, replaceappIdand environment with the test application values, and runmain.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.
Checks by feature
Section titled “Checks by feature”| Feature | Check page |
|---|---|
| Startup and connection | Startup and connection |
| Game authorization | Game authorization |
| Real-name verification and anti-addiction | Real-name verification and anti-addiction |
| Achievements | Achievements |
| Multiplayer lobby | Multiplayer lobby |
| Rooms | Rooms |
| Realtime messaging | Realtime messaging |
| State and RPC | State and RPC |
| Mirror transport | Mirror transport |
Pre-release checks
Section titled “Pre-release checks”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
BLOCKstate have game-side handling. - SDK initialization has one clear owner, and optional modules and capabilities are checked before use.