test-coverage

Test Coverage Fix

Fix test coverage for $ARGUMENTS (or the whole app if no argument is given). This skill enforces the 80% line coverage hard gate required for Flows app approval by finding AND fixing coverage gaps. Work through every step in order.

---

Step 1 — Verify test framework and coverage tooling

Check that the project has a working test framework with coverage configured:

# Check for vitest or jest in package.json
grep -E "(vitest|jest)" package.json

# Check for coverage configuration
cat vitest.config.ts 2>/dev/null || cat vitest.config.js 2>/dev/null || cat jest.config.ts 2>/dev/null || cat jest.config.js 2>/dev/null

Verify:

• A test framework (Vitest or Jest) is installed and configured
• The config file has a coverage section (e.g. coverage: { provider: 'v8', ... } in vitest.config.ts)
• A coverage reporter is configured (at least text and lcov or json-summary)

If coverage tooling is not configured, fix it now:

1. Install the coverage provider:

pnpm add -D @vitest/coverage-v8

1. Add the coverage configuration to vitest.config.ts. Read the existing config file, then add the coverage section inside test:

// vitest.config.ts — minimum coverage configuration to add
test: {
  coverage: {
    provider: 'v8',
    reporter: ['text', 'text-summary', 'lcov'],
    include: ['src/**/*.{ts,tsx}'],
    exclude: [
      'src/**/*.test.{ts,tsx}',
      'src/**/*.spec.{ts,tsx}',
      'src/**/vite-env.d.ts',
      'src/main.tsx',
    ],
  },
}

Write the updated config file. If no vitest.config.ts exists at all, create one with the full defineConfig wrapper.

---

Step 2 — Validate coverage scope

The 80% threshold applies to all .ts and .tsx files under src/, excluding only:

• Test files (*.test.ts, *.test.tsx, *.spec.ts, *.spec.tsx)
• Type declaration files (vite-env.d.ts)
• The entry point (main.tsx)

Apps must not exclude pages, components, hooks, or other production code from coverage measurement.