A black-box regression suite for the Labs64.IO platform, run through the gateway edge. Part of the Labs64.IO Ecosystem: the cross-module safety net: every test exercises the gateway, never a backend port.
Get started · Features · AI agents · Ecosystem · Documentation · labs64.io
Note
The suite needs a running Labs64.IO stack reachable through its gateway edge. By default it expects the local k3d addresses (http://gateway.localhost); override them with environment variables for any other address.
A change in one module can break another, and the break shows up at the edge: a wrong scope, a missing route, a payment that never reaches the audit log. This suite checks the platform the way a real client sees it, so you find out before your users do.
- Edge only. Every test goes through Traefik and the Auth Gateway, so authentication and authorization are always part of what is tested.
- Real tokens. Tokens are minted with exact scopes from the mock identity provider or Keycloak.
- Tagged and filterable.
smoke,regression,authand module tags let you run exactly the slice you need.
A good fit if
- You change a Labs64.IO module and want to know whether the platform as a whole still behaves.
- You deploy the platform and want a regression gate (smoke on every pull request, deeper runs nightly).
- You want proof that authorization is enforced for every route and scope.
Probably not what you need if
- You need unit tests for a module: those live in each module's repository.
- You have no running stack: the suite exercises a live gateway, so it needs one.
- Gateway-edge only: Traefik and the Auth Gateway are always in the path.
- Exact-scope tokens: minted from mock OIDC or Keycloak per test, so authorization is really exercised.
- Auth matrix: a generated suite checks every route against the scopes it should and should not accept.
- Module coverage: AuditFlow, Payment Gateway and the cross-module audit delivery probe.
- Tags:
smoke,regression,auth,flaky,not-ga,local-k8s-only. - CI-ready: a nightly workflow and a readiness gate that fails fast on unrecoverable pods.
| Area | What is checked |
|---|---|
| AuditFlow | Publishing events, validation errors and the authorization matrix |
| Payment Gateway | Provider lifecycle with the NoOp provider and the authorization matrix |
| Auth enforcement | A generated matrix across every route: the scopes it should and should not accept |
| Across modules | A payment appearing in AuditFlow (local cluster only, via correlation-scoped logs) |
Runs are tagged smoke, regression, auth, flaky, not-ga and local-k8s-only, so you can pick exactly the slice you need.
Run the narrowest slice of the suite before and after touching a module. The guide for AI agents covers authentication, retries and errors across all modules. Working on this repository with an agent? AGENTS.md describes the conventions, tags and how to add a module.
Tests is one module of the Labs64.IO Ecosystem. All modules are listed in the documentation.
We would love your help. New scenarios are the most useful contribution, especially for a module that has none yet. Fork the repository, make your change on a branch, run the checks described in AGENTS.md and open a pull request. Not sure whether an idea fits? Open an issue first and we will talk it through; that is a perfectly good way to start.
Everything in this repository is open source under the Apache License 2.0: you can use it, change it and ship it commercially. The core of the Labs64.IO Ecosystem is free forever; community modules are Apache-2.0 licensed.
Made by the Labs64 team and community.
