add-test

Add Test

Add an integration test for a specific tool in an existing collection. This skill creates a single test file following the collection's established test patterns.

Use this skill when:

• You added a new tool with /add-tool and want to test it separately
• You manually created or modified a tool and need a test
• You deleted a test and need to recreate it
• /build-tools-tests skipped the collection because tests already exist

Prerequisites

Before running, ensure:

1. The collection exists (src/umbraco-api/tools/{collection}/index.ts)
2. The test infrastructure exists (src/umbraco-api/tools/{collection}/__tests__/setup.ts) — if not, tell the user to run /build-tools-tests {collection} first
3. The project compiles: npm run compile
4. The Umbraco instance is running
5. An API user exists — remind the user: "You need to create an API user via the Umbraco backoffice UI: Settings > Users, with Client ID umbraco-back-office-mcp and Client Secret 1234567890"

Arguments

• Collection name (required): the collection containing the tool (e.g. /add-test form)
• Tool name (optional): the specific tool to test (e.g. /add-test form copy-form)

If no tool name is provided, compare the tools in the collection index against existing test files and present the untested tools to the user.

Agents

Agent	When to use
integration-test-creator	Creating the test file (Step 3)
integration-test-validator	Validating the test (Step 4)

Critical Rules

TEST INFRASTRUCTURE MUST EXIST. This skill does not create setup.ts, builders, or helpers. If they don't exist, tell the user to run /build-tools-tests {collection} first.

ONE FILE AT A TIME. Create one test file, compile, run, fix. Then move to the next if testing multiple tools.

RUN COMMANDS SEPARATELY. Always run compile and test as separate Bash calls. Never chain with &&.

REAL API — NO MOCKING. These are integration tests against a real Umbraco instance. Do NOT create mock infrastructure.