Project

General

Profile

coordination #17714

[sles][functional][medium][epic] various testsuite enhancements (names, descriptions, etc.)

Added by okurz almost 6 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Start date:
2018-03-13
Due date:
2018-03-27
% Done:

100%

Estimated time:
(Total: 0.00 h)
Difficulty:

Description

Acceptance criteria

  • AC1: All questions mentioned in "Tasks" are answered

Tasks

fcrozat, ast and me went over the current list of testsuites as we have them enables for the sles functional group. Out of that discussions we gathered the following questions and ideas. Please try to answer each one individually here, could be links to delegated tickets

  • DONE: btrfs tests, some variants for s390, do we need them? -> yes, we need them all because they test important different machine variants. Most likely we could schedule these tests on "default_install" instead of "btrfs"
  • DONE: +dud_sdk: @jpupava: add description to test_suite -> delegated to #23624
  • "extratest": try to think of better name -> Couldn't think of anything. At least we have a good test suite description.
  • DONE: rename "gnome" to "default" or "default-graphical" -> delegated to #33172
  • DONE: add description for "gnome"
  • DONE: cover "gnome@ipmi" -> we have a scenario "gnome@ipmi" now
  • DONE: check difference between "gnome" and "gnome+acpi" -> "gnome+acpi" is aarch64 specific forcing of acpi
  • add testsuite for gnome+sdk+proxy_SCC_without_addons did not understand why we would need to do that
  • DONE: check "gpt" for non-ppc64le, why no scenario? -> I do not see a reason why not test it on other archs as well so I schedule in test development at least on x86_64 -> delegated to #33175
  • DONE: why "minimal_x+uefi" and not just one? -> that is a aarch64 specific scenario which is not applicable to other architectures. Could not think of any better name
  • DONE: can we remove the sle/sles12 prefix -> we did
  • DONE: add description for "sles12sp2_autoyast_bug-872"
  • DONE: "smb+xfs@s390x-zVM-vswitch-l2"
  • DONE: "xen" test suite not needed because we have system roles covered? -> generally true. The difference is that in one case we rely on the defaults coming from the role, in the case of "xen" we use a "default" installation and check the xen pattern. Both are valid test cases and also they help for crosschecking, e.g. if just one of both fail then it could be about pattern selection, etc.

Please mark them off individually when DONE.


Subtasks

action #33172: [sle][functional]rename "gnome" to "default"Resolvedokurz

action #33175: [sle][functional]Test "gpt" scenario on non-ppc64leResolvedokurz


Related issues

Related to openQA Tests - action #20830: [tools][sles][functional]Get rid of version specific prefix in test suite names when the test suites also apply for other versionsResolved2017-06-11

History

#1 Updated by okurz over 5 years ago

  • Related to action #20830: [tools][sles][functional]Get rid of version specific prefix in test suite names when the test suites also apply for other versions added

#2 Updated by okurz about 5 years ago

  • Target version set to Milestone 13

#3 Updated by riafarov almost 5 years ago

  • Target version changed from Milestone 13 to Milestone 14

Still valid, okurz, please refine if want to schedule it.

#4 Updated by okurz almost 5 years ago

  • Due date set to 2018-03-13

I would just try to answer every specific question on its own.

#5 Updated by okurz almost 5 years ago

  • Subject changed from [sles][functional] various testsuite enhancements (names, descriptions, etc.) to [sles][functional][medium] various testsuite enhancements (names, descriptions, etc.)
  • Description updated (diff)
  • Status changed from New to Workable

#6 Updated by mgriessmeier almost 5 years ago

  • Subject changed from [sles][functional][medium] various testsuite enhancements (names, descriptions, etc.) to [sles][functional][medium][epic] various testsuite enhancements (names, descriptions, etc.)
  • Assignee set to okurz

#7 Updated by mgriessmeier almost 5 years ago

  • Due date changed from 2018-03-13 to 2018-03-27
  • Target version changed from Milestone 14 to Milestone 15

#8 Updated by okurz almost 5 years ago

  • Description updated (diff)

#9 Updated by okurz almost 5 years ago

  • Description updated (diff)

#10 Updated by okurz almost 5 years ago

  • Status changed from Workable to Feedback

just waiting for the two subtickets to be done now.

#11 Updated by mgriessmeier almost 5 years ago

  • Status changed from Feedback to Resolved

subtickets are resolved

#12 Updated by szarate over 2 years ago

  • Tracker changed from action to coordination

Also available in: Atom PDF