action #109434
closed
Added by jlausuch about 2 years ago.
Updated about 2 years ago.
Description
For BCI tests, include a module before running bci-tests.
Current execution is:
1) boot to desktop
2) host_configuration
3) bci_prepare
4) bci_test
New execution shall be:
1) boot to desktop
2) host_configuration
3) bci_prepare
4) bci_smoke
5) bci_test
This new module should execute a common code valid for any BCI image, for example: test_container_image which will work as a smoke test before running specific BCI tests.
ph03nix wrote:
The smoke test is actually happening within the BCI test module as GitHub Actions: https://github.com/dcermak/pytest_container/blob/main/.github/workflows/ci.yml
The reason for a new module is because there might be some cases where we don't have tests yet (e.g. Rust container coming), so, by providing that smoke test module is enough for automation until we have proper testing. Also, it could serve as a pre-condition before running the bci-tests suite. I don't mean writing something from scratch, but reusing what we already have, making sure we can do basic operations with the image under test (pull, create, etc).
Maybe instead of porting another integration test to openQA we could search for ways of improving the test coverage of the repo as a whole? e.g. adding openSUSE Leap and Tumbleweed there as well?
Improving the coverage as a whole is part of the epic https://progress.opensuse.org/issues/103323. I just need to create more tickets for that.
- Status changed from Workable to Rejected
I don't think this has relevance any more. The team is very proactively extending the coverage in BCI-tests directly and having new images without tests (e.g. PCP) is not happening every day, and we can increase the priority for those tickets.
Also available in: Atom
PDF