action #29730

[sle][functional][u][medium] New test suite create_hdd_gnome+all_patterns

Added by SLindoMansilla over 2 years ago. Updated about 1 year ago.

Status:RejectedStart date:22/12/2017
Priority:NormalDue date:
Assignee:okurz% Done:

0%

Category:New test
Target version:QA - future
Difficulty:medium
Duration:

Description

There are several test suite that use the same installation.

If we had the installation in a separated test suite that generates de qcow2 image for the rest of the test suites that need it, we would have:

  • shorter execution times on productive instance (faster build feedback)
  • shorter execution times on QA engineers machines (machines less busy/blocked)
  • easier maintenance of test suites that need this qcow2 image.
  • Avoid redundancy problems on test suites that should perform the same installation by centralizing such installation into one test suite.

The following test suites could boot using that qcow2 image:

Acceptance criteria

  • AC1: There a new test suite that creates a qcow2 image with all patterns installed.

Task

  1. Create a new test suite.
  2. Test is locally.
  3. Enable it on OSD.

Related issues

Related to openQA Tests - action #23454: [sle][functional][epic][sle15] Adapt former SDK tests to ... Resolved 18/08/2017 14/08/2018
Blocks openQA Tests - action #29733: [sle][functional][medium][u] Test suites that use "all pa... Workable 22/12/2017
Copied to openQA Tests - action #31108: [opensuse][functional][medium] New test suite all_patterns Resolved 22/12/2017 27/02/2018

History

#1 Updated by SLindoMansilla over 2 years ago

  • Blocks action #29733: [sle][functional][medium][u] Test suites that use "all patterns" boot from created qcow2 image added

#2 Updated by okurz over 2 years ago

  • Status changed from Workable to New

I don't understand the use case or benefit. Please elaborate.

#3 Updated by okurz over 2 years ago

  • Due date set to 30/01/2018

#4 Updated by SLindoMansilla about 2 years ago

  • Description updated (diff)

okurz, clarified enough?

#5 Updated by jorauch about 2 years ago

  • Subject changed from [sle][functional] New test suite create_hdd_gnome+all_patterns to [sle][functional][medium]New test suite create_hdd_gnome+all_patterns
  • Status changed from New to In Progress
  • Assignee set to jorauch

#6 Updated by jorauch about 2 years ago

Important setting:

DESKTOP=gnome
ENABLE_ALL_SCC_MODULES=1
PATTERNS=all

#7 Updated by jorauch about 2 years ago

Verification run on OSD:
https://openqa.suse.de/tests/1397275#

#8 Updated by jorauch about 2 years ago

Verification run on O3: https://openqa.opensuse.org/tests/585030
Test suite created on OSD, need to wait for new build to verify it is actually triggered

#9 Updated by jorauch about 2 years ago

Verification for PATTERNS=all:
https://openqa.suse.de/tests/1399842

#10 Updated by jorauch about 2 years ago

  • Description updated (diff)
  • Status changed from In Progress to Feedback

Automatically triggered on OSD:
https://openqa.suse.de/tests/1404053

At least an all pattern installation suite should be created on O3

#11 Updated by okurz about 2 years ago

  • Target version set to Milestone 13

#12 Updated by riafarov about 2 years ago

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

@jrauch, is o3 test suite only missing part here?

#13 Updated by jorauch about 2 years ago

  • Target version deleted (Milestone 14)

Yes O3 is the only missing part, I am wondering if ENABLE_ALL_SCC_MODULES is really needed for all patterns?

#14 Updated by jorauch about 2 years ago

  • Target version set to Milestone 14

readding target version

#15 Updated by jorauch about 2 years ago

  • Due date deleted (13/02/2018)
  • 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.

#16 Updated by jorauch about 2 years ago

  • Parent task deleted (#23454)

#17 Updated by jorauch about 2 years ago

  • Related to action #23454: [sle][functional][epic][sle15] Adapt former SDK tests to something equivalent for SLE15 added

#18 Updated by jorauch about 2 years ago

  • Copied to action #31108: [opensuse][functional][medium] New test suite all_patterns added

#19 Updated by SLindoMansilla about 2 years ago

Why did you deleted the parent task?

#20 Updated by okurz about 2 years ago

because the former parent task can be fulfilled without this task according to the ACs

#21 Updated by okurz almost 2 years ago

  • Subject changed from [sle][functional][medium]New test suite create_hdd_gnome+all_patterns to [sle][functional][u][medium] New test suite create_hdd_gnome+all_patterns
  • Difficulty set to medium

#22 Updated by okurz almost 2 years ago

  • Target version changed from future to future

#23 Updated by okurz over 1 year 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.

#24 Updated by okurz about 1 year ago

  • Status changed from New to Rejected
  • Assignee set to okurz

I think time has shown that we do not benefit from that currently. When we see a direct need we can bring this back up. However then we would do it differently after in the past months we have split out the YaST job group and image creation jobs plus post-install validations are conducted differently.

Also available in: Atom PDF