What problem does it solve?
This Skill prevents weak or misleading tests by defining a strict, real-resource-first testing strategy for vrcpilot’s VRChat automation adapters.
Core Features & Use Cases
- Real-resource priority testing: Prefer real filesystem I/O, real subprocess behavior, real loopback UDP, real Xvfb/X11, and real PipeWire audio fixtures over mocks.
- Controlled mock policy: Allow fakes only for vrcpilot-owned ABCs, while explicitly banning mocks of 3rd-party library surfaces and internal helper functions.
- Test organization standards: Enforce a 1:1 mirroring layout between
src/vrcpilot/ and tests/vrcpilot/, plus a clear testing taxonomy (unit, integration-with-fakes, integration-real, e2e).
- Quality guardrails: Avoid trivial tests, require substring-based error assertions, and include guidance for mutation testing to find weak coverage.
- Exception contract pinning: Provide a defined mechanism to pin public API contracts via a dedicated test marker.
Quick Start
Read this strategy before writing new tests so your test placement, resource usage, and mocking approach match the project’s guarantees.