JevMade

Sign in
← Back to guides

JevMade field notes / Technical guide

Select tests from a Git change

jev-test-filter asks which tests a code change may affect. It always includes changed tests, includes uncertain cases, and can fall back to running everything when selective testing is unsupported.

Original by mizchiEvaluation
Bookmark: Select tests from a Git change Keep this in your collection.
Leave a noteWhat would you try with this? : Select tests from a Git change

Only you can see your notes.

Listen to this guide

JevMade’s plain-English explanation

0:00 /

Our summary

A code project may have many automated tests, making every small edit slow to check. jev-test-filter compares a Git change with the tests known to the normal test runner. It suggests which tests to run, without replacing the testing framework itself.

Tests directly changed by the edit run without a model decision. Uncertain selections also run. Detailed output records each score and selection reason, while separate outcomes distinguish no selected tests from bad input or failure. Unsupported situations can use a full test run instead.

A selected set is not proof that all affected behaviour is covered. Missing context may hide a relevant test, so keep the full suite for release checks. The guide also warns that copying its generated command arguments incorrectly can change how they are interpreted.

Key takeaways

  1. Always include tests directly changed by the edit.
  2. Run uncertain cases rather than skipping them.
  3. Keep full testing for releases and unsupported changes.

The repository's example selection is source-reported.

GitHub README

Read the original guide Opens the author’s site in a new tab.

Your note

Only you can see this. Clear the text and save to remove it.

Keep what you save

Sign in to keep bookmarks and private notes on every device. We email you a link; there is no password, and the same link creates your account.