History

Ondřej Míchal a24c2f6dc1 test/system: Bump secondary fedora image from 29 to 32 The fedora-toolbox:32 image is the first of images in the renamed toolbox image repository[0]. With the change we can drop the pull_image_old() function because it was kept only for the old image. Seems like newer version of ShellCheck checks the validity of variable names (SC2153). This caused a false positive, so I silenced it. [0] https://github.com/containers/toolbox/pull/615 https://github.com/containers/toolbox/pull/780		2021-05-31 12:28:24 +02:00
..
libs	test/system: Bump secondary fedora image from 29 to 32	2021-05-31 12:28:24 +02:00
001-version.bats	test/system: Use env var for invoking Toolbox	2021-05-26 22:52:40 +02:00
002-help.bats	test/system: Use env var for invoking Toolbox	2021-05-26 22:52:40 +02:00
101-create.bats	test/system: Bump secondary fedora image from 29 to 32	2021-05-31 12:28:24 +02:00
102-list.bats	test/system: Bump secondary fedora image from 29 to 32	2021-05-31 12:28:24 +02:00
103-run.bats	test/system: Use env var for invoking Toolbox	2021-05-26 22:52:40 +02:00
104-rm.bats	test/system: Use env var for invoking Toolbox	2021-05-26 22:52:40 +02:00
105-rmi.bats	test/system: Use env var for invoking Toolbox	2021-05-26 22:52:40 +02:00
README.md	test/system: Update documentation	2021-02-19 20:37:29 +01:00

README.md

System tests

These tests are built with BATS (Bash Automated Testing System).

The tests are meant to ensure that Toolbox's functionality remains stable throughout updates of both Toolbox and Podman/libpod.

Warning: The tests are not executed in an isolated environment. Running the tests will clear all podman state (delete all containers, images, etc).

Dependencies

bats
podman
skopeo
toolbox

These tests use a few standard libraries for bats which help with clarity and consistency. In order to use it you need to download them to the libs directory:

# Go to the Toolbox root folder
$ git clone https://github.com/bats-core/bats-assert test/system/libs/bats-assert
$ git clone https://github.com/bats-core/bats-support test/system/libs/bats-support

Convention

All tests should follow the nomenclature: [command]: <test description>...
When the test is expected to fail, start the test description with "Try to..."
When the test is to give a non obvious output, it should be put in parenthesis at the end of the title

Examples:

@test "create: Create the default container"
@test "rm: Try to remove a non-existent container"

All the tests start with a clean system (no images or containers) to make sure that there are no dependencies between tests and they are really isolated. Use the setup() and teardown() functions for that purpose.

How to run the tests

First, make sure you have all the dependencies installed.

Enter the toolbox root folder
Prepare container images. See playbooks/setup-env.yaml
Invoke command bats ./test/system/ and the test suite should fire up

Mocking of images is done to prevent potential networking issues and to speed up the cases.

Currently, this is done in a playbook that is a part of Toolbox's CI. In the future, this should be converted and become part of the test suite itself to allow local execution.

By default the test suite uses the system versions of podman and toolbox.

If you have a podman or toolbox installed in a nonstandard location then you can use the PODMAN and TOOLBOX environmental variables to set the path to the binaries. So the command to invoke the test suite could look something like this: PODMAN=/usr/libexec/podman TOOLBOX=./toolbox bats ./test/system/.