coordination #40484
open[qe-core][functional][epic] Move different checks to separate test suites not to affect other functional tests
100%
Description
Motivation¶
We test some UI features which affect many and sometimes all test suites. Best example is test for proceeding without accepting license. This is important check, whereas if we want to know overall status of the build, will break all the tests.
In case it's located in a separate test suite, we could still validate this functionality, but don't affect other tests.
Same is valid for scenarios when some problem makes testing complex, e.g. screensaver. If we have separate test covering screensaver, we have low risk of missing something and have better stability as do not have to apply additional actions for screensaver detection.
installer_extended is one of test suites which can be used for UI changes https://openqa.suse.de/tests/2163370
Acceptance criteria¶
- All such non-functional checks are identified and either addressed using this ticket, or as a sub-ticket
- Only relevant tests are affected when some feature is broken
Updated by okurz about 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: lvm
https://openqa.suse.de/tests/2086886
Updated by okurz about 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: autoyast_gnome_no_product_reg
https://openqa.suse.de/tests/2131049
Updated by okurz about 6 years ago
- Due date changed from 2018-11-20 to 2018-12-18
due to changes in a related task
Updated by riafarov about 6 years ago
- Due date changed from 2018-12-18 to 2019-01-29
due to changes in a related task
Updated by riafarov about 6 years ago
- Due date changed from 2019-01-29 to 2019-01-15
due to changes in a related task
Updated by okurz almost 6 years ago
- Due date changed from 2019-01-15 to 2019-02-12
due to changes in a related task
Updated by okurz almost 6 years ago
- Status changed from New to Blocked
- Assignee set to okurz
I think the ticket is refined enough, see the subtasks. Blocking by subtasks.
Updated by okurz almost 6 years ago
- Due date changed from 2019-02-12 to 2019-05-07
due to changes in a related task
Updated by okurz almost 6 years ago
- Target version changed from Milestone 22 to Milestone 24
-> subtickets
Updated by okurz almost 6 years ago
- Target version changed from Milestone 24 to Milestone 25
Updated by okurz almost 6 years ago
@riafarov should we resolve the epic with one u-team subtask still open or do you think we need to do more (with according subtasks) to have the epic sufficiently covered?
Updated by okurz almost 6 years ago
- Due date changed from 2019-05-07 to 2019-06-04
due to changes in a related task
Updated by okurz almost 6 years ago
- Assignee changed from okurz to riafarov
@riafarov to track as stand-in PO
Updated by riafarov over 5 years ago
- Due date changed from 2019-06-04 to 2019-02-12
due to changes in a related task
Updated by mgriessmeier over 5 years ago
- Subject changed from [functional][y][epic] Move different checks to separate test suites not to affect other functional tests to [functional][y][u][epic] Move different checks to separate test suites not to affect other functional tests
- Assignee changed from riafarov to mgriessmeier
Updated by mgriessmeier over 5 years ago
- Target version changed from Milestone 25 to Milestone 26
Updated by mgriessmeier over 5 years ago
- Status changed from Blocked to New
- Target version changed from Milestone 26 to Milestone 27
to be groomed as well as the subtask
Updated by mgriessmeier over 5 years ago
removed due date to prevent email spam
Updated by mgriessmeier over 5 years ago
- Target version changed from Milestone 27 to Milestone 28
Updated by riafarov about 5 years ago
- Target version changed from Milestone 28 to Milestone 30+
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 30+ to Milestone 30
bulk moved to M30 for revisiting
Updated by SLindoMansilla over 4 years ago
- Status changed from Blocked to Workable
- Assignee changed from mgriessmeier to szarate
Updated by riafarov over 4 years ago
- Subject changed from [functional][y][u][epic] Move different checks to separate test suites not to affect other functional tests to [functional][u][epic] Move different checks to separate test suites not to affect other functional tests
Updated by szarate about 4 years ago
- Tracker changed from action to coordination
- Status changed from Workable to New
Updated by szarate about 4 years ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html
Updated by tjyrinki_suse about 4 years ago
- Subject changed from [functional][u][epic] Move different checks to separate test suites not to affect other functional tests to [qe-core][functional][epic] Move different checks to separate test suites not to affect other functional tests
Updated by okurz over 3 years ago
This ticket had a due set but exceeded it already by more than 14 days. We would like to take the due date seriously so please update the ticket accordingly (resolve the ticket or update the due-date or remove the due-date). See https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives for details. This update was done as agreed within the SUSE QE Sync call 2021-09-01
Updated by slo-gin over 2 years ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.