Actions
action #132449
closed[qe-core] remove fips test from qe-core aggregate job group
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Refactor/Code Improvements
Target version:
Start date:
2023-07-07
Due date:
% Done:
0%
Estimated time:
Difficulty:
Sprint:
QE-Core: August Sprint 23 (Aug 09 - Sep 04)
Tags:
Description
According to https://suse.slack.com/archives/C02D16TCP99/p1688721103274659 fips tests are maintained by security squad.
Known fips test in qe-core are:
- https://openqa.suse.de/tests/11529860 qam-regression-firefox-SLED_fips_kernelmode
- https://openqa.suse.de/tests/11529864 qam-regression-other_fips_kernelmode
- https://openqa.suse.de/tests/11530950 mau-extratests_fips_kernelmode
AC:
- Check for other places where we run fips test
- Sync with Security Squad to check if our tests are duplicate to theirs so we can just remove them or they should take over these as well to their job groups
- Remove fips test from Core Maintenance job group
Updated by szarate over 1 year ago
- Sprint set to QE-Core: July Sprint 23 (Jul 05 - Jul 26)
- Tags set to qe-core-july-sprint
- Status changed from New to Workable
- Target version set to QE-Core: Ready
Updated by szarate over 1 year ago
One thing, it is essential to stress the importance of this testsuite, as during the Vendor Affirmation, it was capable of catching quite few bugs that afaik, weren't catched by the more specialized tests the Security team runs... While maybe not all the test modules, some of them are touching parts that get affected when FIPS is enabled.
Updated by szarate about 1 year ago
- Sprint changed from QE-Core: July Sprint 23 (Jul 05 - Jul 26) to QE-Core: August Sprint 23 (Aug 09 - Sep 04)
Updated by rfan1 about 1 year ago
- Status changed from Workable to In Progress
Updated by rfan1 about 1 year ago
- Status changed from In Progress to Feedback
Actions