ory/dockertest

Write better integration tests! Dockertest helps you boot up ephermal docker images for your Go tests with minimal work.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 15th, 2026
Created on March 19th, 2015
Open Issues & Pull Requests: 14 (+0)
GitHub issues: Enabled
Number of forks: 270
Total Stargazers: 4,525 (+0)
Total Subscribers: 29 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.1 days
Mean response time: 177.3 days
90th percentile: 814.5 days
Tracked items: 17

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 444 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (14)
  • stale (4)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Dockertest is a Go library that simplifies writing integration tests by automating the provisioning and teardown of ephemeral Docker containers.

The problem it addresses is the difficulty of testing application services that depend on external systems like databases. Rather than maintaining complex mocks that break with schema or API changes, Dockertest lets developers spin up real Docker containers for testing and destroy them afterward. The tool handles container lifecycle management, configuration, readiness checks, and cleanup with minimal boilerplate code, supporting any Docker image from Docker Hub or a custom Dockerfile across Windows, macOS, and Linux.

Dockertest suits projects that need reliable integration tests against real services. It works well for teams already using Docker and testing Go applications that depend on databases or other containerized services. The library is particularly valuable when schema or API changes would otherwise require extensive mock rewrites. Version 4 introduced automatic container reuse across test runs, which speeds up test execution by avoiding repeated container creation.

The project maintains active development with regular updates to its codebase. The maintainers have invested in reducing external dependencies by adopting a lightweight Docker client implementation. Documentation is comprehensive, covering pool creation, container configuration, readiness waiting strategies, command execution, networking, and CI integration patterns for GitHub Actions and GitLab CI. The project provides clear upgrade guidance for users migrating from earlier versions.