coordination #29733: [epic][functional][u] Test suites that use "all patterns" boot from created qcow2 image - openQA Tests - openSUSE Project Management Tool

Actions

Copy link

coordination #29733

closed

[epic][functional][u] Test suites that use "all patterns" boot from created qcow2 image

Added by SLindoMansilla over 6 years ago. Updated over 3 years ago.

Status:

Rejected

Priority:

Normal

Assignee:

szarate

Category:

New test

Target version:

QA - future

Start date:

2020-05-06

Due date:

% Done:

100%

Estimated time:

(Total: 84.00 h)

Difficulty:

Description

Motivation¶

There were three test suites in SLE12 that covered the installation with all patterns selected. For SLE15+ there is only one.

allmodules+allpatters
allpatterns SLE-12-SP3, SLE-12-SP4, SLE-15
sdk+allpatterns SLE 12-SP3, SLE 12-SP4
we+allpatterns SLE 12-SP3, SLE 12-SP4

The execution time was long and the maintenance tedious. It would be easier if they would be split into create_hdd_*_allpatterns and extra_tests_*_allpatterns.
It would also be good to recover the lost coverage after the new SLE15 installation media.

Subtasks 4 (0 open — 4 closed)

Related issues 3 (0 open — 3 closed)

Actions

Copy link

Updated by SLindoMansilla over 6 years ago

Status changed from Workable to Blocked

Blocked by: https://progress.opensuse.org/issues/29730

Actions

Copy link

Updated by SLindoMansilla over 6 years ago

Blocked by action #29730: [sle][functional][u][medium] New test suite create_hdd_gnome+all_patterns added

Actions

Copy link

Updated by SLindoMansilla over 6 years ago

Blocks action #23628: [sle][functional][medium] Add SLE15 test corresponding to former "sdk+allpatterns" test suite added

Actions

Copy link

Updated by okurz over 6 years ago

Due date set to 2018-01-30

Actions

Copy link

Updated by okurz over 6 years ago

Target version set to Milestone 13

Actions

Copy link

Updated by jorauch over 6 years ago

Subject changed from [sle][functional] Test suites that use "all patterns" boot from created qcow2 image to [sle][functional][medium] Test suites that use "all patterns" boot from created qcow2 image
Assignee set to jorauch

Apply these settings to the test suites:

START_AFTER_TEST=create_hdd_gnome+all_patterns
HDD_1=SLES-%VERSION%-%ARCH%-Build%BUILD%@%MACHINE%-gnome-all-patterns.qcow2
BOOT_HDD_IMAGE=1

Actions

Copy link

Updated by jorauch over 6 years ago

Status changed from Blocked to In Progress

not blocked anymore

Actions

Copy link

Updated by jorauch over 6 years ago

https://bugzilla.suse.com/show_bug.cgi?id=1071939
Might become a problem, will fix select_console first

Actions

Copy link

Updated by jorauch about 6 years ago

Allpatterns SL15:
pinky.arch.suse.de/tests/167
Allpatterns Sle12/4:
http://pinky.arch.suse.de/tests/171

Actions

Copy link

#10

Updated by jorauch about 6 years ago

ADDONS=sdk
ADDONS=we
would need to be installed afterwards

Actions

Copy link

#11

Updated by riafarov about 6 years ago

Due date changed from 2018-01-30 to 2018-02-13
Target version changed from Milestone 13 to Milestone 14

Actions

Copy link

#12

Updated by okurz about 6 years ago

Category set to Enhancement to existing tests
Status changed from In Progress to Feedback

I would like to discuss this ticket with you in person when you are in office again. Please delay work on it until then.

Actions

Copy link

#13

Updated by JERiveraMoya about 6 years ago

Please, consider increasing story complexity to [HARD], at least to reflect heavy testing with image creation or peer with someone else to get verification runs without increasing the complexity.

Actions

Copy link

#14

Updated by okurz about 6 years ago

Blocks deleted (action #23628: [sle][functional][medium] Add SLE15 test corresponding to former "sdk+allpatterns" test suite)

Actions

Copy link

#15

Updated by okurz about 6 years ago

Related to action #23628: [sle][functional][medium] Add SLE15 test corresponding to former "sdk+allpatterns" test suite added

Actions

Copy link

#16

Updated by jorauch about 6 years ago

Due date deleted (~~2018-02-13~~)
Category changed from Enhancement to existing tests to New test
Status changed from Feedback to Workable
Assignee deleted (~~jorauch~~)
Target version changed from Milestone 14 to future

As discussed with okurz we do not have a current use case for these. Could make sense in the future whenever we need it, i.e. when we have any test that wants to test based on special patterns.

Actions

Copy link

#17

Updated by jorauch about 6 years ago

Parent task deleted (~~#23454~~)

Actions

Copy link

#18

Updated by okurz almost 6 years ago

Subject changed from [sle][functional][medium] Test suites that use "all patterns" boot from created qcow2 image to [sle][functional][medium][u] Test suites that use "all patterns" boot from created qcow2 image

Actions

Copy link

#19

Updated by okurz almost 6 years ago

Target version changed from future to future

Actions

Copy link

#20

Updated by okurz over 5 years ago

Status changed from Workable to New

Bulk action to set status back to "New" for older tickets which are in "future". They would need to be revisited in time when we come up with a defined plan and assign to a milestone.

Actions

Copy link

#21

Updated by okurz over 5 years ago

Priority changed from Normal to Low

Actions

Copy link

#22

Updated by szarate about 4 years ago

Status changed from New to Workable
Priority changed from Low to High

We agreed to create_hdd_ENV+allpatterns => extratests_allpatterns_blah

Actions

Copy link

#23

Updated by zluo almost 4 years ago

Status changed from Workable to In Progress
Assignee set to zluo

take over

Actions

Copy link

#24

Updated by SLindoMansilla almost 4 years ago

Description updated (diff)

Actions

Copy link

#25

Updated by zluo almost 4 years ago

for current convention, they should be named:

extra_tests_allpatterns
extra_tests_allpatterns_sdk
extra_tests_allpatterns_we

And the one that generates the qcow2:

create_hdd_allpatterns
So, the first step would be to create a test suite in OSD called create_hdd_allpatterns.
Then you could have it scheduled in your own test development job group until it is stable.
When it is stable, it can be moved to https://gitlab.suse.de/qsf-u/qa-sle-functional-userspace/-/blob/master/functional_sle15_jobgroup.yaml

Then, we start migrating allpatterns into extra_tests_allpatterns and similar steps 1. 2. 3.

Actions

Copy link

#26

Updated by zluo almost 4 years ago

create_hdd_allpatterns created on osd.
https://openqa.suse.de/admin/job_templates/312 first draft

Actions

Copy link

#27

Updated by szarate almost 4 years ago

szarate wrote:

We agreed to create_hdd_ENV+allpatterns => extratests_allpatterns_blah

create_hdd_gnome+allpatterns => extra_tests_gnome_allpatterns

Actions

Copy link

#28

Updated by SLindoMansilla almost 4 years ago

Due date set to -4712-01-01
Start date set to 5000-01-01

due to changes in a related task: #29733

Actions

Copy link

#29

Updated by SLindoMansilla almost 4 years ago

Due date set to -4712-01-01

due to changes in a related task: #66541

Actions

Copy link

#30

Updated by SLindoMansilla almost 4 years ago

Subject changed from [sle][functional][medium][u] Test suites that use "all patterns" boot from created qcow2 image to [epic][functional][u] Test suites that use "all patterns" boot from created qcow2 image
Description updated (diff)
Status changed from In Progress to Workable
Assignee changed from zluo to SLindoMansilla