Skip to content

rsicarelli/fakt / .claude/skills/bdd-test-runner

bdd-test-runner

Verified

Runs BDD-compliant GIVEN-WHEN-THEN tests, validates naming compliance, and analyzes coverage. Use when running tests, checking BDD compliance, validating test patterns, or verifying that test names follow GIVEN-WHEN-THEN conventions. Make sure to use this skill whenever tests need to be executed — it validates naming compliance and catches convention violations that plain test runners miss.

FileKindSize
SKILL.mdskill md3.6 KB
---
name: bdd-test-runner
description: Runs BDD-compliant GIVEN-WHEN-THEN tests, validates naming compliance, and analyzes coverage. Use when running tests, checking BDD compliance, validating test patterns, or verifying that test names follow GIVEN-WHEN-THEN conventions. Make sure to use this skill whenever tests need to be executed — it validates naming compliance and catches convention violations that plain test runners miss.
allowed-tools: Read, Bash, Grep, Glob, TaskCreate, TaskUpdate
---

# BDD Test Runner & Compliance Validator

Executes GIVEN-WHEN-THEN tests with compliance validation and coverage analysis.

## Instructions

### 1. Understand Test Request

**Common requests:**
- "Run all tests" → `./gradlew test`
- "Run compiler tests" → `./gradlew :compiler:test`
- "Run specific tests" → `./gradlew :compiler:test --tests "*Pattern*"`
- "Validate test naming" → BDD compliance check only
- "Check coverage" → Coverage analysis

### 2. Pre-Execution BDD Compliance Check

Unit tests live in `compiler/`, `codegen-runtime/`, `gradle-plugin/`, `compiler-api/` and `build-logic/` (`src/test/kotlin`); sample tests live under `samples/*/src/*Test/`.

```bash
TEST_DIRS="compiler/src/test codegen-runtime/src/test gradle-plugin/src/test compiler-api/src/test build-logic/src/test"

# Count GIVEN-WHEN-THEN tests
grep -rh "fun \`GIVEN" $TEST_DIRS | wc -l

# Forbidden "should" naming — expect zero matches
grep -rn "fun \`should" $TEST_DIRS
```

**Compliance checklist:**
- [ ] All test methods use GIVEN-WHEN-THEN naming (uppercase)
- [ ] No "should" pattern (forbidden)
- [ ] All classes have `@TestInstance(TestInstance.Lifecycle.PER_CLASS)`
- [ ] Vanilla assertions only (no custom matchers)
- [ ] No mocks (use fakes)

**If violations found — report and do not proceed until acknowledged:**
```
BDD COMPLIANCE VIOLATION

Found {count} tests using "should" pattern (forbidden)
Files: {list}
Reference: .claude/docs/development/validation/testing-guidelines.md
```

### 3. Execute Tests

```bash
# All tests (from the repository root)
./gradlew test

# One module (:compiler, :codegen-runtime, :gradle-plugin, :compiler-api)
./gradlew :codegen-runtime:test

# Pattern-based
./gradlew :compiler:test --tests "*{Pattern}*"

# Samples (built against the published plugin)
make publish-local && make test-sample
```

### 4. Analyze Results

**Parse output:** total run, passed, failed, skipped, execution time.

**If failures:** categorize each failure and suggest relevant skills:
- Compilation errors → `compilation` skill
- Test logic errors → fix test or implementation
- Missing imports → check generated code

### 5. Coverage Analysis

List source files with no matching `*Test.kt` in the module you changed (a heuristic — some classes are covered through other tests):

```bash
MODULE=codegen-runtime   # or compiler, gradle-plugin, compiler-api
find $MODULE/src/main/kotlin -name "*.kt" | while read file; do
    testFile="${file/src\/main/src\/test}"
    testFile="${testFile/.kt/Test.kt}"
    if [ ! -f "$testFile" ]; then
        echo "Missing tests for: $file"
    fi
done
```

### 6. Report

```
BDD TEST EXECUTION REPORT

Compliance: {PASSED/FAILED}
- GIVEN-WHEN-THEN naming: {count}/{total} ✅
- "should" violations: {count}

Execution:
- Total: {n} | Passed: {n} | Failed: {n} | Skipped: {n}
- Time: {duration}

Coverage:
- Implementation files: {n} | Test files: {n}
- Coverage gaps: {list if any}
```

**Follow-up suggestions:**
- If coverage gaps → offer to write GIVEN-WHEN-THEN tests for them
- If failures → suggest fixes or relevant skills

## Related Skills

- **`compilation`** — Validate code compiles
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall