mender-testkit 0.1.1__tar.gz

mender_testkit-0.1.1/LICENSE

@@ -0,0 +1,181 @@
+Copyright 2026 Northern.tech AS
+
+All content in this project is licensed under the Apache License v2, unless
+indicated otherwise.
+
+-------------------------------------------------------------------------------
+
+                               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.

mender_testkit-0.1.1/PKG-INFO

@@ -0,0 +1,215 @@
+Metadata-Version: 2.4
+Name: mender-testkit
+Version: 0.1.1
+Summary: Shared test infrastructure for the Mender integration test suites
+License: Apache-2.0
+Project-URL: Repository, https://github.com/mendersoftware/mender-testkit
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: aiosmtpd>=1.4.6
+Requires-Dist: cryptography>=47.0.0
+Requires-Dist: docker>=7.1.0
+Requires-Dist: filelock>=3.29.0
+Requires-Dist: msgpack>=1.2.1
+Requires-Dist: pymongo>=4.17.0
+Requires-Dist: pytest>=9.0.3
+Requires-Dist: redo>=3.0.0
+Requires-Dist: requests>=2.34.2
+Requires-Dist: stripe>=15.2.0
+Requires-Dist: urllib3>=2.7.0
+Requires-Dist: websockets>=16.0
+Provides-Extra: kubernetes
+Requires-Dist: kubernetes>=36.0.2; extra == "kubernetes"
+Dynamic: license-file
+
+# mender-testkit
+
+Shared test infrastructure for the Mender integration test suites.
+
+The suites in `mender-binary-delta`, `mender-configure-module`, `mender-gateway`,
+`mender-orchestrator` and `integration` all rely on the same things: a mender-server
+backend brought up under docker compose, a client for its management API, and a
+way to start QEMU devices against it. Each repo used to carry its own copy of all
+of it, kept in step by hand, plus a `mender_server` submodule for the compose
+files. This package is that copy.
+
+## Install
+```
+pip install mender-testkit
+```
+
+That replaces both the `mender_server` submodule and the
+`pip install -r mender_server/backend/tests/requirements-integration.txt` line
+that every consuming repo used to have -- the dependency list is this package's
+own.
+
+`kubernetes` is an extra rather than a dependency. Nothing here imports it unless
+`K8S` is set in the environment, so a suite running against docker compose does
+not need it installed:
+
+```
+pip install mender-testkit[kubernetes]     # only if you run against a cluster
+```
+
+## Using it
+
+**The backend.** Request one of two pytest fixtures and it is up before your test
+runs. They arrive through an entry point, so there is nothing to import or
+register:
+
+```python
+def test_something(os_backend_server):
+    server = Server()                      # plan="os"
+
+def test_something_else(enterprise_backend_server):
+    server = Server(plan="enterprise")     # provisions a tenant via tenantadm
+```
+
+One backend runs at a time. Two full stacks plus QEMU clients starve the Go
+services of CPU and requests start coming back from Traefik as 504s, so asking
+for the other flavour switches rather than adding. Under `pytest-xdist` the stack
+is started once for the whole run and torn down when the last worker finishes.
+
+**The API.** `Server` is a client, not a lifecycle manager -- it assumes the
+backend is already up:
+
+```python
+from mender_testkit.server import Server
+
+server = Server(plan="enterprise")
+device_ids = server.accept_devices(env.devices)
+server.upload_image("artifact.mender")
+deployment = server.create_deployment("artifact.mender", device_ids)
+server.check_expected_status("finished", deployment)
+```
+
+Every request carries `Host: docker.mender.io`, because Traefik's routers match on
+Host as well as path and the tests reach it by container IP. `GATEWAY_HOSTNAME`
+is set when this package is first imported; override it in the environment if your
+ingress answers to something else.
+
+**Devices.**
+
+```python
+from mender_testkit.devices import Env, clients_up, wait_for_devices
+
+env = Env()
+env.server = Server()
+env.devices = clients_up(2, "docker-compose.client.yml", network=env.server.network)
+wait_for_devices(env)
+```
+
+Client compose files stay in the consuming repo: the device under test is the
+repo's product, not this package's business. What this package supplies is the
+network it attaches to, via `MENDER_SERVER_NETWORK`, which `clients_up` exports.
+Declare it in your client compose file as
+
+```yaml
+networks:
+  mender_server:
+    external: true
+    name: ${MENDER_SERVER_NETWORK:-mender_default}
+```
+
+**Compose files, directly.** If you drive compose yourself rather than through the
+fixtures:
+
+```python
+from mender_testkit.compose import compose_dir, compose_files
+
+files = compose_files("enterprise")        # absolute paths, in -f order
+```
+
+They are package data, so they are copied to a real directory on first use --
+compose needs actual files, and it needs the whole tree, because
+`docker-compose.yml` bind-mounts `./compose/certs` and `./compose/config` relative
+to the project directory. Pass `compose_dir()` as `--project-directory`. It is a
+temporary directory removed at process exit; pass `compose_dir(dest=...)` if you
+need one that outlives the process.
+
+By default the backend publishes no host ports. The tests reach Traefik by
+container IP, so publishing buys nothing and costs exclusivity -- only one stack
+can hold 443. Pass `publish_ports=True` if you want to reach the backend from the
+host, which works for one backend at a time.
+
+## The vendored trees
+
+Two directories are **generated, not written**:
+
+| path | from |
+| --- | --- |
+| `src/mender_testkit/testutils/` | mender-server's `backend/tests/testutils` |
+| `src/mender_testkit/data/mender_server/` | mender-server's compose files |
+
+Both are copies of the commit in `src/mender_testkit/_server_ref.py`, produced by
+`scripts/vendor.py`. Do not edit either by hand: a fix belongs upstream in
+mender-server, after which the ref moves and the copies are regenerated. Editing
+them here creates a fork that looks identical to a stale one, which is the state
+this package exists to end.
+
+`testutils` is vendored rather than depended on because mender-server does not
+publish it. Committing the copies rather than fetching at build time keeps the
+wheel reproducible from a tag and lets `pip install` work without reaching
+GitHub.
+
+To refresh:
+
+```
+$EDITOR src/mender_testkit/_server_ref.py     # or let Renovate do it
+scripts/vendor.py
+scripts/vendor.py --check                     # asserts the trees match the ref
+```
+
+`--check` is worth running in CI: it catches both a hand-edit and a ref bump whose
+files were never regenerated.
+
+### Why a commit and not a release tag
+
+Because these suites test unreleased server code. `.env` pins the backend images
+to `main`, and the clients they run against are `client-main` builds, so the
+compose files and `testutils` have to come from the same place -- a release tag
+would mean a released compose driving unreleased images.
+
+The immediate reason is narrower: fixes these suites need land on `main` first and
+reach a tag only at the next release, so a tag-based pin is always some way behind
+what the tests require.
+
+A tag is otherwise perfectly workable. Tracking released versions instead would
+mean putting a tag in `_server_ref.py`, swapping this file's manager to the
+`github-releases` datasource (matching `currentValue` rather than
+`currentDigest`), and teaching `scripts/vendor.py` to fetch a tag rather than a
+SHA. Note that release tags route on path alone; the `Host(...)` clause matching
+`MENDER_HOSTNAME` is something `main` *added*, so the explicit `Host` header this
+package sends is required by `main` and merely redundant against a tag.
+
+### Judging a ref bump
+
+mender-server moves at roughly 280 commits a month, so most bumps change nothing
+here. What matters is whether the files these suites actually consume moved:
+
+```
+git diff <old>..<new> -- docker-compose.yml compose/docker-compose.enterprise.yml \
+                         compose/config compose/certs
+```
+
+Empty or cosmetic, and one suite is enough to gate it. If the service list moved,
+run them all. A 1699-commit bump once turned out to be nine lines of image tags.
+
+## Building
+
+```
+rm -rf build dist src/*.egg-info
+python -m build --wheel
+```
+
+The `rm` is needed here because setuptools reuses `build/lib`, and after
+`testutils` moved under `mender_testkit/`, a stale copy there produced a wheel
+containing the tree *twice* -- once at top level, once namespaced -- with no
+warning. Verify what you built:
+
+```
+python -c "import zipfile,glob; \
+  print([n for n in zipfile.ZipFile(sorted(glob.glob('dist/*.whl'))[-1]).namelist() \
+         if n.startswith('testutils/')])"     # must be empty
+```

