wbrawner/toolbox
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
toolbox/test/system
History
Debarshi Ray b9a0bd5f0c cmd/initContainer, test/system: Don't rely on D-Bus for /etc/timezone 
This is one more step towards enabling toolbox(1) to be run as root.
When invoked as 'sudo toolbox ...' there's no user or session D-Bus
instance available for the root user, which prevents the use of D-Bus
services like org.freedesktop.Flatpak.SessionHelper.

The code is forgiving to runtime errors when reacting to file system
events because it's not worth abruptly terminating the entry point
because of what might be a passing error. However, it's a lot stricter
when initially configuring the container because the failure mode isn't
as surprising for the user and it's worth starting from a valid state.

https://github.com/containers/toolbox/issues/267
2020-10-26 16:00:07 +01:00
..
001-version.bats playbooks, test/system: Test the Go implementation and update tests 2020-07-21 16:31:50 +02:00
002-help.bats playbooks, test/system: Test the Go implementation and update tests 2020-07-21 16:31:50 +02:00
101-list.bats test/system: Rework the tests 2020-02-18 14:00:59 +01:00
102-create.bats playbooks, test/system: Test the Go implementation and update tests 2020-07-21 16:31:50 +02:00
103-list.bats playbooks, test/system: Test the Go implementation and update tests 2020-07-21 16:31:50 +02:00
201-run.bats test/system: Rework check if toolbox started successfully 2020-10-24 17:32:15 +02:00
301-rm.bats playbooks, test/system: Test the Go implementation and update tests 2020-07-21 16:31:50 +02:00
302-rmi.bats test/system: Rework the tests 2020-02-18 14:00:59 +01:00
helpers.bash cmd/initContainer, test/system: Don't rely on D-Bus for /etc/timezone 2020-10-26 16:00:07 +01:00
README.md test/system: Rework the tests 2020-02-18 14:00:59 +01:00

README.md

System tests

These tests are built with BATS (Bash Automated Testing System). They are strongly influenced by the libpod project.

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

Structure

  • 0xx (Info)
    • Commands that are not dependent on the presence/number of containers or images. eg., version, help, etc..
  • 1xx (Initialization)
    • Commands (list, create) when Toolbox has not really been used, yet.
    • It tries to list an empty list, creates several containers (default one and several with custom names and images).
  • 2xx (Usage)
    • The created containers are used for the first time testing the initialization (CMD of the container).
    • Not all containers will be used because in the Cleanup phase we want to try removing containers in both running and not running states.
  • 3xx (Cleanup)
    • In this section the containers and images from the previous phases are removed.
    • There is a difference between removing running and not running containers. We need to check the right behaviour.

Convention

  • All tests that start with Try to.. expect non-zero return value.

How to run the tests

Make sure you have bats and podman with toolbox installed on your system.

Important Before you start the tests, you need to have present two images: the default fedora-toolbox image for your version of Fedora and the fedora-toolbox:29 image.

  • Enter the toolbox root folder
  • Invoke command bats ./test/system/ and the test suite should fire up

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/.