Paul Holzinger pointed out that when we invoke the podman tests inside the
passt testsuite, the way we point podman at the newly built pasta binary
is kind of indirect. It's therefore prudent to check that podman is
actually using the binary we expect it to - in particular that it is using
the binary built in this tree, not some system installed pasta binary.
Suggested-by: Paul Holzinger <pholzing(a)redhat.com>
Signed-off-by: David Gibson <david(a)gibson.dropbear.id.au>
---
test/pasta_podman/bats | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/test/pasta_podman/bats b/test/pasta_podman/bats
index 46a958a9..6b1c5751 100644
--- a/test/pasta_podman/bats
+++ b/test/pasta_podman/bats
@@ -13,7 +13,14 @@
htools git make go bats ip jq socat ./test/podman/bin/podman
+set PODMAN test/podman/bin/podman
+hout WD pwd
+
+test Podman pasta path
+
+hout PASTA_BIN CONTAINERS_HELPER_BINARY_DIR="__WD__" __PODMAN__ info --format
"{{.Host.Pasta.Executable}}"
+check [ "__PASTA_BIN__" = "__WD__/pasta" ]
+
test Podman system test with bats
-hout WD pwd
-host PODMAN="test/podman/bin/podman"
CONTAINERS_HELPER_BINARY_DIR="__WD__" bats
test/podman/test/system/505-networking-pasta.bats
+host PODMAN="__PODMAN__" CONTAINERS_HELPER_BINARY_DIR="__WD__" bats
test/podman/test/system/505-networking-pasta.bats
--
2.44.0