Smoke test

Q: How deeply does Learn Docker in a Month of Lunches, Second Edition cover smoke test?

Explains the Docker Compose workflow and image choices, but stops short of detailed test design or browser automation.

As explained in Learn Docker in a Month of Lunches, Second Edition

A smoke test is a short, focused test that checks whether a software build or deployment performs its essential functions.

A smoke test is a short, focused end-to-end check that verifies an application build or deployment performs its essential functions. A typical script starts the application with Docker Compose, sends web requests, confirms that the application does something useful, and shuts the containers down. section 16.3

Use smoke tests to keep build and deployment feedback practical:

Run them after earlier pipeline stages establish reasonable confidence in the build. section 16.3
Choose local images while developing, or staging images when reproducing a tester-reported issue. section 16.3
Extend the script with fuller BDD or simulated-browser tests when basic checks are insufficient. section 16.3

Run the local smoke test

Use the images already built on the developer machine: ./smoke-test.ps1 -Local The same script can run without the flag to pull the latest staging images. section 16.3

How Learn Docker in a Month of Lunches, Second Edition covers it

Cover of Learn Docker in a Month of Lunches, Second Edition

liveBook manning.com

Read Learn Docker in a Month of Lunches, Second Edition on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Effective Platform EngineeringA smoke test is a shallow test that checks whether a system or service is broadly operational before deeper testing.
liveBook manning.com

Machine Learning System DesignA preliminary test that checks whether a system or component operates sufficiently to warrant further testing.
liveBook manning.com

Infrastructure as Code, Patterns and Practices: With examples in Python and TerraformA small, rapid set of tests that checks whether critical functionality remains operational after a change.

Compare how 4 books explain smoke test →

Related concepts

end-to-end testingkind of · End-to-end testing evaluates a complete system workflow across integrated components, from an external or user-relevant input to an observable outcome.
CPUuses · A CPU, or central processing unit, is a general-purpose hardware processor that executes computer instructions and performs computational operations.
Docker Composeuses · Docker Compose is a tool for defining and running applications composed of multiple containers through declarative configuration.
testkind of · A test is a procedure or check that evaluates behavior using specified inputs or evidence against expected results or criteria.
misconfigurationaddresses · A misconfiguration is an incorrect, unsuitable, or insufficiently restrictive system or application setting that causes unintended behavior, operational problems, or security exposure.
pipelineuses · A pipeline is an ordered or coordinated sequence of connected processing stages or tasks that passes data, work, or results toward an outcome.

This explainer was generated by Manning's knowledge graph from the text of Learn Docker in a Month of Lunches, Second Edition. The section links point to the parts of the book it draws on.