# TestShed

> A pytest plugin that hands your tests real Docker containers and Playwright browsers as fixtures.

## Table of Contents

### Guide

- [Getting Started](https://testshed.kloudkit.com/guide/getting-started.md): Install TestShed, point it at your image and write a pytest test against a live Docker container.
- [Images](https://testshed.kloudkit.com/guide/images.md): How TestShed gets the image your tests run against: tags and digests, and the pull, build, require and rebuild policies.
- [Containers](https://testshed.kloudkit.com/guide/containers.md): Get a shared or dedicated container per test, configure it with markers and defaults, start it on demand, or attach one that's already running.
- [Inside a Container](https://testshed.kloudkit.com/guide/inside-a-container.md): Run commands, read files and inspect processes inside a TestShed container, and customize the container class.
- [Readiness Probes](https://testshed.kloudkit.com/guide/readiness-probes.md): Wait until a TestShed container is ready with HTTP, log and shell probes, set suite-wide defaults and adjust timeouts.
- [Playwright Browsers](https://testshed.kloudkit.com/guide/playwright-browsers.md): Drive a Chromium browser that runs in a Playwright container, with no browser installed on the host.
- [Cleanup and Parallel Runs](https://testshed.kloudkit.com/guide/cleanup.md): How TestShed removes containers, volumes and networks, runs in parallel with pytest-xdist, and shows container logs on failure.

### Reference

- [Fixtures and Markers](https://testshed.kloudkit.com/reference/fixtures.md): Every fixture and marker TestShed registers, with its scope and what it returns.
- [Command-Line Options](https://testshed.kloudkit.com/reference/options.md): Every TestShed command-line option, with its default.