Tests

SkillWeb & browsing

Add or maintain node:test, native-load/runtime, visual/offscreen, hardware-dependent, browser/WebGL/Three.js, and integration validation.

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Tests skill

What this skill tells your AI

The instructions your AI receives, as published by node-3d/node-3d in .agents/skills/tests/SKILL.md and read by ahel’s review.

Executable validation and the meaning of test coverage.

Name the layer: pure TS, native adapter, native load, native runtime, rendering, plugin integration, or compute/hardware.
Use the package's established test/bootstrap shape and focused node --test scripts.
Skip unsupported native/hardware tests gracefully rather than converting them into misleading passes.
Centralize GLFW/core test windows through established helpers so CI-specific context/platform settings remain consistent.
For visual tests, require deterministic-enough output before adding baselines.
Report exactly what the test proves.
Skip only for a named environmental absence; native errors in an available environment are failures. Use child-process probes when initialization order makes an in-process test invalid.

Load .agents/references/ci-platform-limits.md when platform runners, graphics contexts, GPUs, or native runtime availability affect the test.

Add $ci only when workflow behavior itself changes.

Advanced