Project

General

Profile

action #43856

coordination #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

Added by riafarov almost 3 years ago. Updated 21 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA - 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:
1) Different architectures (to see that package is available)
2) Online vs offline (as we might get release notes from DVD)
3) Addons (source doesn't matter, either all-packages DVD, or ftp url, or as module)

Acceptance criteria

  1. Coverage remains same for relevant scenarios
  2. Release notes are not tested in every installation
  3. 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.


Related issues

Blocks openQA Tests - action #14774: [sle][functional][yast][y] Disconnected installation: grab release notes while a system is not plugged into network takes too long Resolved2016-11-14

History

#1 Updated by riafarov almost 3 years ago

  • Description updated (diff)

#2 Updated by okurz almost 3 years ago

  • Due date set to 2018-12-18
  • Category set to Enhancement to existing tests
  • Target version set to Milestone 21

#3 Updated by riafarov almost 3 years ago

  • Description updated (diff)

#4 Updated by riafarov almost 3 years ago

  • Description updated (diff)
  • Estimated time set to 5.00 h

#5 Updated by riafarov almost 3 years ago

  • Due date changed from 2018-12-18 to 2019-01-29
  • Target version changed from Milestone 21 to Milestone 22

No capacity.

#6 Updated by riafarov almost 3 years ago

  • Due date changed from 2019-01-29 to 2019-01-15

#7 Updated by JERiveraMoya over 2 years ago

  • Assignee set to JERiveraMoya

#8 Updated by JERiveraMoya over 2 years ago

  • Status changed from Workable to In Progress

#9 Updated by JERiveraMoya over 2 years ago

  • Status changed from In Progress to Feedback

PR: Schedule release notes when relevant
I got a little confuse by release_note origin here, we are referring only to release note, right? not the checking of the package or a combination of both? Answered that it is only about the test module testing the dialog.

#10 Updated by JERiveraMoya over 2 years ago

For example, we can introduce the variable for the following groups:
Functional & YaST:create_hdd_gnome
create_hdd_textmode

HPC: create_hdd_hpc_textmode
HA: create_hdd_ha_textmode
SLES for SAP Applications:create_hdd_sles4sap_gnome
create_hdd_sles4sap_textmode
For openSUSE is not currently implemented to check the dialog, so the new variable is not taken into account.

#11 Updated by JERiveraMoya over 2 years ago

  • Status changed from Feedback to In Progress

Added CHECK_RELEASENOTES=1 to test suites mentioned above plus: create_hdd_minimal_base+sdk and create_hdd_gnome+we.

#12 Updated by okurz over 2 years ago

  • Blocks action #14774: [sle][functional][yast][y] Disconnected installation: grab release notes while a system is not plugged into network takes too long added

#13 Updated by JERiveraMoya over 2 years ago

  • Status changed from In Progress to Feedback

Waiting for next build to verify the change.

#14 Updated by JERiveraMoya over 2 years ago

  • Status changed from Feedback to Resolved

#15 Updated by okurz 21 days ago

  • Due date deleted (2019-01-15)

Also available in: Atom PDF