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: Add fixture tests to CI #1406

Closed
lentzi90 opened this issue Oct 30, 2023 · 3 comments · Fixed by #1437
Closed

E2e: Add fixture tests to CI #1406

lentzi90 opened this issue Oct 30, 2023 · 3 comments · Fixed by #1437
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@lentzi90
Copy link
Member

User Story

As a developer I would like to ensure that the BMO e2e tests flexible enough to run in many different environments, including on actual hardware.

Detailed Description

We rely on libvirt, VBMC/sushy-tools and similar for CI. This introduces the risk that the e2e tests become dependent on the platform.
As a way to mitigate this, I initially made the e2e tests so that they can be run with the fixture provider (test-mode). This way of running the tests does not use libvirt, VBMC or any similar tools, which means it can be used as a way of ensuring that we do not depend on them. However, we do not run the fixture provider tests in CI currently. This issue is for adding the fixture tests to CI to ensure that we do not accidentally tie the tests to the CI platform.

Anything else you would like to add:

The tests with fixture provider is quite light weight. We could consider running them in a github action. Otherwise Jenkins is always an option.

/kind feature

@metal3-io-bot metal3-io-bot added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Oct 30, 2023
@lentzi90
Copy link
Member Author

/triage accepted

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Oct 30, 2023
@lentzi90
Copy link
Member Author

/cc @Rozzii

@maxrantil
Copy link
Member

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants