Actions
action #43856
closedcoordination #40484: [qe-core][functional][epic] Move different checks to separate test suites not to affect other functional tests
[functional][y] Verify release notes only in relevant scenarios
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA (private) - Milestone 22
Start date:
2018-11-15
Due date:
% Done:
0%
Estimated time:
5.00 h
Difficulty:
Description
Motivation¶
See motivation in the parent ticket.
We validate release notes in each installation, which is a bit too much. Relevant cases are following:
- Different architectures (to see that package is available)
- Online vs offline (as we might get release notes from DVD)
- Addons (source doesn't matter, either all-packages DVD, or ftp url, or as module)
Acceptance criteria¶
- Coverage remains same for relevant scenarios
- Release notes are not tested in every installation
- Change in behavior is communicated to other teams, so release notes are also tested for the products QSF is not responsible for (e.g. SLED, SLES4SAP, etc.)
Suggestion¶
Simplest implementation would be to introduce variable and validate Release Notes in relevant test suites only.
Please, check https://openqa.suse.de/tests/2260719 as we test release note origin there.
Let's address this for SLE only for the start, considering applying same approach for openSUSE.
Actions