mender_testkit-0.1.1/README.md

@@ -0,0 +1,190 @@
+# mender-testkit
+
+Shared test infrastructure for the Mender integration test suites.
+
+The suites in `mender-binary-delta`, `mender-configure-module`, `mender-gateway`,
+`mender-orchestrator` and `integration` all rely on the same things: a mender-server
+backend brought up under docker compose, a client for its management API, and a
+way to start QEMU devices against it. Each repo used to carry its own copy of all
+of it, kept in step by hand, plus a `mender_server` submodule for the compose
+files. This package is that copy.
+
+## Install
+```
+pip install mender-testkit
+```
+
+That replaces both the `mender_server` submodule and the
+`pip install -r mender_server/backend/tests/requirements-integration.txt` line
+that every consuming repo used to have -- the dependency list is this package's
+own.
+
+`kubernetes` is an extra rather than a dependency. Nothing here imports it unless
+`K8S` is set in the environment, so a suite running against docker compose does
+not need it installed:
+
+```
+pip install mender-testkit[kubernetes]     # only if you run against a cluster
+```
+
+## Using it
+
+**The backend.** Request one of two pytest fixtures and it is up before your test
+runs. They arrive through an entry point, so there is nothing to import or
+register:
+
+```python
+def test_something(os_backend_server):
+    server = Server()                      # plan="os"
+
+def test_something_else(enterprise_backend_server):
+    server = Server(plan="enterprise")     # provisions a tenant via tenantadm
+```
+
+One backend runs at a time. Two full stacks plus QEMU clients starve the Go
+services of CPU and requests start coming back from Traefik as 504s, so asking
+for the other flavour switches rather than adding. Under `pytest-xdist` the stack
+is started once for the whole run and torn down when the last worker finishes.
+
+**The API.** `Server` is a client, not a lifecycle manager -- it assumes the
+backend is already up:
+
+```python
+from mender_testkit.server import Server
+
+server = Server(plan="enterprise")
+device_ids = server.accept_devices(env.devices)
+server.upload_image("artifact.mender")
+deployment = server.create_deployment("artifact.mender", device_ids)
+server.check_expected_status("finished", deployment)
+```
+
+Every request carries `Host: docker.mender.io`, because Traefik's routers match on
+Host as well as path and the tests reach it by container IP. `GATEWAY_HOSTNAME`
+is set when this package is first imported; override it in the environment if your
+ingress answers to something else.
+
+**Devices.**
+
+```python
+from mender_testkit.devices import Env, clients_up, wait_for_devices
+
+env = Env()
+env.server = Server()
+env.devices = clients_up(2, "docker-compose.client.yml", network=env.server.network)
+wait_for_devices(env)
+```
+
+Client compose files stay in the consuming repo: the device under test is the
+repo's product, not this package's business. What this package supplies is the
+network it attaches to, via `MENDER_SERVER_NETWORK`, which `clients_up` exports.
+Declare it in your client compose file as
+
+```yaml
+networks:
+  mender_server:
+    external: true
+    name: ${MENDER_SERVER_NETWORK:-mender_default}
+```
+
+**Compose files, directly.** If you drive compose yourself rather than through the
+fixtures:
+
+```python
+from mender_testkit.compose import compose_dir, compose_files
+
+files = compose_files("enterprise")        # absolute paths, in -f order
+```
+
+They are package data, so they are copied to a real directory on first use --
+compose needs actual files, and it needs the whole tree, because
+`docker-compose.yml` bind-mounts `./compose/certs` and `./compose/config` relative
+to the project directory. Pass `compose_dir()` as `--project-directory`. It is a
+temporary directory removed at process exit; pass `compose_dir(dest=...)` if you
+need one that outlives the process.
+
+By default the backend publishes no host ports. The tests reach Traefik by
+container IP, so publishing buys nothing and costs exclusivity -- only one stack
+can hold 443. Pass `publish_ports=True` if you want to reach the backend from the
+host, which works for one backend at a time.
+
+## The vendored trees
+
+Two directories are **generated, not written**:
+
+| path | from |
+| --- | --- |
+| `src/mender_testkit/testutils/` | mender-server's `backend/tests/testutils` |
+| `src/mender_testkit/data/mender_server/` | mender-server's compose files |
+
+Both are copies of the commit in `src/mender_testkit/_server_ref.py`, produced by
+`scripts/vendor.py`. Do not edit either by hand: a fix belongs upstream in
+mender-server, after which the ref moves and the copies are regenerated. Editing
+them here creates a fork that looks identical to a stale one, which is the state
+this package exists to end.
+
+`testutils` is vendored rather than depended on because mender-server does not
+publish it. Committing the copies rather than fetching at build time keeps the
+wheel reproducible from a tag and lets `pip install` work without reaching
+GitHub.
+
+To refresh:
+
+```
+$EDITOR src/mender_testkit/_server_ref.py     # or let Renovate do it
+scripts/vendor.py
+scripts/vendor.py --check                     # asserts the trees match the ref
+```
+
+`--check` is worth running in CI: it catches both a hand-edit and a ref bump whose
+files were never regenerated.
+
+### Why a commit and not a release tag
+
+Because these suites test unreleased server code. `.env` pins the backend images
+to `main`, and the clients they run against are `client-main` builds, so the
+compose files and `testutils` have to come from the same place -- a release tag
+would mean a released compose driving unreleased images.
+
+The immediate reason is narrower: fixes these suites need land on `main` first and
+reach a tag only at the next release, so a tag-based pin is always some way behind
+what the tests require.
+
+A tag is otherwise perfectly workable. Tracking released versions instead would
+mean putting a tag in `_server_ref.py`, swapping this file's manager to the
+`github-releases` datasource (matching `currentValue` rather than
+`currentDigest`), and teaching `scripts/vendor.py` to fetch a tag rather than a
+SHA. Note that release tags route on path alone; the `Host(...)` clause matching
+`MENDER_HOSTNAME` is something `main` *added*, so the explicit `Host` header this
+package sends is required by `main` and merely redundant against a tag.
+
+### Judging a ref bump
+
+mender-server moves at roughly 280 commits a month, so most bumps change nothing
+here. What matters is whether the files these suites actually consume moved:
+
+```
+git diff <old>..<new> -- docker-compose.yml compose/docker-compose.enterprise.yml \
+                         compose/config compose/certs
+```
+
+Empty or cosmetic, and one suite is enough to gate it. If the service list moved,
+run them all. A 1699-commit bump once turned out to be nine lines of image tags.
+
+## Building
+
+```
+rm -rf build dist src/*.egg-info
+python -m build --wheel
+```
+
+The `rm` is needed here because setuptools reuses `build/lib`, and after
+`testutils` moved under `mender_testkit/`, a stale copy there produced a wheel
+containing the tree *twice* -- once at top level, once namespaced -- with no
+warning. Verify what you built:
+
+```
+python -c "import zipfile,glob; \
+  print([n for n in zipfile.ZipFile(sorted(glob.glob('dist/*.whl'))[-1]).namelist() \
+         if n.startswith('testutils/')])"     # must be empty
+```

