testshed

TestShedThe support crew for your test bench

Integration tests against real services, not mocks. Ask for a fixture, get a live Docker container or browser.

Get Started

GitHub

Containers as Fixtures

Request shed (or docker_sidecar) and run commands, read files and inspect processes inside a real container.

Playwright Browsers

Drive a browser running in a Playwright sidecar container.

Per-Test Configuration

Set env vars, volumes and readiness probes with markers, or defaults for the whole suite.

Lifecycle Handled

Images are resolved up front; containers and volumes are removed when the test finishes, even on failure.

Ready When You Are

HTTP, log and shell probes block until the container is ready, so tests don't race its startup.

Parallel Out of the Box

pytest -n auto works without setup; networks and labels are namespaced per xdist worker.

Why TestShed

Integration tests need real services (a database, an API, a browser), not mocks. Standing those up by hand means container code in conftest.py, flaky startup races, and leftover containers when a test crashes.

TestShed hands you a running Docker container, or a Playwright browser, as a fixture. Ask for shed and you get a live container: TestShed pulls or builds the image, waits for it to be ready, and removes everything when the test ends.

python

def test_container_is_alive(shed):
  assert shed.execute(["echo", "hello"]) == "hello"