Skip to content

Commit 3ec055f

Browse files
cgwaltersjmarrero
authored andcommitted
tests: Validate ESP-related error in no-ESP failure test
The no-ESP test only checked for a non-zero exit code, which would also pass if podman itself failed for unrelated reasons. Check that the output contains "ESP" to confirm the right failure mode. Assisted-by: OpenCode (Claude Opus 4) Signed-off-by: Colin Walters <walters@verbum.org>
1 parent 11ddd18 commit 3ec055f

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

tmt/tests/booted/test-multi-device-esp.nu

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -404,6 +404,9 @@ def test_no_esp_failure [] {
404404
} | complete)
405405

406406
assert ($result.exit_code != 0) "Expected install to fail with no ESP partitions"
407+
# Verify the failure is ESP-related, not an unrelated podman/runtime error
408+
let combined = $"($result.stdout)\n($result.stderr)"
409+
assert ($combined | str contains "ESP") $"Expected ESP-related error message, got: ($combined | str substring 0..200)"
407410
print $"Install failed as expected with exit code ($result.exit_code)"
408411
} catch {|e|
409412
cleanup $vg_name [$loop1, $loop2] $mountpoint

0 commit comments

Comments
 (0)