frontend-testing

Name: frontend-testing - Agent Skill
Rating: 5.0 (126934 reviews)
Author: langgenius

126,934

Use when writing or changing Vitest or React Testing Library tests under `web/` or `packages/dify-ui/`, or when the user explicitly requests frontend test strategy, including evaluation of an existing strategy. Do not use for frontend code-review-only requests, general testability discussion, Python tests, or Cucumber/Playwright E2E.

Download Folder View on GitHub

CLI Install

Recommended

Use the skills CLI to install this skill with one command. Auto-detects all installed AI assistants.

Method 1 - skills CLI

npx skills i langgenius/dify/.agents/skills/frontend-testing

Method 2 - openskills (supports sync & update)

npx openskills install langgenius/dify

Auto-detects Claude Code, Cursor, Codex CLI, Gemini CLI, and more. One install, works everywhere.

Installation Path

Download and extract to one of the following locations:

~/.claude/skills/frontend-testing/

SKILL.md

Skill Instructions

Back

Run with Cloud Agent

No setup needed. Let our cloud agents run this skill for you.

Select Provider

Select Model

Claude Sonnet 4.5

$0.20/task

Best for coding tasks

No setup required

Frontend Testing

web/docs/test.md is the single policy owner. Read it before changing frontend tests; this skill adds no separate requirements.

Identify the observable contract and regression risk.
Choose the smallest boundary that includes the behavior owner.
Establish the failing case first when practical, then implement one coherent scenario.
Run the focused spec before the affected suite and relevant static checks.
Report the behavior verified and any remaining browser, visual, or end-to-end risk.

Recommend deleting low-value tests as readily as adding missing behavior coverage. Use web/docs/test.md for policy and Web commands; use packages/dify-ui/docs/testing.md for Dify UI commands.