/testing--test-coverage

Runs a checklist before you ship, covering code quality, security, database and configuration, to catch problems before release.

Scans your code, config files and recent git history for API keys, tokens, passwords and private keys, and explains how to remediate each.

Runs your package manager's audit and lists each vulnerable dependency with its CVE, severity, fixed version and a remediation plan.

Audits your backend and frontend code for bottlenecks and lists each finding with its location, estimated impact and a specific fix.

Generates end-to-end tests for a user workflow in Playwright, Cypress or similar, covering happy path, error paths and data cleanup.

Generates tests for boundaries, nulls, concurrency, Unicode and state in your code, explaining which bug each one would catch.

Runs your test suite, works out whether each failure is in the test, the code or the environment, fixes it and re-runs to confirm.

Reads a file and writes unit tests covering normal use, edge cases and errors in your existing framework, then runs them to check they pass.

Generates integration tests that exercise real interactions between components, APIs and databases, including partial failures and retries.

Creates mocks, stubs, spies, fakes and realistic fixture data for your code's dependencies, following Jest, Vitest, pytest or Go conventions.