Maximize meaningful test coverage quickly, prioritizing testability over preserving existing structure. Be willing to refactor aggressively (within module boundaries) when it unlocks better, maintainable tests.

Prerequisites

A project with identifiable top-level modules or packages
Existing test runner available (e.g., cargo test, pytest, jest, go test)
Clean git working tree before starting

Step 0: Pre-flight Checks

Verify clean git state with git status --porcelain.
Identify the test runner and confirm tests currently pass.
Identify top-level modules/packages (e.g., src/*, services/*, libs/*, apps/*).

If the baseline test run fails, stop and report the failure before proceeding.

Step 1: Plan Module Coverage

Prerequisites

A project with identifiable top-level modules or packages
Existing test runner available (e.g., cargo test, pytest, jest, go test)
Clean git working tree before starting

Step 0: Pre-flight Checks

Verify clean git state with git status --porcelain.
Identify the test runner and confirm tests currently pass.
Identify top-level modules/packages (e.g., src/*, services/*, libs/*, apps/*).

If the baseline test run fails, stop and report the failure before proceeding.

Aggressive Testing

Prerequisites

Step 0: Pre-flight Checks

Step 1: Plan Module Coverage

Aggressive Testing

Prerequisites

Step 0: Pre-flight Checks

Step 1: Plan Module Coverage

Step 2: Per-Module Work (Run in Parallel per Module)

Aggressive Refactor Policy

Timebox and Abort Rules

Validation Discipline

Step 3: Per-Module Report

Step 4: Final Consolidated Summary

Constraints

Test

Feature Flags

Unit Tests

Integration Tests

Write Frontend Tests

Golang Testing