Project

General

Profile

action #38936

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

Added by okurz about 2 years ago. Updated 4 months ago.

Status:
New
Priority:
Normal
Category:
Enhancement to existing tests
Target version:
SUSE QA tests - 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

History

#1 Updated by okurz almost 2 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

#2 Updated by mgriessmeier 7 months 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

#3 Updated by riafarov 6 months ago

  • Target version changed from Milestone 31 to Milestone 32

#4 Updated by SLindoMansilla 5 months ago

  • Assignee changed from mgriessmeier to SLindoMansilla

#5 Updated by SLindoMansilla 5 months ago

Maybe only add it to offline scenarios.

#6 Updated by riafarov 4 months 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.

Also available in: Atom PDF