Project

General

Profile

Actions

action #43091

closed

[desktop] Separate isosize into a independent test suite

Added by GraceWang over 5 years ago. Updated about 2 years ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
Enhancement to existing tests
Target version:
-
Start date:
2018-10-30
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

In SLED12SP4 Functional: Desktop group, the isosize problem occurred many times.
(bsc#1101761, bsc#1112652 and bsc#1113863)

Every time when the iso size over limit problem occurred, it will block all the other remaining testing.
(See https://openqa.suse.de/tests/overview?distri=sle&version=12-SP4&build=0371&groupid=152)
Majority of the test suites are skipped.

IMHO, the iso size problem is critical but should not block the other regression testing.

I like the way we deal with mediacheck and installcheck.

I am opening this ticket to see the possibility to enhance this (maybe after SLE12SP4 or before SLE12SP5)

Please share your opinions or add relevant people to the watcher list.

Actions #1

Updated by okurz over 5 years ago

  • Subject changed from [Enhancement] Separate isosize into a independent test suite to Separate isosize into a independent test suite
  • Category set to Enhancement to existing tests

Actually a good idea. I don't see a problem to schedule it only for e.g. Media heck, the name would fit :)

Actions #2

Updated by okurz over 5 years ago

  • Subject changed from Separate isosize into a independent test suite to [desktop] Separate isosize into a independent test suite
Actions #3

Updated by okurz over 2 years ago

  • Priority changed from Normal to Low

This ticket was set to "Normal" priority but was not updated within 730 days which is 2 times the period of the SLO for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . The ticket will be set to the next lower priority of "Low".

Actions #4

Updated by GraceWang about 2 years ago

  • Status changed from New to Rejected

This ticket was reported on SLE12SPX(sorry for not implementing it when we were doing SLE12SPX), and I didn't see any possibility to apply this to SLE15SPX since we didn't meet such kind of issue during the development of SLE15SP4.
So, set the status to REJECTED.

Actions

Also available in: Atom PDF