How do I install the S Test skill?

Run npx skillmds add majiayu000/s-test in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is S Test safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with S Test?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is S Test free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published S Test?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

S Test by majiayu000 — Agent Skill

Name: S Test
Rating: 4.2 (5 reviews)
Author: majiayu000

S Test

Write and run unit tests for WoW addons using Busted and the Mechanic test framework. Covers test structure, mocking WoW APIs, and coverage analysis. Use when adding tests, fixing bugs with regression tests, or improving coverage. Triggers: test, unit test, coverage, Busted, mock, TDD, sandbox.

majiayu000 da69064 2 files · 2.7 KB Updated Sep 9, 2026 567 repo stars

File contents

Testing WoW Addons

Expert guidance for testing WoW addons using Sandbox, Desktop, and In-Game methods.

Related Commands

c-test - Run unit tests workflow
c-review - Full code review (includes test step)

CLI Commands (Use These First)

MANDATORY: Always use CLI commands before manual exploration.

Task	Command
Generate Stubs	`mech call sandbox.generate`
Run Sandbox Tests	`mech call sandbox.test -i '{"addon": "MyAddon"}'`
Run Busted Tests	`mech call addon.test -i '{"addon": "MyAddon"}'`
Test Coverage	`mech call addon.test -i '{"addon": "MyAddon", "coverage": true}'`
Sandbox Status	`mech call sandbox.status`

Capabilities

Sandbox Testing — Fast, offline tests using generated WoW API stubs
Desktop Testing (Busted) — Integration tests with custom mocks
In-Game Testing — Runtime verification via MechanicLib registration
Coverage Analysis — Identify untested code paths

Routing Logic

Request type	Load reference
Sandbox, Busted, In-Game guides	../../docs/integration/testing.md
Busted spec patterns	references/busted-patterns.md
Mocking WoW APIs	references/wow-mocking.md
MechanicLib test registration	../../docs/integration/mechaniclib.md

Quick Reference

Recommended Workflow

Sandbox (Core): Fast feedback for business logic.
Desktop (Integration): Test interactions between modules.
In-Game (Verification): Final check against live APIs.

Example Sandbox Test

describe("MyAddon Core", function()
    it("calculates values correctly", function()
        local result = Core.Calculate(10, 20)
        assert.equals(30, result)
    end)
end)

Running Tests

# Generate stubs once
mech call sandbox.generate

# Run tests frequently
mech call sandbox.test -i '{"addon": "MyAddon"}'

---name: s-testdescription: Write and run unit tests for WoW addons using Busted and the Mechanic test framework. Covers test structure, mocking WoW APIs, and coverage analysis. Use when adding tests, fixing bugs with regression tests, or improving coverage. Triggers: test, unit test, coverage, Busted, mock, TDD, sandbox.--- # Testing WoW Addons Expert guidance for testing WoW addons using Sandbox, Desktop, and In-Game methods. ## Related Commands - [c-test](../../commands/c-test.md) - Run unit tests workflow - [c-review](../../commands/c-review.md) - Full code review (includes test step) ## CLI Commands (Use These First) > **MANDATORY**: Always use CLI commands before manual exploration. | Task | Command | |------|---------| | Generate Stubs | `mech call sandbox.generate` | | Run Sandbox Tests | `mech call sandbox.test -i '{"addon": "MyAddon"}'` | | Run Busted Tests | `mech call addon.test -i '{"addon": "MyAddon"}'` | | Test Coverage | `mech call addon.test -i '{"addon": "MyAddon", "coverage": true}'` | | Sandbox Status | `mech call sandbox.status` | ## Capabilities 1. **Sandbox Testing** — Fast, offline tests using generated WoW API stubs 2. **Desktop Testing (Busted)** — Integration tests with custom mocks 3. **In-Game Testing** — Runtime verification via MechanicLib registration 4. **Coverage Analysis** — Identify untested code paths ## Routing Logic | Request type | Load reference | |--------------|----------------| | Sandbox, Busted, In-Game guides | [../../docs/integration/testing.md](../../docs/integration/testing.md) | | Busted spec patterns | [references/busted-patterns.md](references/busted-patterns.md) | | Mocking WoW APIs | [references/wow-mocking.md](references/wow-mocking.md) | | MechanicLib test registration | [../../docs/integration/mechaniclib.md](../../docs/integration/mechaniclib.md) | ## Quick Reference ### Recommended Workflow 1. **Sandbox (Core)**: Fast feedback for business logic. 2. **Desktop (Integration)**: Test interactions between modules. 3. **In-Game (Verification)**: Final check against live APIs. ### Example Sandbox Test ```lua describe("MyAddon Core", function() it("calculates values correctly", function() local result = Core.Calculate(10, 20) assert.equals(30, result) end) end) ``` ### Running Tests ```bash # Generate stubs once mech call sandbox.generate # Run tests frequently mech call sandbox.test -i '{"addon": "MyAddon"}' ```

Frequently asked questions