test-runner

To automatically rerun relevant unit tests on file changes, you need a tool that maps edited source files to their corresponding test files and executes only those suites, skipping unrelated tests to shorten the edit-test feedback cycle.

The best way to run affected tests across these languages is to use smart test detection that identifies frameworks like jest, vitest, pytest, cargo test, and go test, then maps changed files to the correct runner automatically.

Yes, automatic test framework detection supports watch-style workflows and bail-on-failure behavior, providing quicker pass or fail signal by stopping execution upon the first test failure.

You map edited source files to their corresponding test files by applying changed-file-to-test mapping logic, which identifies the relationship between your code and tests to avoid running unrelated suites.

When no tests are found for the changed files, the test runner safely skips execution to avoid errors, ensuring the workflow continues without failing when explicitly disabled or lacking test coverage.