Test

Name: Test
Author: ahn-h-j

ahn-h-j/team-dashboard

1 installs
Updated March 23, 2026
ahn-h-j/team-dashboard

test is a Claude Code skill that selects and runs the right Gradle, npm, Vitest, or Playwright command for a team-dashboard project and reports the results.

About

test is a Claude Code skill that runs the test suite for a team-dashboard project with a Java/Gradle backend and a frontend using Vitest and Playwright. It decides which command to run based on the request (full backend, a specific class, frontend, a single file, E2E, or lint), executes it, and reports pass counts or a failure analysis. A developer uses it to run tests or verify changes without remembering each project-specific command.

Maps user test requests to the right Gradle, npm, Vitest, or Playwright command
Analyzes failures into failing test, cause, related code line, and fix suggestion
Documents the backend and frontend test directory layout

Test by the numbers

1 all-time installs (skills.sh)
Ranked #1,750 of 2,153 Testing & QA skills by installs in the Skillselion catalog
Data as of Jul 7, 2026 (Skillselion catalog sync)

At a glance

test capabilities & compatibility

Capabilities: run tests · test failure analysis · e2e testing · lint
Works with: playwright
Use cases: testing

From the docs

What test says it does

Use this skill when the user wants to run tests, execute test suite, check if tests pass, or verify code changes with tests.

SKILL.md

| 프론트엔드 특정 파일 | `cd frontend && npx vitest run {파일경로}` |

SKILL.md

npx skills add https://github.com/ahn-h-j/team-dashboard --skill test

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/ahn-h-j/team-dashboard/test.svg)](https://skillselion.com/skills/ahn-h-j/team-dashboard/test)

Installs	1
Last updated	March 23, 2026
Repository	ahn-h-j/team-dashboard ↗

What it does

Run the backend, frontend, or E2E test suite and report pass/fail analysis for a Gradle + Vitest project.

Who is it for?

Developers on this Gradle + Vitest + Playwright project who want the correct test command chosen automatically.

Skip if: Writing new tests; the skill runs and analyzes existing tests rather than authoring them.

When should I use this skill?

The user wants to run tests, execute the test suite, check if tests pass, or verify code changes with tests.

What you get

test results with pass counts or a failure analysis

By the numbers

7 request-to-command mappings
3-step run-and-analyze flow

Files

SKILL.mdMarkdownGitHub ↗

테스트 실행

$ARGUMENTS

Step 1: 실행 대상 결정

사용자 요청	명령어
백엔드 전체 / 지정 없음	`cd backend && gradle test`
클래스 지정	`cd backend && gradle test --tests "{클래스명}"`
패턴 지정	`cd backend && gradle test --tests "{패턴}"`
프론트엔드 전체	`cd frontend && npm run test`
프론트엔드 특정 파일	`cd frontend && npx vitest run {파일경로}`
E2E 테스트	`npx playwright test`
린트 검사	`cd frontend && npm run lint`

Step 2: 테스트 실행

해당 명령어 실행.

Step 3: 결과 분석

성공 시

테스트 통과: {n}개 테스트 성공

실패 시

아래 항목 분석 후 보고:

1. 실패 테스트: 클래스명.메서드명 2. 실패 원인: assertion 실패 / 예외 / 타임아웃 3. 관련 코드: {파일경로}:{라인번호} 4. 해결 방안: 코드 수정 제안 또는 테스트 수정 필요 여부

테스트 구조 참고

backend/src/test/java/com/teamdashboard/
├── domain/
│   ├── user/         # User 관련 테스트
│   ├── project/      # Project 관련 테스트
│   ├── task/         # Task 관련 테스트
│   └── comment/      # Comment 관련 테스트
└── ...

frontend/src/
├── components/__tests__/   # 컴포넌트 테스트
├── hooks/__tests__/        # 훅 테스트
└── ...

e2e/                        # Playwright E2E 테스트