Files
podman/test/system/620-option-conflicts.bats
Ed Santiago 29d18079cb [systests] new defer-assertion-failure
Some system tests run deep loops:

  for x in a b c; do
    for y in d e f; do
        .... check condition $x + $y

Normally, if one of these fails, game over. This can be frustrating
to a developer looking for failure patterns.

Here we introduce a new defer-assertion-failure function, meant
to be called before loops like these. Everything is the same,
except that tests will continue running even after failure.

When test finishes, or if test runs immediate-assertion-failure,
a new message indicates that multiple tests failed:

  FAIL: X test assertions failed. Search for 'FAIL': above this line.

Signed-off-by: Ed Santiago <santiago@redhat.com>
2023-11-27 11:31:29 -07:00

54 lines
1.8 KiB
Bash

#!/usr/bin/env bats -*- bats -*-
#
# options that cannot be set together
#
load helpers
@test "options that cannot be set together" {
skip_if_remote "not much point testing remote, and container-cleanup fails anyway"
tests="
create,run | --cpu-period=1 | --cpus=2 | $IMAGE
create,run | --cpu-quota=1 | --cpus=2 | $IMAGE
create,run | --no-hosts | --add-host=foo:1.1.1.1 | $IMAGE
create,run | --userns=bar | --pod=foo | $IMAGE
container cleanup | --all | --exec=foo
container cleanup | --exec=foo | --rmi | foo
"
# Run all tests, continue even if any fail
defer-assertion-failures
# FIXME: parse_table is what does all the work, giving us test cases.
while read subcommands opt1 opt2 args; do
opt1_name=${opt1%=*}
opt2_name=${opt2%=*}
readarray -d, -t subcommand_list <<<$subcommands
for subcommand in "${subcommand_list[@]}"; do
run_podman 125 $subcommand $opt1 $opt2 $args
is "$output" "Error: $opt1_name and $opt2_name cannot be set together" \
"podman $subcommand $opt1 $opt2"
# Reverse order
run_podman 125 $subcommand $opt2 $opt1 $args
is "$output" "Error: $opt1_name and $opt2_name cannot be set together" \
"podman $subcommand $opt2 $opt1"
done
done < <(parse_table "$tests")
# Different error message; cannot be tested with the other ones above
for opt in arch os; do
for cmd in create pull; do
run_podman 125 $cmd --platform=foo --$opt=bar sdfsdf
is "$output" "Error: --platform option can not be specified with --arch or --os" \
"podman $cmd --platform + --$opt"
done
done
}
# vim: filetype=sh