cloudru-qa-logging-context 1.0.0__py3-none-any.whl

cloudru_qa_logging_context-1.0.0.dist-info/METADATA

@@ -0,0 +1,396 @@
+Metadata-Version: 2.5
+Name: cloudru-qa-logging-context
+Version: 1.0.0
+Summary: Разделение контекста логов при параллельном запуске автотестов
+Project-URL: Repository, https://github.com/cloud-ru-tech/qa-libraries
+Project-URL: Issues, https://github.com/cloud-ru-tech/qa-libraries/issues
+Author-email: Алексей Кирютин <ayukiryutin@cloud.ru>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: allure,logging,pytest,testing
+Classifier: Framework :: Pytest
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Testing
+Classifier: Typing :: Typed
+Requires-Python: >=3.13
+Requires-Dist: pytest<10,>=8.4.0
+Description-Content-Type: text/markdown
+
+# Logging context for automated tests
+
+[![PyPI](https://img.shields.io/pypi/v/cloudru-qa-logging-context)](https://pypi.org/project/cloudru-qa-logging-context/)
+[![Python](https://img.shields.io/pypi/pyversions/cloudru-qa-logging-context)](https://pypi.org/project/cloudru-qa-logging-context/)
+[![License](https://img.shields.io/pypi/l/cloudru-qa-logging-context)](https://github.com/cloud-ru-tech/qa-libraries/blob/master/LICENSE)
+
+English | [Русский](README.ru.md)
+
+A pytest plugin that writes each test's logs to a separate file and attaches them to
+the Allure report.
+
+Each test report should contain only that test's logs. With a regular
+`FileHandler`, all tests append to one file, so attached logs include
+messages from other tests. Parallel execution with
+[`pytest-xdist`](https://pytest-xdist.readthedocs.io/en/stable/) also means
+multiple processes writing to the same file. This plugin handles both cases.
+
+- [Installation](#installation)
+- [Skills for AI agents](#skills-for-ai-agents)
+- [Quick start](#quick-start)
+- [Demo projects](#demo-projects)
+- [Where to find logs](#where-to-find-logs)
+- [Settings](#settings)
+- [Allure](#allure)
+- [structlog](#structlog)
+- [Other loggers and custom formats](#other-loggers-and-custom-formats)
+- [Development](#development)
+
+## Installation
+
+Requires Python 3.13 or later.
+
+```shell
+pip install cloudru-qa-logging-context
+```
+
+Import the plugin as `logging_context`.
+
+## Skills for AI agents
+
+This library does not have its own skill yet. If your project uses other
+libraries from this suite with [skills for AI agents](https://github.com/cloud-ru-tech/qa-libraries#skills-for-ai-agents),
+select and enable them from your project root (requires [`uv`](https://docs.astral.sh/uv/)):
+
+```shell
+uvx library-skills
+```
+
+For Claude Code, add `--claude`.
+
+## Quick start
+
+The plugin loads automatically when installed, but **does nothing** until you set
+a log directory. One line is enough:
+
+```toml
+# pyproject.toml
+[tool.pytest.ini_options]
+logging_context_dir = "logs"
+```
+
+A custom `conftest.py` is needed only for formatters that cannot be expressed as an ini string,
+such as structlog or JSON (see below). For this test:
+
+```python
+import logging
+
+import pytest
+
+logger = logging.getLogger("test-logger")
+
+
+@pytest.fixture
+def user():
+    logger.info("creating a user")
+    yield {"id": 1}
+    logger.info("deleting a user")
+
+
+def test_login(user):
+    logger.info("logging in as id=%s", user["id"])
+
+
+@pytest.mark.parametrize("role", ["admin", "guest"])
+def test_roles(role):
+    logger.info("checking role %s", role)
+```
+
+running `pytest` produces:
+
+```
+logs/test_login.log
+logs/test_roles[48fb048115c186ec].log
+logs/test_roles[a81f6f2ab448a918].log
+```
+
+The plugin-generated headers retain their original Russian text:
+
+```
+--- logs/test_login.log
+30.07.2026 15:21:40.776 - INFO - Запуск теста id=test_demo.py::test_login
+30.07.2026 15:21:40.776 - INFO - creating a user
+30.07.2026 15:21:40.778 - INFO - logging in as id=1
+30.07.2026 15:21:40.780 - INFO - deleting a user
+
+--- logs/test_roles[a81f6f2ab448a918].log
+30.07.2026 15:21:40.790 - INFO - Запуск теста id=test_demo.py::test_roles[a81f6f2ab448a918] с параметрами {"role": "admin"}
+30.07.2026 15:21:40.792 - INFO - checking role admin
+```
+
+Logs are attached to the Allure report automatically when `allure-pytest` is installed.
+
+![allure-report](https://raw.githubusercontent.com/cloud-ru-tech/qa-libraries/master/packages/logging-context/assets/allure-report.png)
+
+## Demo projects
+
+[`examples/`](https://github.com/cloud-ru-tech/qa-libraries/tree/master/packages/logging-context/examples) contains two ready-to-run projects with the plugin enabled. Both use
+the same sample shop client and tests, with fixtures, parametrization,
+an intentionally failing test, and retries. Only their log formats differ:
+
+| Example | Log file contents |
+|---|---|
+| [`examples/logging`](https://github.com/cloud-ru-tech/qa-libraries/tree/master/packages/logging-context/examples/logging) | Standard library `logging`, with lines such as `INFO shop.client товар SKU-TEA — Чай листовой` |
+| [`examples/structlog`](https://github.com/cloud-ru-tech/qa-libraries/tree/master/packages/logging-context/examples/structlog) | `structlog`, using JSON Lines |
+
+Run commands from the example directory, such as `packages/logging-context/examples/logging`:
+
+```shell
+uv sync
+rm -rf logs
+uv run pytest -v --clean-alluredir --alluredir=allure-results
+npx allure awesome allure-results --single-file --output allure-report
+```
+
+Each test's logs remain in `logs/`, and the report is in `allure-report/index.html`. For parallel
+runs with `pytest-xdist`, add `-n 4` to pytest. Building the report requires Node.js.
+
+One test in each example fails intentionally, showing that a failing test's report contains
+its own logs and that those logs explain the failure.
+
+## Where to find logs
+
+| File | Contents |
+|---|---|
+| `<test name>.log` | Test logs, including setup and teardown of all its fixtures |
+| `fixtures_<worker_id>.log` | Logs outside tests, such as `pytest_sessionstart` or `conftest.py` imports |
+
+Test parameters in filenames are replaced with hashes to keep names short and safe
+regardless of parameter values. The parameters themselves appear in the first log line.
+
+If a filename repeats, such as when retrying a failed test with
+`pytest-rerunfailures` or when test functions in different modules share a name,
+a numeric suffix is added. Each rerun attempt has its own file, so the report
+shows the logs of the failed attempt:
+
+```
+logs/test_login.log     <- first attempt
+logs/test_login.2.log   <- second attempt
+logs/test_login.3.log   <- third attempt
+```
+
+Parallel runs add a worker identifier to filenames, so tests with the same function name
+running on different workers do not write to the same file:
+
+```
+pytest            ->  logs/test_login.log
+pytest -n 2       ->  logs/test_login.gw0.log
+```
+
+No log file is overwritten.
+
+## Settings
+
+Set all options in pytest configuration (`pyproject.toml`, `pytest.ini`, or `tox.ini`).
+
+| Setting | Default | Description |
+|---|---|---|
+| `logging_context_dir` | — | Log directory. **The plugin is inactive until this is set.** Relative paths are resolved from `rootdir`. |
+| `logging_context_launch_id` | — | Subdirectory within `logging_context_dir`, such as a CI run identifier. Must be a single path component. Can be overridden by a CLI option or environment variable; see below. |
+| `logging_context_loggers` | root | Loggers to collect records from. Defaults to root, including third-party libraries. |
+| `logging_context_level` | `INFO` | Minimum record level, as a name (`DEBUG`) or number. |
+| `logging_context_format` | `%(asctime)s.%(msecs)03d - %(levelname)s - %(message)s` | Log line format. |
+| `logging_context_date_format` | `%d.%m.%Y %H:%M:%S` | Timestamp format. |
+| `logging_context_attach_allure` | `true` | Attach log files to the Allure report. |
+| `logging_context_attach_fixtures_log` | `true` | Attach `fixtures_<worker_id>.log` to each test. |
+| `logging_context_log_test_header` | `true` | Start each file with the test identifier and parameters. |
+| `logging_context_params_indent` | `-1` | JSON indentation for parameters. `-1` means a single line. |
+
+Collect logs only from your own loggers:
+
+```toml
+[tool.pytest.ini_options]
+logging_context_dir = "logs"
+logging_context_loggers = ["test-logger", "api-client"]
+logging_context_level = "INFO"
+```
+
+By default, logs include third-party libraries (`httpx`, `urllib3`,
+`playwright`), which often help explain test failures. To exclude this noise,
+list your own loggers in `logging_context_loggers`.
+
+The default mode also captures loggers with `propagate = False`, even if created
+after the run starts. With `logging_context_loggers` set, however,
+you must list these loggers explicitly; they are not discovered automatically.
+
+Test parameters appear in the header as supplied. If they contain tokens or passwords,
+disable the header: `logging_context_log_test_header = false`.
+
+### Launch identifier
+
+`launch_id` often comes from CI, so you can set it outside ini configuration:
+
+```shell
+pytest --logging-context-launch-id="$CI_PIPELINE_ID"
+```
+
+```shell
+LOGGING_CONTEXT_LAUNCH_ID="$CI_PIPELINE_ID" pytest
+```
+
+Priority: command-line option → `LOGGING_CONTEXT_LAUNCH_ID` environment variable →
+`logging_context_launch_id` in ini. Logs are stored in `<logging_context_dir>/<launch_id>/`.
+
+## Allure
+
+No extra setup is needed: when `allure-pytest` is installed and `--alluredir` is set,
+the plugin attaches the test log and fixtures log to each test. Disable this with
+`logging_context_attach_allure = false`, or disable only the fixtures log with
+`logging_context_attach_fixtures_log = false`.
+
+`allure-pytest` **also attaches its own** `log` attachment to each test.
+To avoid duplicate log attachments, disable one using `--allure-no-capture` or
+`logging_context_attach_allure = false`.
+
+## structlog
+
+Route `structlog` through standard library logging and set the formatter with the
+`pytest_logging_context_configure`:
+
+```python
+# conftest.py
+import structlog
+
+structlog.configure(
+    processors=[
+        structlog.stdlib.add_logger_name,
+        structlog.stdlib.add_log_level,
+        structlog.stdlib.ProcessorFormatter.wrap_for_formatter,
+    ],
+    logger_factory=structlog.stdlib.LoggerFactory(),
+    wrapper_class=structlog.stdlib.BoundLogger,
+    cache_logger_on_first_use=True,
+)
+
+
+def pytest_logging_context_configure(handler):
+    handler.setFormatter(
+        structlog.stdlib.ProcessorFormatter(
+            processor=structlog.processors.JSONRenderer(ensure_ascii=False),
+            foreign_pre_chain=[
+                structlog.stdlib.add_logger_name,
+                structlog.stdlib.add_log_level,
+            ],
+        ),
+    )
+```
+
+```toml
+# pyproject.toml
+[tool.pytest.ini_options]
+logging_context_dir = "logs"
+logging_context_log_test_header = false
+```
+
+`logging_context_log_test_header = false` keeps the file valid
+JSON Lines.
+
+The hook also accepts `config`; add it to the signature if needed. A complete working example
+is in [`examples/structlog`](https://github.com/cloud-ru-tech/qa-libraries/tree/master/packages/logging-context/examples/structlog).
+
+Test:
+
+```python
+import structlog
+
+log = structlog.get_logger("test-logger")
+
+
+def test_creates_shipment():
+    log.info("shipment created", shipment_id=77)
+```
+
+`logs/test_creates_shipment.log`:
+
+```json
+{"shipment_id": 77, "event": "shipment created", "logger": "test-logger", "level": "info"}
+```
+
+Bound context is preserved:
+
+```python
+def test_retries_request():
+    log = structlog.get_logger("test-logger").bind(request_id="req-51")
+    log.warning("unexpected response")
+```
+
+```json
+{"request_id": "req-51", "event": "unexpected response", "logger": "test-logger", "level": "warning"}
+```
+
+With `foreign_pre_chain`, third-party logs using standard library `logging` go to
+the same file in the same format:
+
+```python
+def test_mixes_loggers():
+    structlog.get_logger("test-logger").info("from structlog")
+    logging.getLogger("legacy.client").warning("from stdlib")
+```
+
+`logs/test_mixes_loggers.log`:
+
+```json
+{"event": "from structlog", "logger": "test-logger", "level": "info"}
+{"event": "from stdlib", "logger": "legacy.client", "level": "warning"}
+```
+
+## Other loggers and custom formats
+
+Any logger that writes through standard library `logging` works. For `loguru`, use its
+standard `InterceptHandler`; the rest is the same.
+
+Use `pytest_logging_context_configure` for any formatter that cannot be expressed
+as an ini string:
+
+```python
+# conftest.py
+import json
+import logging
+
+
+class JsonFormatter(logging.Formatter):
+    def format(self, record: logging.LogRecord) -> str:
+        return json.dumps(
+            {
+                "time": self.formatTime(record),
+                "level": record.levelname,
+                "logger": record.name,
+                "message": record.getMessage(),
+            },
+            ensure_ascii=False,
+        )
+
+
+def pytest_logging_context_configure(handler):
+    handler.setFormatter(JsonFormatter())
+```
+
+## Development
+
+This library is developed in the [qa-libraries](https://github.com/cloud-ru-tech/qa-libraries) monorepo
+alongside the other `cloudru-qa-*` libraries. You need [`uv`](https://docs.astral.sh/uv/), GNU Make
+and [`checkmake`](https://github.com/checkmake/checkmake);
+run the commands from the repository root:
+
+```shell
+make sync                        # dependencies for all libraries from uv.lock
+make test-logging-context        # tests for this library
+make typecheck-logging-context   # mypy for this library
+make check                       # formatting, Ruff, mypy, and tests for the whole suite
+```
+
+All checks must pass without errors or warnings. Tests run on Python 3.13 and 3.14.
+Each version uses a separate environment: `make sync test-logging-context PYTHON_VERSION=3.14`.
+
+Create a release with the Git tag `logging-context/v<version>`. The tag version must match the version
+in `packages/logging-context/pyproject.toml`.

cloudru_qa_logging_context-1.0.0.dist-info/RECORD

@@ -0,0 +1,11 @@
+logging_context/__init__.py,sha256=e56rVYTxiKcyY-RYSGnOMgqhcEQRe-9h3A0-rcOmXiU,221
+logging_context/handler.py,sha256=YqkKw0rTbsFF1Ez1SkZlR0T-bTGVAUSywG39pqswBhs,7931
+logging_context/hooks.py,sha256=M_GjJ3Wj-NK91woa_BulFvk0XvPP8VCyL84X6FYErs8,655
+logging_context/naming.py,sha256=v2WEEMa4Gu3Vwddq1WY1mhXiGE6AUTYMRWp2ioZnJSM,2933
+logging_context/plugin.py,sha256=7kumEWe938kTKM33uj_4K6yS-pD8nRaZZKBEbCedEdI,16872
+logging_context/py.typed,sha256=hX8e_n7eEN-XCFXp-0DSLCxxy9hHO4Sczj3VNIVXt_k,77
+cloudru_qa_logging_context-1.0.0.dist-info/METADATA,sha256=8tIpwSXaCszGVTLtTaPJ6QSLpWhdhmMLiIzBQn6pHZU,13958
+cloudru_qa_logging_context-1.0.0.dist-info/WHEEL,sha256=2iZrJkDIkeDh0k9SikKMqFuRP-ua6mb4Ir1AsER4BEw,87
+cloudru_qa_logging_context-1.0.0.dist-info/entry_points.txt,sha256=ztXgO9QS1E3YxWa1G0h3IauSjzOK_XdX3vLxB2J2Gy4,52
+cloudru_qa_logging_context-1.0.0.dist-info/licenses/LICENSE,sha256=z8d0m5b2O9McPEK1xHG_dWgUBT6EfBDz6wA0F7xSPTA,11358
+cloudru_qa_logging_context-1.0.0.dist-info/RECORD,,

cloudru_qa_logging_context-1.0.0.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.33.0
+Root-Is-Purelib: true
+Tag: py3-none-any

cloudru_qa_logging_context-1.0.0.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[pytest11]
+logging_context = logging_context.plugin

cloudru_qa_logging_context-1.0.0.dist-info/licenses/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   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.

logging_context/__init__.py

@@ -0,0 +1,4 @@
+from .handler import HandlerOptions, LoggingContextHandler
+from .naming import build_test_id, build_test_name, slugify
+
+__all__ = ["HandlerOptions", "LoggingContextHandler", "build_test_id", "build_test_name", "slugify"]