frontmcp-testing

name	frontmcp-testing
description	Use for anything about testing FrontMCP servers: writing or running unit, integration, and E2E tests and reaching the 95%+ coverage bar. Covers Jest setup and coverage gating; unit-testing a ToolContext execute() with mock context, inputs, and Zod schema validation; testing resources and prompts; in-memory testing via create() and connectOpenAI / connectClaude (no HTTP); full MCP-protocol E2E over HTTP with McpTestClient and TestServer; authenticated tests with TestTokenFactory, MockOAuthServer, and role-based access; browser-bundle validation with Playwright; and CLI-binary / SEA startup tests. Triggers: write tests, run tests, add e2e tests, improve coverage, test a tool / resource / prompt, mock auth, jest config. The skill for ALL testing needs.
when_to_use	Trigger when writing or running tests for a FrontMCP server: editing a *.spec.ts / *.e2e.spec.ts file or a jest config, setting up Jest or coverage gating, unit-testing a ToolContext execute(), writing MCP-protocol E2E tests with McpTestClient / TestServer, testing auth with TestTokenFactory / MockOAuthServer, validating a browser bundle with Playwright, or testing a CLI / SEA binary.
paths	**/*.spec.ts, **/*.e2e.spec.ts, **/jest.config.*, **/jest.e2e.config.*
tags	["router","testing","jest","e2e","coverage","quality","guide"]
category	testing
targets	["all"]
bundle	["recommended","full"]
priority	10
visibility	both
license	Apache-2.0
metadata	{"docs":"https://docs.agentfront.dev/frontmcp/testing/overview"}

FrontMCP Testing Router

Entry point for testing FrontMCP applications. This skill helps you navigate testing strategies across component types and find the right patterns for unit, integration, and E2E tests.

When to Use This Skill

Must Use

• Setting up testing infrastructure for a new FrontMCP project
• Deciding how to test a specific component type (tool, resource, prompt, agent)
• Planning a testing strategy that covers unit, E2E, and coverage requirements

Recommended

• Looking up testing patterns for a component type you haven't tested before
• Understanding the relationship between unit tests, E2E tests, and coverage thresholds
• Troubleshooting test failures or coverage gaps

Skip When

• You need detailed Jest configuration and test harness setup (go directly to setup-testing)
• You need to build components, not test them (see frontmcp-development)
• You need to deploy, not test (see frontmcp-deployment)

Decision: Use this skill for testing strategy and routing. Open the setup-testing reference under references/ for hands-on Jest configuration and test writing.

Prerequisites

• A FrontMCP project with at least one component to test (see frontmcp-development).
• Jest installed and configured — if not, start with setup-testing before opening any other testing skill.
• The component itself implemented and exported; tests reach decorated classes through the SDK, not by importing internal builders.

Steps

This is a router skill. Follow this order to pick a testing approach, then move to the target reference under references/.

1. Pick the test layer — unit (fastest, mock DI), integration (real DI scope), or E2E (real MCP client + server). Use the Testing Strategy table below.
2. Pick the component flavour — tool / resource / prompt / agent / job — each has a distinct recipe.
3. Pick the runtime concern — auth, browser/CLI build, direct vs streamable transport — and add the matching reference to your reading list.
4. Open the target reference (e.g. references/test-tool-unit.md, references/test-e2e-handler.md, references/test-auth.md) and follow its Steps section.