Testing
Hangar: on-demand remote GitLab environments join the platform
Hangar provisions isolated, production-like GitLab environments on a shared cluster for Caproni to deploy into, reachable by a person or an agent, and ends them on a TTL. What it does today, where the boundary with Caproni sits, and where it is going.
Testing on Theseus: ownership, ordering, and the release gate
A new entry point for testing guidance: who owns tests and release gating, which layer to reach for first, and links to the GitLab-wide guides.
Get a remote GitLab environment with Hangar
Stand up your own production-like GitLab on the shared Hangar host with Caproni's vcluster driver, check that it is yours and not public, set its lifetime, and tear it down.
Test a modular feature in isolation
Acceptance-test your service against in-process fakes and Caproni-provided infrastructure — no monolith, no neighbouring services.
Testing on Theseus
Where testing a modular feature starts: who owns your tests, which layer to reach for first, and what the release gate is for, with links to the GitLab-wide testing guides.
Modular feature test isolation
The strategy behind the default testing layer: test each modular feature against its contracts, with fakes for service dependencies, real infrastructure from Caproni, and no spun-up world.