mender_testkit-0.1.1/pyproject.toml

@@ -0,0 +1,64 @@
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "mender-testkit"
+version = "0.1.1"
+description = "Shared test infrastructure for the Mender integration test suites"
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "Apache-2.0" }
+
+# What this package's own code imports, at the floors mender-server's
+# backend/tests/requirements-integration.txt was tested against.
+#
+# Not a copy of that file: it is a lockfile listing the whole resolved tree, so
+# copying it here declared 25 transitive packages as direct dependencies and
+# pinned all 37 exactly. Both are wrong for a library -- the exact pins made this
+# uninstallable beside any consumer with its own opinion, and azure-iot-hub-api,
+# which nothing imports, dragged in azure-cli and constrained cryptography for
+# everyone. Consumers keep the exact set in their own lockfiles.
+#
+# 'kubernetes' is deliberately absent: testutils no longer imports it at module
+# scope, so a consumer running against docker compose does not need it. Install
+# the 'kubernetes' extra if you do run against a cluster.
+dependencies = [
+    "aiosmtpd>=1.4.6",
+    "cryptography>=47.0.0",
+    "docker>=7.1.0",
+    "filelock>=3.29.0",
+    "msgpack>=1.2.1",
+    "pymongo>=4.17.0",
+    "pytest>=9.0.3",
+    "redo>=3.0.0",
+    "requests>=2.34.2",
+    "stripe>=15.2.0",
+    "urllib3>=2.7.0",
+    "websockets>=16.0",
+]
+
+# So the PyPI page links back to the source. Without it there is no way to get
+# from a requirements entry to this repo.
+[project.urls]
+Repository = "https://github.com/mendersoftware/mender-testkit"
+
+[project.optional-dependencies]
+kubernetes = ["kubernetes>=36.0.2"]
+
+[project.entry-points.pytest11]
+mender_testkit = "mender_testkit.plugin"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+# The compose tree is data, not code, and its layout matters: docker-compose.yml
+# binds ./compose/certs and ./compose/config relative to the project directory.
+[tool.setuptools.package-data]
+# The explicit .env entry is not redundant: glob patterns do not match dotfiles,
+# so "data/**/*" silently skips it, and compose then falls back to
+# MENDER_IMAGE_TAG=latest instead of the "main" that .env sets.
+mender_testkit = ["data/**/*", "data/mender_server/.env"]
+
+[tool.black]
+extend-exclude = "^/src/mender_testkit/testutils/"

mender_testkit-0.1.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

mender_testkit-0.1.1/src/mender_testkit/__init__.py

@@ -0,0 +1,31 @@
+# Copyright 2026 Northern.tech AS
+#
+#    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.
+"""Shared test infrastructure for the Mender integration test suites."""
+
+import os
+
+# Traefik's routers match on Host as well as path, and the tests address the
+# ingress by container IP, so every request has to carry this. testutils defaults
+# it to "traefik", the name mender-server's own deployments answer to.
+#
+# Set here rather than in plugin.py because it has to happen before
+# testutils.api.client is imported -- that module reads it into a module-level
+# constant. Importing any submodule of this package runs this file first, whereas
+# plugin.py's own module-level imports already pull testutils in before its body
+# executes.
+os.environ.setdefault("GATEWAY_HOSTNAME", "docker.mender.io")
+
+from ._server_ref import MENDER_SERVER_REF  # noqa: E402
+
+__all__ = ["MENDER_SERVER_REF"]