Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

e2e-test: assert job condition on job tests #1969

Merged

Conversation

mkulke
Copy link
Collaborator

@mkulke mkulke commented Jul 31, 2024

We have elaborate condition checks on a job's pods, but we do not test the job status itself, which will produce wrong test results. A test for job that always fails (cmd: /bin/false) will pass.

This keeps the current assertions in-place, but makes the test fail on a failed job status

@mkulke mkulke added the test_e2e_libvirt Run Libvirt e2e tests label Jul 31, 2024
We have elaborate condition checks on a job's pods, but we do not test
the job status itself, which will produce wrong test results. A test
for job that always fails (cmd: /bin/false) will pass.

This keeps the current assertions in-place, but makes the test fail on a
failed job status

Signed-off-by: Magnus Kulke <magnuskulke@microsoft.com>
@mkulke mkulke force-pushed the mkulke/add-jobstatus-assertion branch from f163116 to e0722c1 Compare August 1, 2024 07:09
Copy link
Member

@bpradipt bpradipt left a comment

Choose a reason for hiding this comment

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

/lgtm

@wainersm wainersm merged commit 09c6c83 into confidential-containers:main Aug 5, 2024
29 checks passed
@mkulke mkulke deleted the mkulke/add-jobstatus-assertion branch August 5, 2024 20:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test_e2e_libvirt Run Libvirt e2e tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants