Individual skill

fec-testing-strategy

Use when planning or reviewing a frontend testing strategy, selecting the right test layer by risk, mapping coverage across static checks, unit tests, component tests, integration tests, E2E, Storybook/visual regression, a11y, security, performance, or CI gates. Do not use to write individual component/E2E tests or merely run existing validation commands; Chinese triggers include test strategy, test layering, test plan, coverage matrix.

skills/fec-testing-strategy/SKILL.md

Read pinned source

Source commit 5d44782572025045a552ff8945b354726eb5d183

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 23
Repository last updated: Nov 8, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
claude-code-plugin Repository topic
claude-code-skills Repository topic
e2e-tests Repository topic
fronend-development Repository topic
frontend-plugin Repository topic
frontend-project Repository topic
react Repository topic
typescript Repository topic
vue3 Repository topic
testing Derived category
design Derived category
security Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 4,065 bytes

Read excerpt


# Front-end testing strategy

## Purpose

Choose your testing approach by “closeness to code/level of risk coverage” to avoid cramming all risks into component tests or E2E.

## Procedure

1. Identify the type of change: pure logic, UI components, cross-module processes, browser capabilities, visual stability, dedicated quality risks, or release gates.
2. Establish a test level matrix, at least distinguish:
   - Static checking: TypeScript, ESLint, format, dependency security, build.
   - Unit testing: utils, hooks/composables, state logic, schema, pure functions.
   - Component testing: props/emits, user interaction, loading/error/empty, mock boundaries.
   - Lightweight integration testing: form + API mock + routing/Store/Provider context.