smithery/falkicon

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.

Installation

$ npx skills add smithery/falkicon --skill s-test

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/falkicon · top by installs.

npx skills add smithery/falkicon

Browse all from smithery/falkicon

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,468 B
  • docs SUMMARY.md 309 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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

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"}'