Project

General

Profile

Actions
Copy link

coordination #38936

open

[qe-core][functional][epic] schedule all tests after installcheck as this one only takes two minutes and finds easy issues

Added by okurz over 5 years ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 32
Start date:
2018-07-30
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Motivation

Most aarch64 jobs in SLE12SP4 build 0305 failed in https://openqa.suse.de/tests/1873481#step/installation_overview/48 with a dependency problem "nothing provides openssl-1_0_0 = 1.0.2j needed by openssl-1.0.2j-15.1.noarch" which has been reported in bsc#1103063 and promptly fixed afterwards. These are issues that can be more easily detected by running the "installcheck" scenario which is also faster. No need to run a full graphical installation.

Acceptance criteria

  • AC1: installcheck fails on these issues and no other scenario shows dependency issues as they are not even scheduled then

Suggestions

  • Set START_AFTER_TEST=installcheck on all test suites that do not have it yet
  • Add installcheck on scenarios where we do not have it yet, e.g. aarch64 and s390x
  • start with one SLE product, one architecture, then more architectures and more products
  • crosscheck situation on o3
Actions
Copy link
 #1

Updated by okurz over 5 years ago

  • Subject changed from [functional][epic] schedule all tests after installcheck as this one only takes two minutes and finds easy issues to [functional][u][epic] schedule all tests after installcheck as this one only takes two minutes and finds easy issues
Actions
Copy link
 #2

Updated by mgriessmeier about 4 years ago

  • Subject changed from [functional][u][epic] schedule all tests after installcheck as this one only takes two minutes and finds easy issues to [functional][u][y][epic] schedule all tests after installcheck as this one only takes two minutes and finds easy issues
  • Assignee set to mgriessmeier
  • Target version changed from future to Milestone 31

let's discuss with [y]-team in parallel and find proper subtasks

Actions
Copy link
 #3

Updated by riafarov about 4 years ago

  • Target version changed from Milestone 31 to Milestone 32
Actions
Copy link
 #4

Updated by SLindoMansilla almost 4 years ago

  • Assignee changed from mgriessmeier to SLindoMansilla
Actions
Copy link
 #5

Updated by SLindoMansilla almost 4 years ago

Maybe only add it to offline scenarios.

Actions
Copy link
 #6

Updated by riafarov almost 4 years ago

  • Subject changed from [functional][u][y][epic] schedule all tests after installcheck as this one only takes two minutes and finds easy issues to [functional][u][epic] schedule all tests after installcheck as this one only takes two minutes and finds easy issues

In our team we have already worked on similar concept to chain test suites where it makes sense. However, experience shows that RMs will be interested to see as much results as possible regardless of single failure to understand risks failure introduces.

Actions
Copy link
 #7

Updated by szarate over 3 years ago

  • Tracker changed from action to coordination
Actions
Copy link
 #9

Updated by tjyrinki_suse over 3 years ago

  • Subject changed from [functional][u][epic] schedule all tests after installcheck as this one only takes two minutes and finds easy issues to [qe-core][functional][epic] schedule all tests after installcheck as this one only takes two minutes and finds easy issues
Actions
Copy link
 #10

Updated by SLindoMansilla about 3 years ago

  • Assignee deleted (SLindoMansilla)

No time to work on this :(

Actions
Copy link
 #11

Updated by slo-gin over 1 year 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.

Actions
Copy link
 #12

Updated by slo-gin about 1 month 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.

Actions
Copy link

Also available in: Atom PDF