test

Execute unit and integration tests guided by TEST_STRATEGY.md and TEST.md.

2|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/ByeongminLee/nextjs-claude-code --skill test-byeongminlee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/ByeongminLee/nextjs-claude-code/tree/main/template/.claude/skills/test
Command: npx skills add https://github.com/ByeongminLee/nextjs-claude-code --skill test-byeongminlee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps run unit and integration tests for a new feature based on a defined test strategy (TEST_STRATEGY.md) and feature-level tests (TEST.md), coordinating planning, execution, and verification.

Core Features & Use Cases

  • Supports unit and integration test workflows guided by TEST_STRATEGY.md and TEST.md.
  • Allows configuring the test strategy with --setup.
  • Enables browser, visual, and accessibility testing via /qa when needed.

Quick Start

Define the feature to test and run the test workflow with the appropriate CLI commands.

Frequently Asked Questions about test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run unit and integration tests for a specific feature?

You can run unit and integration tests for a feature by using a strategy-driven plan guided by TEST_STRATEGY.md and feature-level TEST.md files, coordinating planning, execution, and verification across test scopes.

What is a strategy-driven test plan and how does it work?

A strategy-driven test plan uses TEST_STRATEGY.md and feature-level TEST.md files to guide and coordinate test planning, execution, and verification across unit, integration, and browser QA scopes.

Can I configure the test strategy for my project?

Yes, you can configure the test strategy by running the --setup command, which establishes the TEST_STRATEGY.md file to guide subsequent feature testing workflows.

How do I run browser, visual, and accessibility testing for a feature?

Browser, visual, and accessibility testing is executed via the /qa command, which coordinates routing and verification steps for browser QA scopes alongside unit and integration tests.

Do I need a defined test strategy before running feature tests?

Yes, this testing workflow applies to projects with a defined test strategy. You must establish the TEST_STRATEGY.md file first, either manually or by using the --setup command, before executing tests.

What are the limitations of using TEST_STRATEGY.md for test coordination?

This approach is limited to projects maintaining a defined test strategy and feature-level TEST.md files. Without these files configured, the workflow cannot route and verify test execution across scopes.