coordination #91142: [qe-core][epic] add product QE exclusive tests to QEM runs to increase coverage
[qe-core][qem] Add existing console Product QE tests to QEM
After comparing test coverage of SLE 15 SP2 and SP3 in opneQA I identified several tests that are exclusive to either pre-release or post-release testing and could be easily used to increase our coverage just by using what we already have.
It is possible that are some errors and some of the tests from the list are already being used. It is also just my opinion, therefor review from other colleagues is more then welcome.
These are the console tests that run only before release and could be used also after the release (product QE -> QEM)
tests/console/btrfsmaintenance.pm (runs on mau-filesystem)
- AC1 All aforementioned tests are scheduled in maintenance tests (aggregated or incidents), in their corresponding categories (When in doubt ask in qe-core channel)
- AC2 Cross reference with openqa-module-mapper to figure what's already done and what's running where.
- AC3 If a test module needs black magic to work (i.e, takes more than half a day), a corresponding ticket is created and it is removed from this list.
Please stop blindly adding broken tests.
Why do you really think that they were added blindly?
In the [PR], you have mentioned two failed jobs:
- 12-sp5 in s390x failed today. As you can see from the VRs that are provided in the description of the pr, this test has passed https://openqa.suse.de/tests/6143653#step/journald_fss/20 .
- As for the 12-sp2 x86_84 fail, it was one case that I missed running, which as far as I can see from the fail message, the test installs
openvswitch, then tries to start the service and then it fails, which doesn't seem at all to me like a broken test.
In any case, I had also no intention to ignore any issues that they would happen in the 16 jobgroups/sle-versions that they were scheduled.