vrcpilot-testing

Define a real-resource-first testing strategy for vrcpilot automation adapters.

7|Updated May 7, 2026
One-click install
npx skills add https://github.com/MLShukai/vrcpilot --skill vrcpilot-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vrcpilot-testing
Source: https://github.com/MLShukai/vrcpilot/tree/main/.claude/skills/vrcpilot-testing
Command: npx skills add https://github.com/MLShukai/vrcpilot --skill vrcpilot-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about vrcpilot-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a real-resource-first testing strategy for automation adapters?▼

A real-resource-first testing strategy prioritizes actual filesystem I/O, subprocess behavior, loopback UDP, Xvfb/X11, and PipeWire audio fixtures over mocks to validate OS integration realistically for automation adapters.

How do I organize tests to mirror source code for pytest integration testing?▼

Enforce a strict 1:1 mirroring layout between the source directory and tests directory, categorizing tests into unit, integration-with-fakes, integration-real, and e2e taxonomies to ensure structural parity.

Can I mock third-party library surfaces when testing VRChat launch flows?▼

No, the strategy explicitly bans mocking third-party library surfaces and internal helper functions, allowing fakes only for project-owned ABCs to maintain strict integration-real guarantees for VRChat flows.

Does mutation testing work with integration-real and e2e test layouts?▼

Yes, mutation testing is integrated as a quality guardrail to detect weak coverage within integration-real and e2e layouts by avoiding trivial tests and requiring substring-based error assertions.

What are the environment constraints for e2e automation testing on Windows cp932?▼

Environment constraints for e2e automation testing require handling Windows cp932 quirks, utilizing Xvfb for X11, and configuring PipeWire null-sink for real audio capture verification across different OS integrations.