History

Ondřej Míchal 6c86cabbe5 cmd/root: Make 'toolbox' create or fall back to a container if possible This makes 'toolbox', without any commands specified, behave a lot like 'toolbox enter'. When there aren't any toolbox containers, it will offer to create a new container matching the same parameters passed to the command. If there's just one toolbox container available, then it will fall back to it. This makes the command line interface a lot similar to that of github.com/coreos/toolbox, which makes things easier for those switching over from it. Some changes by Debarshi Ray. https://github.com/containers/toolbox/pull/811		2021-06-29 15:27:56 +02:00
..
libs	test/system: Fix variable dereference	2021-06-21 18:42:21 +02:00
000-setup.bats	cmd/list, test/system: Ignore the problem of UBI not being listed	2021-06-19 01:12:08 +02:00
001-version.bats	test/system: Use env var for invoking Toolbox	2021-05-26 22:52:40 +02:00
002-help.bats	cmd/root: Make 'toolbox' create or fall back to a container if possible	2021-06-29 15:27:56 +02:00
101-create.bats	test/system: Decouple image caching from Zuul	2021-06-01 00:41:20 +02:00
102-list.bats	cmd/list: Support images without names	2021-06-22 21:58:29 +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
999-teardown.bats	test/system: Decouple image caching from Zuul	2021-06-01 00:41:20 +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/.