tigrbl_tests
Reusable Tigrbl pytest fixtures, conformance assertions, integration helpers, and package test utilities.
What is tigrbl_tests?
Reusable Tigrbl pytest fixtures, conformance assertions, integration helpers, and package test utilities.
Why use tigrbl_tests?
Use it when downstream packages need the same Tigrbl fixtures, conformance helpers, and regression assertions used by the workspace.
When should I install tigrbl_tests?
Install it in CI, package-local validation, transport integration tests, and compatibility checks.
Who is tigrbl_tests for?
Maintainers, extension authors, and integration teams validating Tigrbl-compatible packages.
Where does tigrbl_tests fit?
tigrbl_tests lives at pkgs/97_tests/tigrbl_tests and serves reusable test, conformance, and integration support for Tigrbl packages.
How does tigrbl_tests work?
It packages reusable pytest assets and helper modules that exercise public Tigrbl behavior instead of relying on private workspace state.
Install
uv add tigrbl_tests
pip install tigrbl_tests
Surface Coverage
| Surface | Value |
|---|---|
| PyPI package | tigrbl_tests |
| Repository path | pkgs/97_tests/tigrbl_tests |
| Python import root | benchmarks, tigrbl_tests, triage_tests, v4 |
| Console scripts | none declared |
| Entry points | none declared |
| Optional extras | none declared |
| Legal files | LICENSE, NOTICE |
| Supported Python | `3.10 |
What It Owns
tigrbl_tests owns the test support package boundary. It should be installed when you need this package's focused responsibility without assuming every other Tigrbl workspace package is present.
Implementation orientation:
benchmarks: comparative_benchmark_verification, open_loop_load_patterns, run_hot_path_perf_suite, tigrbl_fastapi_surface_matrix_benchmark, tigrbl_kernel_plan_benchmark, tigrbl_request_response_benchmark, tigrbl_sse_perf_suite, tigrbl_streaming_perf_suite, tigrbl_websocket_perf_suite, tigrbl_webtransport_perf_suitetigrbl_tests: tests/v4: tests/
Public API and Import Surface
- Import roots:
benchmarks,tigrbl_tests,triage_tests,v4. - Public symbols: public surface is module-oriented; import the package boundary and inspect submodules as needed.
- Workspace dependencies:
tigrbl,tigrbl-examples,tigrbl_client. - External runtime dependencies:
psycopg2-binary>=2.9.9,asyncpg>=0.30.0,pytest>=8.0,pytest-asyncio>=0.24.0,pytest-xdist>=3.6.1,pytest-json-report>=1.5.0,python-dotenv,requests>=2.32.3,flake8>=7.0,pytest-timeout>=2.3.1,ruff>=0.9.9,pytest-benchmark>=4.0.0,jinja2>=3.1.0.
Usage Examples
Verify the installed package
python -m pip show tigrbl_tests
python - <<'PY'
from importlib.metadata import version
print(version("tigrbl_tests"))
PY
Run packaged Tigrbl tests
uv run pytest pkgs/97_tests/tigrbl_tests/tests -q
python -m pytest --pyargs tigrbl_tests
Import reusable test helpers
import tigrbl_tests
print(tigrbl_tests.__name__)
Use it in downstream CI
pip install tigrbl-tests pytest
pytest -q
How To Choose This Package
Choose tigrbl_tests when the quick-answer table matches your use case. Choose tigrbl instead when you want the full public facade. Choose a lower-level package such as tigrbl-core, tigrbl-base, or tigrbl-runtime when you are building framework extensions or testing a specific internal boundary.
Related Packages
Documentation Links
- Workspace docs
- Package catalog
- Package layout
- Current target
- Current state
- SSOT registry
- Release workflow
Support
- Community: Discord.
- Issues: GitHub Issues.
- Repository: pkgs/97_tests/tigrbl_tests.
Package-local Boundary
This README is the package-local distribution entry point for tigrbl_tests. It answers install, usage, API, ownership, and certification-orientation questions for this package. Broader architectural decisions, release status, and cross-package proof chains remain in the repository-level docs and SSOT registry.
Certification Status
- Package status: governed package in the
tigrbl/tigrblworkspace. - Governance source: SSOT registry.
- Release evidence: publish workflow validates package builds, tests, GitHub release assets, and PyPI publication for managed packages.
- Local certification guard:
pkgs/97_tests/tigrbl_tests/tests/unit/test_package_badges_and_notices.pyverifies every package README keeps the Discord badge, Apache 2.0 badge, explicit Python-version badge,LICENSE, andNOTICE. - Scope note: this README documents the package boundary. Runtime feature support remains governed by
.ssot/entities and the conformance docs linked below.
License
Licensed under the Apache License, Version 2.0. See LICENSE, NOTICE, and the official Apache 2.0 license text.
Metadata
Release files for tigrbl_tests 0.4.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tigrbl_tests-0.4.5.tar.gz | 517.3 kB | Without provenance | Details for tigrbl_tests-0.4.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tigrbl_tests-0.4.5-py3-none-any.whl | Python 3 | none | any | Details for tigrbl_tests-0.4.5-py3-none-any.whl |
Total release size: 1.3 MB
Release files / tigrbl_tests-0.4.5.tar.gz
| Download URL | tigrbl_tests-0.4.5.tar.gz |
|---|---|
| Size | 517.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b354e7afee658f75c467597dc54ca6d3302f1ade30d0efb2d6047864e0054d5b
|
|
BLAKE2b-256 checksum How to use checksums |
129c02aa223a1b68eddead13f9ffc5667c68723956928f1fae59024153dba32d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / tigrbl_tests-0.4.5-py3-none-any.whl
| Download URL | tigrbl_tests-0.4.5-py3-none-any.whl |
|---|---|
| Size | 831.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f3f17607f5f902ebebf5136ca25cb2592ad446d8ed175c910633f2f7658ba3b
|
|
BLAKE2b-256 checksum How to use checksums |
ebad0b98409fbf2a17b5d5aa1aedc7733301435f3955b6911f6725bac75f555d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for tigrbl_tests 0.4.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.