🎯

s-test

🎯Skill

from falkicon/mechanic

VibeIndex|
What it does

Guides WoW addon developers in writing comprehensive unit tests using Busted, mocking WoW APIs, and analyzing test coverage.

πŸ“¦

Part of

falkicon/mechanic(15 items)

s-test

Installation

pip installInstall Python package
pip install -e .
πŸ“– Extracted from docs: falkicon/mechanic
1Installs
-
AddedFeb 4, 2026

Skill Details

SKILL.md

>

Overview

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

```