toolbox/test/system/meson.build

test_system = files(
  '201-ipc.bats',
  '203-network.bats',
  '206-user.bats',
  '210-ulimit.bats',
  '211-dbus.bats',
)

if shellcheck.found()
  test('shellcheck test/system', shellcheck, args: [test_system])
endif
test/system: Test that networking works Note that 'run --keep-empty-lines' counts the trailing newline on the last line as a separate line. https://github.com/containers/toolbox/pull/1325 2023-06-30 11:59:46 +00:00			`test_system = files(`
test/system: Test that interprocess communication works Note that 'run --keep-empty-lines' counts the trailing newline on the last line as a separate line. https://github.com/containers/toolbox/pull/1326 2023-06-30 17:35:15 +00:00			`'201-ipc.bats',`
test/system: Test that networking works Note that 'run --keep-empty-lines' counts the trailing newline on the last line as a separate line. https://github.com/containers/toolbox/pull/1325 2023-06-30 11:59:46 +00:00			`'203-network.bats',`
test/system: Test that group and user IDs work These tests assume that the group and user information on the host operating system can be provided by different plugins for the GNU Name Service Switch (or NSS) functionality of the GNU C Library. eg., on enterprise FreeIPA set-ups. However, it's expected that everything inside the Toolbx container will be provided by /etc/group, /etc/passwd, /etc/shadow, etc.. While /etc/group and /etc/passwd can be read by any user, /etc/shadow can only be read by root. However, it's awkward to use sudo(8) in the test cases involving /etc/shadow, because they ensure that root and $USER don't need passwords to authenticate inside the container, and sudo(8) itself depends on that. If sudo(8) is used, the test suite can behave unexpectedly if Toolbx didn't set up the container correctly. eg., it can get blocked waiting for a password. Hence, 'podman unshare' is used instead to enter the container's initial user namespace, where $USER from the host appears as root. This is sufficient because the test cases only need to read /etc/shadow inside the Toolbx container. https://github.com/containers/toolbox/pull/1355 2023-08-12 12:26:22 +00:00			`'206-user.bats',`
test/system: Test the resource limits The following caveats must be noted: * Podman sets the Toolbx container's soft limit for the maximum number of open file descriptors to the host's hard limit, which is often greater than the host's soft limit [1]. * The ulimit(1) options -P, -T, -b, and -k don't work on Fedora 38 because the corresponding resource arguments for getrlimit(2) are absent from the operating system. These are RLIMIT_NPTS, RLIMIT_PTHREAD, RLIMIT_SBSIZE and RLIMIT_KQUEUES respectively. [1] https://github.com/containers/podman/issues/17681 https://github.com/containers/toolbox/issues/213 2023-06-30 19:53:37 +00:00			`'210-ulimit.bats',`
test/system: Test that D-Bus works https://github.com/containers/toolbox/issues/1330 Signed-off-by: Nieves Montero <nmontero@redhat.com> 2023-07-27 12:43:28 +00:00			`'211-dbus.bats',`
test/system: Test that networking works Note that 'run --keep-empty-lines' counts the trailing newline on the last line as a separate line. https://github.com/containers/toolbox/pull/1325 2023-06-30 11:59:46 +00:00			`)`

			`if shellcheck.found()`
			`test('shellcheck test/system', shellcheck, args: [test_system])`
			`endif`