Project

General

Profile

Actions

action #36100

closed

[functional][u] Better explicit system performance test

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

Status:
Resolved
Priority:
Low
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 17
Start date:
2018-05-11
Due date:
2018-06-19
% Done:

0%

Estimated time:
Difficulty:

Description

Motivation

Our openQA tests are very good at finding system performance issues, e.g. bsc#1063638 and bsc#1032831, but very bad at revealing the actual problems to test reviewers because seemingly random test modules fail sporadically due to just timeouts, windows not popping up, etc. . Recording random soft-fails in random scenarios is apparently not the way. We should define specific scenarios to test everything we do not want to test in other scenarios. Whenever we encounter other tests failing we should ensure that they work in a stable way and corresponding test steps are moved into the new "system performance" test scenario

Acceptance criteria

  • AC1: bsc#1063638 is not tracked in any other test scenario than one for system performance testing

Tasks

  • Track in development for TW
  • Add to Leap
  • Add to SLE15
  • Add to SLE12SP4
  • Look for more stuff to add in this scenario, e.g. something about yast2_snapper which was recently removed by lnussel from standard scenarios, "reboot and call krunner test", see

Related issues 2 (0 open2 closed)

Related to openQA Tests - action #20036: [desktop]x11_setup needs to run after force_cron_runsRejectedGraceWang2017-06-26

Actions
Related to openQA Tests - action #39059: [sle][functional][y] detect "openSUSE sucks bug" about btrfs balance and record_soft_fail (was: yast2_gui tests modules as application could not start up)Resolvedriafarov2018-08-012018-10-09

Actions
Actions

Also available in: Atom PDF