FerryDocs
ContributingTesting

Docker end-to-end tests

The tests that need Docker run only with FERRY_E2E=1. Without it, they print skipped and pass.

Edit on GitHub
not setsetA Docker testFERRY_E2E=1 ?the gateskippedthe test passesDocker daemonreal containers

Each test that needs Docker first reads the variable FERRY_E2E.

1 / 3

A test of this type is a .

Run all the suites

Terminal
cargo build -p ferryd                  # the CLI suite drives a real ferryd binary
FERRY_E2E=1 cargo test --workspace

Use a Docker daemon that you can share

The tests create containers, volumes, networks and images. They pull small public images and bind free local ports.

They never touch the resources of a Ferry server, because each test uses its own . But run them where this load is acceptable.

Run one suite

Give the crate and the name of the test.

Terminal
FERRY_E2E=1 cargo test -p ferry-engine --test e2e
FERRY_E2E=1 cargo test -p ferry-build --test build_e2e

The suites lists each name.

On this page