Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 21 additions & 1 deletion base/images/images.toml
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,10 @@ runtime-package-management = true
[images.container-base]
description = "Container Base Image"
definition = { type = "kiwi", path = "container-base/container-base.kiwi", profile = "core" }
tests.test-suites = [{ name = "static-image-checks" }]
tests.test-suites = [
{ name = "static-image-checks" },
{ name = "container-bvt-tests" },
]
Comment thread
bhagyapathak marked this conversation as resolved.

[images.container-base.capabilities]
machine-bootable = false
Expand Down Expand Up @@ -61,4 +64,21 @@ extra-args = [
"--image-path", "{image-path}",
"--image-name", "{image-name}",
"--capabilities", "{capabilities}",
"-m", "not runtime_container_tests",
]

# Container Business Validation Tests (BVT)
[test-suites.container-bvt-tests]
type = "pytest"
description = "Container BVT: runtime validation of system resources, networking, filesystem, and package management"

[test-suites.container-bvt-tests.pytest]
working-dir = "tests"
install = "pyproject"
test-paths = ["cases/container-base/runtime/test_container_bvt.py"]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just specify the whole runtime/ dir? But also, it's odd that the naming of the test suite implies it should be runnable against any container, but it's got a hard-coded reference to container-base in particular.

extra-args = [
"--image-path", "{image-path}",
"--image-name", "{image-name}",
"--capabilities", "{capabilities}",
"-v", "-s"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it makes sense to hard-code -v or -s in the test case, as that's a generic pytest option that the adapter for running pytest-based tests should be able to handle. azldev already does something like that, where it translates its own verbosity options to --log-cli-level. We could refine that, but it doesn't seem like should be test suite specific.

]
Loading