// Test level system (LevelRoot, LevelTag, default lighting, scene hierarchy) against the poke example using the iwsdk CLI.
| name | test-level |
| description | Test level system (LevelRoot, LevelTag, default lighting, scene hierarchy) against the poke example using the iwsdk CLI. |
| argument-hint | [--suite root|tags|lighting|hierarchy|all] |
Run 5 test suites covering LevelRoot, LevelTag membership, default lighting, scene hierarchy, and stability.
Configuration:
$IWSDK_REPO_ROOT/examples/pokeTool calls: every tool call is npx iwsdk <subcommand> [--input-json '<JSON>'] [--timeout <ms>], run from inside the example workspace (cwd $EXAMPLE_DIR). The CLI auto-discovers the IWSDK app root from cwd, so no path tricks are required. Run npx iwsdk mcp inspect from the example to discover available tools and their CLI subcommands.
<JSON> is a JSON object string. Omit --input-json if no arguments are needed.{ok, workspaceRoot, operation, result}. Parse it to check assertions.--timeout 20000 for operations that may take longer (reload, xr enter, screenshot).IMPORTANT: Run each Bash command one at a time. Parse the JSON output and verify assertions before moving to the next command. Do NOT chain multiple CLI commands together.
IMPORTANT: When the instructions say "wait N seconds", use sleep N as a separate Bash command.
cd $IWSDK_REPO_ROOT/examples/poke && npm run fresh:install
Wait for this to complete before proceeding.
Start the dev server as a background task using the Bash tool's run_in_background: true parameter:
cd $IWSDK_REPO_ROOT/examples/poke && npm run dev
IMPORTANT: This command MUST be run with run_in_background: true on the Bash tool — do NOT append & to the command itself.
Once the background task is launched, poll the output for Vite's ready message (up to 60s). You can also run npx iwsdk dev status from the example directory until state.running becomes true. You do not need to extract or manage the port yourself; subsequent commands resolve the active runtime through the CLI automatically.
If the server fails to start within 60 seconds, report FAIL for all suites and skip to Step 5.
npx iwsdk ecs systems 2>/dev/null
This must return JSON with a list of systems. If it fails:
Run these commands in order:
npx iwsdk browser reload --timeout 20000 2>/dev/null
Then: sleep 3
npx iwsdk xr enter --timeout 20000 2>/dev/null
Then: sleep 2
npx iwsdk browser logs --input-json '{"count":20,"level":["error","warn"]}' 2>/dev/null
Assert: No error-level logs.
Test 1.1: Find LevelRoot Entity
npx iwsdk ecs find --input-json '{"withComponents":["LevelRoot"]}' 2>/dev/null
Assert: Exactly 1 entity. Save its entityIndex as <root>.
Entity should have name "LevelRoot".
Entity should also have: Transform, LevelTag, DomeGradient, IBLGradient.
Test 1.2: LevelRoot Transform at Identity
npx iwsdk ecs query --input-json '{"entityIndex":<root>,"components":["Transform"]}' 2>/dev/null
Assert:
[0, 0, 0] (approximately)[0, 0, 0, 1][1, 1, 1]The LevelSystem enforces identity transform on the level root every frame.
Test 2.1: All Level Entities Tagged
npx iwsdk ecs find --input-json '{"withComponents":["LevelTag"]}' 2>/dev/null
Assert: Multiple entities — all entities except entity 0 (scene root, which is persistent).
Test 2.2: LevelTag ID Matches
Pick any tagged entity from the results above:
npx iwsdk ecs query --input-json '{"entityIndex":<any-tagged>,"components":["LevelTag"]}' 2>/dev/null
Assert: id = "level:default"
All tagged entities should have the same id value ("level:default" for the initial level).
Test 2.3: Persistent Entities Excluded
npx iwsdk ecs find --input-json '{"withComponents":["Transform"],"withoutComponents":["LevelTag"]}' 2>/dev/null
Assert: 10 entities — entity 0 (scene root) plus 9 persistent input-rig entities created by the world bootstrap (xrOrigin, head, ray/grip/indexTip spaces for left and right). None of these should carry LevelTag.
Test 3.1: LevelRoot Has Both Environment Components
npx iwsdk ecs query --input-json '{"entityIndex":<root>,"components":["DomeGradient","IBLGradient"]}' 2>/dev/null
Assert: Both components present with default color values.
Test 3.2: LevelSystem Config
npx iwsdk ecs systems 2>/dev/null
Assert: LevelSystem has config key: defaultLighting.
Test 4.1: LevelRoot is Child of Scene Root
npx iwsdk scene hierarchy --input-json '{"maxDepth":2}' 2>/dev/null
Assert:
Test 4.2: Entity Count
npx iwsdk ecs find --input-json '{"limit":50}' 2>/dev/null
Assert: Total entity count should be >= 5.
npx iwsdk browser logs --input-json '{"count":30,"level":["error","warn"]}' 2>/dev/null
Assert: No application-level errors or warnings. Pre-existing 404 resource errors from page load are acceptable.
Kill the dev server:
cd $IWSDK_REPO_ROOT/examples/poke && npx iwsdk dev down
Output a summary table:
| Suite | Result |
|------------------------|-----------|
| 1. LevelRoot | PASS/FAIL |
| 2. LevelTag Membership | PASS/FAIL |
| 3. Default Lighting | PASS/FAIL |
| 4. Scene Hierarchy | PASS/FAIL |
| 5. Stability | PASS/FAIL |
If any suite fails, include which assertion failed and actual vs expected values.
If at any point a transient error occurs (server crash, WebSocket timeout, connection refused, etc.) that is NOT caused by a source code bug:
cd $IWSDK_REPO_ROOT/examples/poke && npx iwsdk dev downOnly give up after one retry attempt per suite. If the same suite fails twice, mark it FAIL and continue to the next suite.
When no GLXF level URL is provided, the level id is "level:default". All entities created via world.createTransformEntity() (without persistent: true) automatically receive LevelTag with this id.
LevelSystem.update() checks and resets the level root's transform to identity every frame. If you modify the level root's position via ecs set-component, it will be reset on the next frame.
Entity 0 wraps the Three.js Scene object. It has Transform but no LevelTag — it's the persistent root that survives level changes.
Never cache entity indices across page reloads. Always re-discover via npx iwsdk ecs find.
MUST read this skill BEFORE developing VR/MR/browser-first 3D applications using IWSDK (Immersive Web SDK). Covers project scaffolding, headless browser setup, CLI tools, reference system, ECS debugging, XR emulation, verification workflows, deployment, and known issues.
Test audio system (AudioSource loading, playback state, stop, spatial audio) against the audio example using the iwsdk CLI.
Test ECS core functionality (system registration, components, Transform sync, pause/step/resume, system toggle, entity discovery, snapshots) against the poke example using the iwsdk CLI.
Test environment system (DomeGradient, IBLGradient, default lighting, component schemas) against the poke example using the iwsdk CLI.
Test grab system (distance grab, one-hand grab, two-hand grab) against the grab example using the iwsdk CLI.
Test XR interactions (ray, poke/touch, dual-mode, audio, UI panel) against the poke example using the iwsdk CLI.