summaryrefslogtreecommitdiff
path: root/vendor/github.com/pkg
diff options
context:
space:
mode:
authorOndřej Míchal <harrymichal@seznam.cz>2020-09-09 17:32:16 +0200
committerOndřej Míchal <harrymichal@seznam.cz>2020-10-09 16:32:47 +0200
commita1e1a3af71ac1bb650412c3236fab835bdc21cdc (patch)
treed13da39d780a192877c78ec7714275b316905702 /vendor/github.com/pkg
parent71d675a164ee64111db1a9214673a3498b3aa123 (diff)
downloadpodman-a1e1a3af71ac1bb650412c3236fab835bdc21cdc.tar.gz
podman-a1e1a3af71ac1bb650412c3236fab835bdc21cdc.tar.bz2
podman-a1e1a3af71ac1bb650412c3236fab835bdc21cdc.zip
tests/e2e: Add Toolbox-specific test cases
In the past, Toolbox[0] has been affected by several of Podman's bugs/changes of behaviour. This is one of the steps to assure that as Podman progresses, Podman itself and subsequently Toolbox do not regress. One of the other steps is including Toolbox's system tests in Podman's gating systems (which and to what extent is yet to be decided on). The tests are trying to stress parts of Podman that Toolbox needs for its functionality: permission to handle some system files, correct values/permissions/limits in certain parts, management of users and groups, mounting of paths,.. The list is most likely longer and therefore more commits will be needed to control every aspect of the Toolbox/Podman relationship :). Some test cases in test/e2e/toolbox_test.go rely on some tools being present in the base image[1]. That is not the case with the common ALPINE image or the basic Fedora image. Some tests might be duplicates of already existing tests. I'm more in favour of having those duplicates. Thanks to that it will be clear what functionality/behaviour Toolbox requires. [0] https://github.com/containers/toolbox [1] https://github.com/containers/toolbox/#image-requirements Signed-off-by: Ondřej Míchal <harrymichal@seznam.cz>
Diffstat (limited to 'vendor/github.com/pkg')
0 files changed, 0 insertions, 0 deletions