# Tenzir Test v1.2.1

This patch release improves the `-m`/`--match` flag with automatic substring matching and centralizes skip handling in the engine for more consistent test reporting.

## 🔧 Changes

### Simpler substring matching for -m/—match flag

Feb 6, 2026 · [@mavam](https://github.com/mavam), [@claude](https://github.com/claude) · [#16](https://github.com/tenzir/test/pull/16)

The `-m`/`--match` flag now treats bare strings as substring matches automatically.

Previously, you had to use glob syntax like `tenzir-test -m '*mysql*'` to match tests by name. Now you can write `tenzir-test -m mysql` and it automatically matches any test path containing “mysql”. This makes the common case of substring matching simpler and more intuitive.

Patterns that contain glob metacharacters (`*`, `?`, `[`) still use fnmatch syntax as before, so existing patterns with wildcards continue to work exactly as they did. This change is fully backwards-compatible.

### Centralize skip-handling logic in engine

Feb 6, 2026 · [@mavam](https://github.com/mavam), [@claude](https://github.com/claude) · [#15](https://github.com/tenzir/test/pull/15)

Skip handling now lives in the engine instead of individual runners. Skipped tests are recorded consistently in summary stats regardless of which runner executes them, so skip counts and paths in the test report are always accurate.

Previously, each runner duplicated the same skip-config parsing, which could lead to inconsistent skip tracking. Custom runners no longer need to implement skip logic because the engine evaluates the `skip` configuration before dispatching to any runner.

[ Download on GitHub ](https://github.com/tenzir/test/releases/tag/v1.2.1)

[Get the release artifacts and source code.](https://github.com/tenzir/test/releases/tag/v1.2.1)