Skip to content
Skills Library
Programming · Testing

code-test-quality

/code-test-quality

Analyze test quality: smells, empty assertions, flaky patterns, coverage gaps. Use when tests are unreliable, coverage is misleading, or after major refactors.

Licence
MIT
Last repository change
24.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Analyze test quality: smells, empty assertions, flaky patterns, coverage gaps. Use when tests are unreliable, coverage is misleading, or after major refactors.

Arguments

/code-test-quality path to test directory or specific test file
Original author description

Analyze test quality: smells, empty assertions, flaky patterns, coverage gaps. Use when tests are unreliable, coverage is misleading, or after major refactors.

How it works

  1. When to Use This Skill
  2. Context
  3. Parameters
  4. Execution
  5. Post-Actions
  6. Agentic Optimizations
Original SKILL.md headings · 133 lines, 689 words
SKILL.md preview
---
name: code-test-quality
description: "Analyze test quality: smells, empty assertions, flaky patterns, coverage gaps. Use when tests are unreliable, coverage is misleading, or after major refactors."
args: "[PATH] [--focus <smells|coverage|flaky|all>]"
argument-hint: path to test directory or specific test file
allowed-tools: Bash(npx vitest *), Bash(npx jest *), Bash(pytest *), Bash(cargo test *), Read, Grep, Glob, TodoWrite
created: 2026-04-10
modified: 2026-05-09
reviewed: 2026-04-10
---

# /code:test-quality

Analyze test suite for quality issues and reliability.

## When to Use This Skill

| Use this skill when... | Use something else when... |
|---|---|
| Test suite passes but bugs still ship | Setting up test framework → /configure:tests |
| Coverage numbers are high but quality feels low | Setting up coverage thresholds → /configure:coverage |
| Tests are flaky or timing-dependent | Looking for code anti-patterns → /code:antipatterns |
| After major refactor, need test health check | Running tests → /test:run |

## Context

- Test files: !`find . -type f \( -name "*.test.*" -o -name "*.spec.*" -o -name "test_*.py" -o -name "*_test.py" -o -name "*_test.go" -o -name "*_test.rs" \) -not -path "*/node_modules/*"`
- Test config: !`find . -maxdepth 2 \( -name "vitest.config.*" -o -name "jest.config.*" -o -name "pytest.ini" -o -name "pyproject.toml" -o -name "conftest.py" \) -type f`

## Parameters

- `$1`: Path to analyze (defaults to current directory)
- `--focus`: Analysis focus — `smells` (default), `coverage`, `flaky`, or `all`

## Execution

Execute this test quality analysis:

### Step 1: Discover test suite

Scan the target path for test files. Categorize by:
- Unit tests
- Integration tests
- E2E tests
Count total test files and estimate test-to-source ratio.

### Step 2: Detect test smells

Scan test files for these anti-patterns:

**Empty tests (Critical):**
- Test bodies with no assertions
- Tests that only call the function without checking results
- `expect()` or `assert` never called

**Weak assertions (High):**
- `expect(result).toBeTruthy()` on objects (always passes)
- `assert result` without specific value checks
- `assertEqual(len(result), len(result))` (tautologies)
- Snapshot tests without meaningful structure checks

**Test duplication (Medium):**
- Copy-pasted test bodies with minor variations
- Same setup/teardown repeated across many tests
- Missing parameterized/table-driven patterns

**Missing edge cases (Medium):**
- No tests for error paths
- No tests for empty/null/undefined inputs
- No boundary value tests
- No tests for concurrent access (where applicable)

**Flaky patterns (High):**
- `setTimeout` / `sleep` in tests
- Hardcoded ports or file paths
- Date/time-dependent assertions without mocking
- Tests depending on external services without mocks
- Non-deterministic ordering assumptions

**Overly broad mocks (Medium):**
- Mocking implementation details instead of interfaces
- Mock that returns the expected value (circular logic)
- Tests that pass even when implementation is deleted

### Step 3: Analyze coverage quality (if --focus coverage or all)

If coverage data is available:
1. Identify files with 0% coverage
2. Find files with high line coverage but low branch coverage
3. Detect "coverage padding" — tests that execute code but don't assert behavior
4. Identify critical paths without coverage (error handlers, auth, data validation)

### Step 4: Report findings

Print categorized results:

```
Test Quality Report
===================
Test files: N
Test-to-source ratio: N:1

Smells Found:
  Critical: N (empty tests, no assertions)
  High: N (weak assertions, flaky patterns)
  Medium: N (duplication, missing edge cases)
  Low: N (style issues)

Top Issues:
1. [file:line] Empty test - "should handle X" has no assertions
2. [file:line] Flaky - uses setTimeout(500) instead of async await
3. [file:line] Weak assertion - toBeTruthy on object (always passes)

Recommendations:
- Add assertions to N empty tests
- Replace N setTimeout calls with proper async patterns
- Add error path tests for N untested handlers
```

### Step 5: Suggest improvements

For each finding, provide specific fix guidance:
- Empty test → show what assertion to add
- Flaky pattern → show the async/mock alternative
- Missing edge case → suggest specific test cases

## Post-Actions

- If test framework not configured → suggest `/configure:tests`
- If coverage not set up → suggest `/configure:coverage`
- If many smells found → suggest fixing critical ones first
- If good quality → report health score and suggest maintaining it

## Agentic Optimizations

| Context | Command |
|---|---|
| Find empty tests (JS) | `grep -rn "it\|test" --include="*.test.*" -l` then check for assertions |
| Find sleeps in tests | `grep -rn "setTimeout\|sleep\|time.sleep" --include="*.test.*"` |
| Coverage report (Vitest) | `npx vitest run --coverage --reporter=json` |
| Coverage report (pytest) | `pytest --cov --cov-report=json` |
| Quick smell scan | Grep for assertion-free test bodies |

Versions

The database has no other skills named code-test-quality.

Database snapshot: 13.11.2026 · package version 66a746c27652 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100test-quality-analysis
    Analyze test code quality to detect coverage-only tests, test smells, and low-value assertions. Use when asked to \"analyze test quality\", \"find coverage-only tests\", \"audit our tests\", \"are these tests valuable\", \"find test smells\", or \"which tests should we delete\".…
  • 100test-quality-analysis
    Detect test smells, overmocking, flaky tests, coverage gaps, and tests that touch the real HOME or git config. Use when reviewing tests or analyzing test effectiveness and reliability.
  • 100test-quality-analysis
    Detect test smells, overmocking, flaky tests, and coverage issues. Analyze test effectiveness, maintainability, and reliability. Use when reviewing tests or improving test quality.
  • 100evaluate-pester-test-development
    Evaluate Pester test quality — analyze code coverage gaps, check mock completeness, detect flaky tests, verify test isolation, measure execution time, generate coverage reports. Use when: evaluate tests, check coverage, find gaps, test quality, flaky tests, coverage report,…
  • 100coverage
    Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".
  • 90proof-audit
    Audit test suite health — find flaky tests, slow tests, coverage gaps, and testing anti-patterns. Use when asked to "audit tests", "fix flaky tests", "why are tests slow", "test health", or "improve test suite".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.