robotframework-okw-env
Driver-agnostic environment abstraction for OKW4Robot.
Deutsche Version: README_de.md
What
One set of keywords (StartEnvironment, StopEnvironment, WaitForReady, ...)
to build, run, and tear down ephemeral test environments — regardless of the
underlying provider (Docker, Proxmox, Kubernetes, ...).
Why — Signal vs. NOISE
Test code should describe what the test needs, not how infrastructure is provisioned. Docker Compose syntax, Proxmox API calls, and Kubernetes manifests are NOISE — the test only needs:
ENV_Start WebShop
ENV_Start PostgresDB version=17
ENV_BuildAndRun
ENV_WaitForReady WebShop
Architecture
┌──────────────────────────────┐
│ Robot Framework Test │ ENV_Start, ENV_Stop, ...
├──────────────────────────────┤
│ okw-env (this library) │ Keywords, YAML loader, provider contract
├──────────────┬───────────────┤
│ okw-env- │ okw-env- │ Provider plugins
│ docker │ proxmox │
├──────────────┼───────────────┤
│ Docker │ Proxmox │ Underlying APIs
│ Compose │ VE API │
└──────────────┴───────────────┘
Install
pip install robotframework-okw-env
Plus one or more provider plugins:
pip install robotframework-okw-env-docker
pip install robotframework-okw-env-proxmox
Component YAML
Environment components are defined in YAML — no infrastructure code in tests:
PostgresDB:
provider: docker
image: postgres
version: "17"
port: 5432
env:
POSTGRES_DB: testdb
POSTGRES_PASSWORD: test123
healthcheck: "pg_isready -U postgres"
Minimal Example
*** Settings ***
Library okw4robot.library.OKW4RobotLibrary WITH NAME OKW
*** Test Cases ***
Order With Payment Gateway
# Phase 0 — Environment
ENV_Start WebShop
ENV_Start PostgresDB
ENV_Start PaymentGW
ENV_BuildAndRun
ENV_WaitForReady WebShop
# Phase 1-4 — Test
StartApp MyShop
SetValue Article Laptop
ClickOn Order
VerifyValue Status Paid
StopApp
# Phase 5 — Teardown
ENV_Stop
Key Benefits
- Isolation — Each test gets its own environment, enabling parallel execution
- Ephemeral — Environments exist only during test execution, no security concerns
- Combinable — Version matrix testing via templates
- Provider-agnostic — Same test, different infrastructure
Provider Plugins
| Plugin | Repository |
|---|---|
| okw-env-docker | Docker Compose |
| okw-env-proxmox | Proxmox VE |
Metadata
Release files for robotframework-okw-env 0.1.0
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 |
|---|---|---|---|---|
| robotframework_okw_env-0.1.0.tar.gz | 11.6 kB | Without provenance | Details for robotframework_okw_env-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| robotframework_okw_env-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for robotframework_okw_env-0.1.0-py3-none-any.whl |
Total release size: 21.2 kB
Release files / robotframework_okw_env-0.1.0.tar.gz
| Download URL | robotframework_okw_env-0.1.0.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a9a8a752e12ac209beda8f02d4a12db716e7b8691fac4cebd6ac102bd67bcfd4
|
|
BLAKE2b-256 checksum How to use checksums |
1f81f8fb34adf6b2d327a95284564ddaaae63b1427386d303c1a10f6c55885e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / robotframework_okw_env-0.1.0-py3-none-any.whl
| Download URL | robotframework_okw_env-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5b0b0c2597fa3ee21d879d178619458b4cdadd5d7f4cdcd114bfc9b20b0e7bfd
|
|
BLAKE2b-256 checksum How to use checksums |
f8585a88c8749cab4ce384ec3bfe983b84cb9bc56cf48c5884b7fe1f0dcbb95b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for robotframework-okw-env 0.1.0
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.