Imagine a car factory where every vehicle goes through a quality check before leaving the assembly line. Without testing, faulty cars could reach customers. In CI pipelines, testing with Docker is that quality check — ensuring applications run correctly inside containers before being deployed.

Testing Docker Foundations

1. Why Test with Docker in CI?

• Consistency: Tests run in the same environment as production.
• Isolation: Each test runs in its own container, avoiding conflicts.
• Automation: Tests are triggered automatically on code commits.
• Reliability: Bugs are caught early, reducing deployment failures.

2. Types of Tests in Docker CI

• Unit Tests: Validate individual functions or modules.
• Integration Tests: Ensure services work together correctly.
• End‑to‑End Tests: Simulate real user workflows.
• Performance Tests: Measure speed, scalability, and resource usage.

3. Workflow for Testing with Docker

1. Build Docker image in CI.
2. Run tests inside containers.
3. Capture logs and results.
4. Fail pipeline if tests fail.
5. Push image to registry only if tests pass.

The Hackers Notebook

• Testing inside containers ensures production‑like validation.
• Pipelines should fail fast if tests fail.
• Different test types (unit, integration, end‑to‑end) strengthen reliability.

Hands‑On Lab

Step 1: Write a Dockerfile for Testing

FROM node:14
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .
CMD ["npm", "test"]

Step 2: Run Tests in CI

docker build -t myapp:test .
docker run --rm myapp:test

Step 3: Example GitHub Actions Workflow

name: CI Pipeline

on:
  push:
    branches: [ "main" ]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout Code
        uses: actions/checkout@v2

      - name: Build Docker Image
        run: docker build -t myapp:test .

      - name: Run Tests
        run: docker run --rm myapp:test

Step 4: Example GitLab CI/CD Workflow

stages:
  - test

test:
  stage: test
  script:
    - docker build -t myapp:test .
    - docker run --rm myapp:test

Practice Exercise

1. Write a Dockerfile for a Python Flask app with pytest.
2. Configure a CI pipeline to:
   • Build the image.
   • Run unit tests inside the container.
   • Fail the pipeline if tests fail.
3. Add integration tests that check API endpoints.
4. Reflect on how containerized testing improves reliability.

Visual Learning Model

Testing with Docker in CI
   ├── Build → docker build
   ├── Run Tests → inside container
   ├── Capture Logs → test results
   └── Push Image → only if tests pass

The Hackers Notebook

Testing with Docker in CI ensures applications are validated in production‑like environments before deployment. By running unit, integration, and end‑to‑end tests inside containers, pipelines catch bugs early and guarantee reliability. Automated testing is the backbone of CI/CD quality assurance.