s-test_skill

Overview

This skill helps you write and run unit tests for World of Warcraft addons using Busted and the Mechanic test framework. It covers test structure, mocking WoW APIs, running sandbox and in-game tests, and performing coverage analysis. Use it to add tests, prevent regressions, and improve code quality and coverage.

How this skill works

The skill guides you through a recommended workflow: generate API stubs, run fast sandbox tests, run desktop Busted integration tests with mocks, then verify in-game via MechanicLib registration. It explains how to mock WoW globals and APIs, structure Busted specs, and gather coverage reports. CLI commands are emphasized for reproducible automation and repeatable results.

When to use it

• When adding unit or integration tests for a new feature
• When fixing bugs and writing regression tests
• When you need to mock WoW APIs for offline testing
• When increasing test coverage and identifying untested code paths
• Before releasing changes that touch core logic or addon APIs

Best practices

• Generate WoW API stubs once and keep them updated to avoid false negatives
• Start with sandbox tests for fast feedback, then add desktop and in-game tests for integration and runtime checks
• Mock only external WoW or addon boundaries; keep business logic pure and easy to test
• Use clear Busted describe/it structure and name tests for behavior, not implementation
• Run coverage analysis regularly and add tests for critical untested paths

Example use cases

• Write a sandbox test to validate core calculation functions without WoW dependencies
• Use Busted with custom mocks to test module interactions and event handling
• Register MechanicLib tests to run quick in-game verification for API-dependent behavior
• Add a regression test when fixing a bug to prevent reintroduction
• Run coverage reports to prioritize tests for high-risk code paths