Test audio system (AudioSource loading, playback state, stop, spatial audio) against the audio example using the iwsdk CLI.
65
79%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/test-audio/SKILL.mdRun 6 test suites covering audio loading, playback trigger, stop, system registration, component schema, and stability.
Configuration:
$IWSDK_REPO_ROOT/examples/audioTool calls: every tool call is npx @iwsdk/cli <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/cli 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.
IMPORTANT: Boolean values in ecs set-component must be actual JSON booleans (value: true), NOT strings (value: "true"). Strings silently fail to coerce.
cd $IWSDK_REPO_ROOT/examples/audio && npm run fresh:installWait 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/audio && npm run devIMPORTANT: 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/cli 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/cli ecs systems 2>/dev/nullThis must return JSON with a list of systems. If it fails:
Run these commands in order:
npx @iwsdk/cli browser reload --timeout 20000 2>/dev/null
Then: sleep 3
npx @iwsdk/cli xr enter --timeout 20000 2>/dev/null
Then: sleep 2
npx @iwsdk/cli browser logs --input-json '{"count":20,"level":["error"]}' 2>/dev/null
Assert: No error-level logs. Audio autoplay warnings are acceptable.
Test 1.1: Find Audio Entity
npx @iwsdk/cli ecs find --input-json '{"withComponents":["AudioSource"]}' 2>/dev/nullAssert: At least 1 entity. Save the first as <audio>.
The audio example uses a native scene level that creates entities via composition. The Spinner entity has an AudioSource.
Test 1.2: Verify Loaded State
npx @iwsdk/cli ecs query --input-json '{"entityIndex":<audio>,"components":["AudioSource"]}' 2>/dev/nullAssert:
src contains an audio file path (e.g., .mp3)_loaded = true (buffer loaded)_loading = false (not currently loading)_isPlaying = false (not playing yet — unless autoplay is set)volume = 1positional = trueTest 1.3: Pool Created
Assert: _pool exists with available array matching maxInstances.
Test 2.1: Request Play
npx @iwsdk/cli ecs set-component --input-json '{"entityIndex":<audio>,"componentId":"AudioSource","field":"_playRequested","value":true}' 2>/dev/nullThe set response may briefly show newValue: true. Wait one frame, then query the
component and assert _playRequested is false; the AudioSystem consumes the
request asynchronously.
sleep 1npx @iwsdk/cli ecs query --input-json '{"entityIndex":<audio>,"components":["AudioSource"]}' 2>/dev/nullTest 2.2: Play with Loop for Observable State
Set loop: true first, then request play:
npx @iwsdk/cli ecs set-component --input-json '{"entityIndex":<audio>,"componentId":"AudioSource","field":"loop","value":true}' 2>/dev/nullnpx @iwsdk/cli ecs set-component --input-json '{"entityIndex":<audio>,"componentId":"AudioSource","field":"_playRequested","value":true}' 2>/dev/nullThen query:
npx @iwsdk/cli ecs query --input-json '{"entityIndex":<audio>,"components":["AudioSource"]}' 2>/dev/nullAssert: _isPlaying = true (looping sound keeps playing).
Test 3.1: Request Stop
npx @iwsdk/cli ecs set-component --input-json '{"entityIndex":<audio>,"componentId":"AudioSource","field":"_stopRequested","value":true}' 2>/dev/nullAssert: _stopRequested consumed, _isPlaying becomes false.
npx @iwsdk/cli ecs systems 2>/dev/nullAssert:
enableDistanceCulling, cullingDistanceMultiplieraudioEntities >= 1npx @iwsdk/cli ecs components 2>/dev/nullAssert AudioSource fields:
src (FilePath), volume (Float32), loop (Boolean), autoplay (Boolean)positional (Boolean), refDistance, rolloffFactor, maxDistance, distanceModel, coneInnerAngle, coneOuterAngle, coneOuterGainplaybackMode (Enum), maxInstances (Int8), crossfadeDuration (Float32), instanceStealPolicy (Enum)_playRequested, _pauseRequested, _stopRequested (Boolean), _fadeIn, _fadeOut (Float32)_pool (Object), _instances (Object), _isPlaying (Boolean), _buffer (Object), _loaded, _loading (Boolean)npx @iwsdk/cli browser logs --input-json '{"count":30,"level":["error","warn"]}' 2>/dev/nullAssert: No application-level errors. Audio autoplay warnings and pre-existing 404 resource errors from page load are acceptable.
Kill the dev server:
cd $IWSDK_REPO_ROOT/examples/audio && npx @iwsdk/cli dev downOutput a summary table:
| Suite | Result |
|--------------------------|-----------|
| 1. Audio Loading | PASS/FAIL |
| 2. Playback Trigger | PASS/FAIL |
| 3. Stop | PASS/FAIL |
| 4. System Registration | PASS/FAIL |
| 5. Component Schema | PASS/FAIL |
| 6. 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/audio && npx @iwsdk/cli 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.
_playRequested, _pauseRequested, and _stopRequested are consumed by the AudioSystem within one frame. The npx @iwsdk/cli ecs set-component response may already show newValue: false.
Non-looping sounds may finish playing before you can query _isPlaying. Set loop: true before playing to observe a persistent _isPlaying: true state.
If _stopRequested and _playRequested are set simultaneously, stop wins.
IWER runs in a browser context where the AudioContext may be suspended until a user gesture. The MCP tools can verify ECS state transitions but cannot confirm actual audio output.
The audio example loads entities from ./scenes/audio.iwsdk.scene.json. Most entities are not created in index.js; they come from the scene document. Use npx @iwsdk/cli ecs find to discover them dynamically.
When setting boolean fields (like _playRequested, loop, _stopRequested) via npx @iwsdk/cli ecs set-component, the value must be a JSON boolean (true), not a string ("true"). Strings silently fail.
Never cache entity indices across page reloads. Always re-discover via npx @iwsdk/cli ecs find.
0778f51
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.