MCP.so
Sign In
Testingevent

Post-Edit Test Guard

Hook-based loop that runs related tests after file edits to catch regressions early.

Kickoff prompt

Install and run the "Post-Edit Test Guard" loop.

Goal: after each batch of file edits, related tests must pass before continuing.
Between iterations run: npm test -- --findRelatedTests <edited files>
Exit when: related tests exit 0.

Step 1: After edits, run related tests. If they fail, fix before making more changes.

Basic information

Category

Testing

Goal

after each batch of file edits, related tests must pass before continuing.

Check command

npm test -- --findRelatedTests <edited files>

Exit when

related tests exit 0.

Supported agents

Cursor

Steps

  1. 1

    Detect edited files

    Identify which source files were edited in the last turn.

  2. 2

    Run related tests

    Run the smallest relevant test subset for edited files. Fix failures before continuing.

    npm test -- --findRelatedTests

More Testing loops

Testing

Build Until Green

Run the production build, fix compile and bundling errors, and loop until the build succeeds.

Testing

Coverage Until Threshold

Add focused tests until coverage meets your threshold (e.g. 80%), without changing production behavior unnecessarily.

Testing

Pre-Commit Guard

Hook that runs tests before git commit commands to block commits when the suite is red.

Testing

Format Until Clean

Run the formatter, fix any remaining style issues, and loop until the codebase formats cleanly with no diffs.

Testing

Flaky Test Triage

Run failing tests repeatedly, classify each failure as flaky or real, and fix only confirmed regressions.

Testing

Autoloop TDD

Test-first loop: write a failing test, implement the minimum code to pass, refactor, and repeat.