Docker logo

Docker

FreemiumPopular

Container platform for packaging applications and creating isolated, reproducible test environments.

Visit websiteGitHub

Pricing

Freemium

Type

Automation

Community

// VERDICT

Reach for Docker when you want reproducible, disposable test environments and dependency parity across local/CI/prod. Skip it only when you don't need containerisation or can't run containers in your environment.

Best for

Containerising applications and their dependencies into reproducible images - for QA, the key to consistent test environments, throwaway dependencies and parity between local, CI and prod.

Avoid when

You don't need environment reproducibility, can't run containers, or your stack is trivially simple.

CI/CD fit

Docker images in CI · docker-compose for test deps · parity local/CI/prod

Team fit

Dev/QA teams · SDETs needing reproducible envs · CI-driven testing

Setup

Easy

Maintenance

Low

Learning

Beginner

Licence

Freemium

// BEST FOR

  • Reproducible test environments via images
  • Spinning up dependencies (DBs, queues) with compose
  • Parity between local, CI and production
  • Disposable, isolated environments per test run
  • Packaging the system under test consistently
  • Eliminating 'works on my machine' for tests

// AVOID WHEN

  • You don't need environment reproducibility
  • You can't run containers in your environment
  • Your stack is trivially simple
  • Heavy GUI/desktop apps that resist containerisation
  • You want full orchestration only (use Kubernetes)
  • Minimal tooling is the goal

// QUICK START

# Dockerfile + docker-compose.yml for app + dependencies
docker compose up -d        # spin up test deps
docker build -t app . && docker run app npm test

// ALTERNATIVES TO CONSIDER

ToolChoose it when
KubernetesYou need orchestration of many containers/services.
TestcontainersYou want throwaway real dependencies inside your test code.
OpenShiftYou want an enterprise Kubernetes platform.

// FEATURES

  • Dockerfile-based image builds with layer caching
  • Docker Compose for multi-service local stacks
  • Volume and network primitives for stateful test setups
  • Docker Hub registry for sharing and reusing images
  • BuildKit for faster, parallel image builds

// PRIMARY USE CASES

  1. REPRODUCIBLE TEST ENVIRONMENTS

    Package an app and its dependencies into a single image so tests run identically on dev, CI, and prod.

  2. EPHEMERAL SERVICES

    Spin up Postgres, Redis, or any service in a container per test run so suites don't share polluted state.

  3. MULTI-SERVICE STACKS

    Compose multi-service stacks via Docker Compose and exercise them end-to-end in CI.

// PROS

  • De facto standard for containerised dev and test workflows
  • Compose files make a full app stack reproducible in seconds
  • Free for individual and small-team use
  • Excellent CI/CD integration across every major provider

// CONS

  • Docker Desktop now requires a paid subscription for larger orgs
  • Performance overhead on macOS and Windows via the VM layer
  • Image bloat is easy without disciplined Dockerfiles

// EXAMPLE QA WORKFLOW

  1. Install Docker

  2. Write a Dockerfile for app/test image

  3. Define dependencies in docker-compose

  4. Run tests inside containers

  5. Use the same images in CI for parity

  6. Maintain images and pin versions

// RELATED QA.CODES RESOURCES

Cheat sheets