This part of the documentation, which is mostly prose, begins with some
background information about goodplay, then focuses on step-by-step
instructions for digging deeper into what can be accomplished with goodplay.

when using docker-compose.yml files in tests with referenced Dockerfiles,
a build is triggered before bringing up the containers (NOT attempting to
pull the latest base image as image might be only available locally)

support become_user with Docker’s native user management when running
privilege escalation task against Docker Compose environment thus sudo
is not required in a Docker container anymore; this may change in a future
version once Ansible supports su with Docker connection plugin

use Docker Compose for defining environments instead of reinventing the
wheel, thus bringing you all the latest and greatest features of
Docker Compose (e.g. running from Dockerfile, custom networks, custom
entrypoints, shared volumes, and more)

support running any test playbook (not only Ansible role playbooks) against
multiple environments

test tasks now run in check mode when supported by module

remove goodplay_image and goodplay_platform support from inventory
files

remove .goodplay.yml support as it has only been used for defining
platform-name-to-docker-image mapping which is now handled by Docker Compose