# Tenzir Test v0.13.0

This release adds `--package-dirs` support and improves startup diagnostics.

## 🚀 Features

### Library mode and extra packages

Dec 2, 2025 · [@codex](https://github.com/codex), [@mavam](https://github.com/mavam) · [#4](https://github.com/tenzir/test/pull/4)

Explicit package loading for tests: use `--package-dirs` (repeatable, accepts comma-separated lists) to point the harness at package directories. The same flag is passed to the Tenzir binaries, and it merges with any `package-dirs:` declared in directory `test.yaml` files. Entries are normalized and de-duplicated, then exported via `TENZIR_PACKAGE_DIRS` for fixtures.

The test configuration uses the same spelling: add

```yaml
package-dirs:
  - ../shared-packages
  - /opt/tenzir/packages/foo
```

to a directory `test.yaml` when you want those packages available for the tests below it.

Example: `uvx tenzir-test --package-dirs example-library example-library` loads both `foo` and `bar` packages so their operators can cross-import. The example-library `test.yaml` files demonstrate the config-based approach if you prefer not to pass the `--package-dirs` flag.

## 🔧 Changes

### Improve diagnostics when Tenzir Node fails to start

Dec 2, 2025 · [@Alainx277](https://github.com/Alainx277), [@claude](https://github.com/claude) · [#2](https://github.com/tenzir/test/pull/2)

The `node` fixture now reports the exit code and stderr output when `tenzir-node` fails to start, making it easier to diagnose startup failures. Previously, the error message provided no context about why the node failed to produce an endpoint.

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

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