tenzir-test 0.15.0__tar.gz

tenzir_test-0.15.0/.gitignore

@@ -0,0 +1,43 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# Distribution / packaging
+.build/
+build/
+dist/
+*.egg-info/
+.eggs/
+
+# Virtual environments
+.venv/
+.python-env/
+
+# uv artifacts
+.uv/
+uv.lock.bak
+
+# Coverage reports
+htmlcov/
+.coverage
+coverage.xml
+*.py,cover
+*.profraw
+
+# Test / pytest cache
+.pytest_cache/
+
+# Mypy / Ruff / other tooling caches
+.mypy_cache/
+.ruff_cache/
+
+# Editor junk
+*.swp
+*.swo
+.DS_Store
+.vscode/
+.idea/
+
+# Documentation (separate repository)
+.docs/

tenzir_test-0.15.0/LICENSE

@@ -0,0 +1,190 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2024 Tenzir
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

tenzir_test-0.15.0/PKG-INFO

@@ -0,0 +1,81 @@
+Metadata-Version: 2.4
+Name: tenzir-test
+Version: 0.15.0
+Summary: Reusable test execution framework extracted from the Tenzir repository.
+Project-URL: Homepage, https://github.com/tenzir/test
+Project-URL: Repository, https://github.com/tenzir/test
+Project-URL: Bug Tracker, https://github.com/tenzir/test/issues
+Project-URL: Documentation, https://docs.tenzir.com
+Author-email: Tenzir <engineering@tenzir.com>
+Maintainer-email: Tenzir Engineering <engineering@tenzir.com>
+License: Apache-2.0
+License-File: LICENSE
+Keywords: automation,pytest,tenzir,testing
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Software Development :: Testing
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Requires-Dist: click>=8.1
+Requires-Dist: pyyaml>=6.0
+Description-Content-Type: text/markdown
+
+# 🧪 tenzir-test
+
+`tenzir-test` is the reusable test harness that powers the
+[Tenzir](https://github.com/tenzir/tenzir) project. It discovers test scenarios
+and Python fixtures, prepares the execution environment, and produces artifacts
+you can diff against established baselines.
+
+## ✨ Highlights
+
+- 🔍 Auto-discovers tests, inputs, and configuration across both project and
+  package layouts, including linked satellite projects.
+- 🧩 Supports configurable runners and reusable fixtures so you can tailor how
+  scenarios execute and share setup logic.
+- 🛠️ Provides a `tenzir-test` CLI for orchestrating suites, updating baselines,
+  and inspecting artifacts.
+
+## 📦 Installation
+
+Install the latest release from PyPI with `uvx`—`tenzir-test` requires Python
+3.12 or newer:
+
+```sh
+uvx tenzir-test --help
+```
+
+`uvx` downloads the newest compatible release, runs it in an isolated
+environment, and caches subsequent invocations for fast reuse.
+
+## 📚 Documentation
+
+Consult our [user guide](https://docs.tenzir.com/guides/testing/write-tests)
+for an end-to-end walkthrough of writing tests.
+
+We also provide a dense [reference](https://docs.tenzir.com/reference/test) that
+explains concepts, configuration, multi-project execution, and CLI details.
+
+## 🗞️ Releases
+
+New versions are published to PyPI through trusted publishing when a GitHub
+release is created. Review the latest release notes on GitHub for details about
+what's new.
+
+## 🤝 Contributing
+
+Want to contribute? We're all-in on agentic coding with [Claude
+Code](https://claude.ai/code)! The repo comes pre-configured with our [custom
+plugins](https://github.com/tenzir/claude-plugins)—just clone and start hacking.
+
+## 📜 License
+
+`tenzir-test` is available under the Apache License, Version 2.0. See
+[`LICENSE`](LICENSE) for details.

tenzir_test-0.15.0/README.md

@@ -0,0 +1,52 @@
+# 🧪 tenzir-test
+
+`tenzir-test` is the reusable test harness that powers the
+[Tenzir](https://github.com/tenzir/tenzir) project. It discovers test scenarios
+and Python fixtures, prepares the execution environment, and produces artifacts
+you can diff against established baselines.
+
+## ✨ Highlights
+
+- 🔍 Auto-discovers tests, inputs, and configuration across both project and
+  package layouts, including linked satellite projects.
+- 🧩 Supports configurable runners and reusable fixtures so you can tailor how
+  scenarios execute and share setup logic.
+- 🛠️ Provides a `tenzir-test` CLI for orchestrating suites, updating baselines,
+  and inspecting artifacts.
+
+## 📦 Installation
+
+Install the latest release from PyPI with `uvx`—`tenzir-test` requires Python
+3.12 or newer:
+
+```sh
+uvx tenzir-test --help
+```
+
+`uvx` downloads the newest compatible release, runs it in an isolated
+environment, and caches subsequent invocations for fast reuse.
+
+## 📚 Documentation
+
+Consult our [user guide](https://docs.tenzir.com/guides/testing/write-tests)
+for an end-to-end walkthrough of writing tests.
+
+We also provide a dense [reference](https://docs.tenzir.com/reference/test) that
+explains concepts, configuration, multi-project execution, and CLI details.
+
+## 🗞️ Releases
+
+New versions are published to PyPI through trusted publishing when a GitHub
+release is created. Review the latest release notes on GitHub for details about
+what's new.
+
+## 🤝 Contributing
+
+Want to contribute? We're all-in on agentic coding with [Claude
+Code](https://claude.ai/code)! The repo comes pre-configured with our [custom
+plugins](https://github.com/tenzir/claude-plugins)—just clone and start hacking.
+
+## 📜 License
+
+`tenzir-test` is available under the Apache License, Version 2.0. See
+[`LICENSE`](LICENSE) for details.

tenzir_test-0.15.0/changelog/config.yaml

@@ -0,0 +1,6 @@
+id: tenzir-test
+name: Tenzir Test
+description: >-
+  An integration testing framework that discovers tests, runs them with managed
+  fixtures, and validates output against baselines.
+repository: tenzir/test

tenzir_test-0.15.0/changelog/releases/v0.11.0/entries/01-expose-tenzir-test-as-a-library.md

@@ -0,0 +1,27 @@
+---
+title: Expose tenzir-test as a library
+type: feature
+authors:
+- mavam
+- codex
+created: 2025-11-04
+---
+
+The test framework now exposes its harness as a reusable Python library,
+returning structured execution results instead of exiting the process. Callers
+can import the new `execute` helper and receive an `ExecutionResult` with
+project summaries, exit codes, and failure details for downstream automation.
+
+Example:
+
+```python
+from pathlib import Path
+
+from tenzir_test import ExecutionResult, execute
+
+result: ExecutionResult = execute(tests=[Path("tests/pipeline.tql")])
+if result.exit_code:
+    raise SystemExit(result.exit_code)
+for project in result.project_results:
+    print(project.selection.root, project.summary.total)
+```

tenzir_test-0.15.0/changelog/releases/v0.11.0/manifest.yaml

@@ -0,0 +1,4 @@
+created: 2025-11-04
+title: Tenzir Test v0.11.0
+intro: >-
+  Expose tenzir-test as a reusable Python library.

tenzir_test-0.15.0/changelog/releases/v0.11.0/notes.md

@@ -0,0 +1,23 @@
+Expose tenzir-test as a reusable Python library.
+
+## 🚀 Features
+
+### Expose tenzir-test as a library
+
+The test framework now exposes its harness as a reusable Python library, returning structured execution results instead of exiting the process. Callers can import the new `execute` helper and receive an `ExecutionResult` with project summaries, exit codes, and failure details for downstream automation.
+
+Example:
+
+```python
+from pathlib import Path
+
+from tenzir_test import ExecutionResult, execute
+
+result: ExecutionResult = execute(tests=[Path("tests/pipeline.tql")])
+if result.exit_code:
+    raise SystemExit(result.exit_code)
+for project in result.project_results:
+    print(project.selection.root, project.summary.total)
+```
+
+*By @mavam and @codex.*

tenzir_test-0.15.0/changelog/releases/v0.12.0/entries/01-honor-no-color-for-python-api-consumers.md

@@ -0,0 +1,16 @@
+---
+title: Add configurable color output control
+type: feature
+authors:
+  - codex
+  - mavam
+created: 2025-11-05
+---
+
+We default library consumers to plain output, keep the CLI smart about ANSI usage, and honour `NO_COLOR` across every helper while locking the behaviour down with tests.
+
+When you `import tenzir_test.run`, the harness now emits unstyled text so CI logs stay machine-readable. You can still opt back into colours via `run.set_color_mode(run.ColorMode.ALWAYS)` or let auto-detection pick the best option.
+
+Running `tenzir-test` in a terminal still shows coloured summaries, but redirecting stdout—or exporting `NO_COLOR=1`—forces the palette to plain text, covering diff hunks, failure trees, retry banners, and runner diagnostics.
+
+A single palette helper now drives every glyph and symbol, and pytest coverage exercises CLI, library, and `NO_COLOR` modes to catch regressions immediately.

tenzir_test-0.15.0/changelog/releases/v0.12.0/manifest.yaml

@@ -0,0 +1,4 @@
+created: 2025-11-05
+title: Tenzir Test 0.12.0
+intro: >-
+  Minor release with improved NO_COLOR handling.

tenzir_test-0.15.0/changelog/releases/v0.12.0/notes.md

@@ -0,0 +1,17 @@
+Minor release with improved NO_COLOR handling.
+
+## 🚀 Features
+
+### Add configurable color output control
+
+We switched library consumers to plain output by default and added full `NO_COLOR` support, keeping ANSI colors only where they enhance the interactive experience.
+
+When you `import tenzir_test.run` directly, the harness now emits unstyled text by default—perfect for log parsers, CI systems, and automation scripts that expect machine-readable output. If you need colors back, call `run.set_color_mode(run.ColorMode.ALWAYS)` to force ANSI sequences on, or use `run.ColorMode.AUTO` to let the harness detect terminal capabilities.
+
+The `tenzir-test` CLI continues to auto-detect your terminal and renders colors when you run tests interactively. Redirect stdout to a file or pipe, and it automatically switches to plain mode. Set `NO_COLOR=1` in your environment, and every output—failure trees, diff hunks, retry banners—strips its color codes.
+
+All palette logic now lives in a single helper that colorizes checkmarks, crosses, diff lines, and progress indicators consistently. This unification means `run.print_diff(...)` respects your color mode choice everywhere, whether you invoke it from the CLI or from library code.
+
+We added pytest coverage for all three modes—CLI with colors, library without colors, and `NO_COLOR=1` forcing plain output—so future changes won't break the contract.
+
+*By @codex and @mavam.*

tenzir_test-0.15.0/changelog/releases/v0.13.0/entries/01-improve-diagnostics-when-tenzir-node-fails-to-start.md

@@ -0,0 +1,12 @@
+---
+title: Improve diagnostics when Tenzir Node fails to start
+type: change
+authors:
+- Alainx277
+- claude
+prs:
+- 2
+created: 2025-12-02
+---
+
+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.

tenzir_test-0.15.0/changelog/releases/v0.13.0/entries/01-library-mode-and-package-dirs.md

@@ -0,0 +1,32 @@
+---
+title: Library mode and extra packages
+type: feature
+authors:
+- codex
+- mavam
+prs:
+- 4
+created: 2025-12-02
+---
+
+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.

tenzir_test-0.15.0/changelog/releases/v0.13.0/manifest.yaml

@@ -0,0 +1,4 @@
+created: 2025-12-03
+title: Tenzir Test v0.13.0
+intro: >-
+  This release adds `--package-dirs` support and improves startup diagnostics.

tenzir_test-0.15.0/changelog/releases/v0.13.0/notes.md

@@ -0,0 +1,29 @@
+This release adds `--package-dirs` support and improves startup diagnostics.
+
+## 🚀 Features
+
+### Library mode and extra packages
+
+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.
+
+*By @codex and @mavam in [#4](https://github.com/tenzir/test/pull/4).*
+
+## 🔧 Changes
+
+### Improve diagnostics when Tenzir Node fails to start
+
+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.
+
+*By @Alainx277 and @claude in [#2](https://github.com/tenzir/test/pull/2).*

tenzir_test-0.15.0/changelog/releases/v0.13.1/entries/strip-root-paths-from-diff-runner-output.md

@@ -0,0 +1,11 @@
+---
+title: Strip root paths from diff_runner output
+type: bugfix
+authors:
+- tobim
+- claude
+pr: 5
+created: 2025-12-08T15:44:59.615542Z
+---
+
+The `DiffRunner` now strips the ROOT path prefix from output to make paths relative, consistent with `run_simple_test` behavior.

tenzir_test-0.15.0/changelog/releases/v0.13.1/manifest.yaml

@@ -0,0 +1,5 @@
+created: 2025-12-08
+title: Tenzir Test v0.13.1
+intro: >-
+  This release fixes path handling in the diff runner to strip root path prefixes
+  from output, making paths relative and consistent with other test runners.

tenzir_test-0.15.0/changelog/releases/v0.13.1/notes.md

@@ -0,0 +1,9 @@
+This release fixes path handling in the diff runner to strip root path prefixes from output, making paths relative and consistent with other test runners.
+
+## 🐞 Bug fixes
+
+### Strip root paths from diff_runner output
+
+The `DiffRunner` now strips the ROOT path prefix from output to make paths relative, consistent with `run_simple_test` behavior.
+
+*By @tobim and @claude in [#5](https://github.com/tenzir/test/pull/5).*

tenzir_test-0.15.0/changelog/releases/v0.14.0/entries/inline-test-inputs-and-local-inputs-directories.md

@@ -0,0 +1,22 @@
+---
+title: Inline test inputs and local inputs directories
+type: feature
+authors:
+  - mavam
+  - claude
+created: 2026-01-15T14:30:30.462557Z
+---
+
+The test harness now supports inline test inputs for better test organization in deeply nested test hierarchies.
+
+Tests can now place input data directly alongside test files using the `.input` extension. The harness automatically sets the `TENZIR_INPUT` environment variable pointing to `<test>.input` when the file exists. This makes test dependencies immediately visible without requiring you to navigate to a distant `inputs/` directory.
+
+Additionally, you can now create `inputs/` directories at any level in the test hierarchy. The harness walks up from each test and uses the nearest `inputs/` directory for `TENZIR_INPUTS`, with shadowing semantics where nearer directories take precedence. This lets you organize shared test data close to the tests that use it.
+
+The resolution hierarchy for `TENZIR_INPUTS` is:
+1. `inputs:` override in test frontmatter or `test.yaml` (highest priority)
+2. Nearest `inputs/` directory walking up from the test
+3. Package-level `tests/inputs/` directory
+4. Project-level `inputs/` directory (fallback)
+
+All existing tests continue to work with the global `inputs/` directory.

tenzir_test-0.15.0/changelog/releases/v0.14.0/manifest.yaml

@@ -0,0 +1,7 @@
+created: 2026-01-15
+title: Inline Test Inputs
+intro: >-
+  This release introduces inline test inputs for better test organization in deeply
+  nested hierarchies. Tests can now place input data directly alongside test files,
+  and you can create local `inputs/` directories at any level with automatic shadowing
+  semantics.

tenzir_test-0.15.0/changelog/releases/v0.14.0/notes.md

@@ -0,0 +1,22 @@
+This release introduces inline test inputs for better test organization in deeply nested hierarchies. Tests can now place input data directly alongside test files, and you can create local `inputs/` directories at any level with automatic shadowing semantics.
+
+## 🚀 Features
+
+### Inline test inputs and local inputs directories
+
+The test harness now supports inline test inputs for better test organization in deeply nested test hierarchies.
+
+Tests can now place input data directly alongside test files using the `.input` extension. The harness automatically sets the `TENZIR_INPUT` environment variable pointing to `<test>.input` when the file exists. This makes test dependencies immediately visible without requiring you to navigate to a distant `inputs/` directory.
+
+Additionally, you can now create `inputs/` directories at any level in the test hierarchy. The harness walks up from each test and uses the nearest `inputs/` directory for `TENZIR_INPUTS`, with shadowing semantics where nearer directories take precedence. This lets you organize shared test data close to the tests that use it.
+
+The resolution hierarchy for `TENZIR_INPUTS` is:
+
+1. `inputs:` override in test frontmatter or `test.yaml` (highest priority)
+1. Nearest `inputs/` directory walking up from the test
+1. Package-level `tests/inputs/` directory
+1. Project-level `inputs/` directory (fallback)
+
+All existing tests continue to work with the global `inputs/` directory.
+
+*By @mavam and @claude.*