Stats
Actions
Tags
From dev-squad
Use when running backend tests - executes gradle test with optional test class filter
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-squad:testThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
테스트를 실행해줘.
테스트를 실행해줘.
.claude/project-config.json을 읽어서 대상 디렉토리와 type을 확인해줘.
파일이 없으면 /start-work를 먼저 실행하라고 안내해줘.
| type | 기본 명령어 | 필터 명령어 |
|---|---|---|
spring-boot (gradle) | ./gradlew test | ./gradlew test --tests "{filter}" |
spring-boot (maven) | ./mvnw test | ./mvnw test -Dtest="{filter}" |
nuxt / nextjs / vite / node | npm run test:unit | npm run test:unit -- {filter} |
go | go test ./... | go test ./... -run "{filter}" |
rust | cargo test | cargo test {filter} |
| 기타 | AskUserQuestion으로 테스트 명령어 확인 | - |
$ARGUMENTS)가 있으면 해당 디렉토리의 type에 맞는 필터 명령어 사용인자: $ARGUMENTS
npx claudepluginhub leoheo/dev-squad --plugin dev-squadRuns the test suite via npm test and reports results concisely. Useful for executing tests without modifying them.
Defines test types (unit, integration, component, end-to-end), source sets, execution commands, and JUnit 5 structure for Java Gradle projects. Useful for TDD and test running tasks.
Runs tests with minimal scope: targeted file-first, full suite only when needed. Saves verbose logs and summarizes failures for fast debugging.