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

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Credits and license

“jev-test-filter” by mizchi. Read the original source.

This expanded guide is an AI-narrated adaptation of the source’s essential explanation, examples and caveats, not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

License: MIT

MIT License

Copyright (c) 2026 mizchi

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

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

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

More guides →See the experiments →