Project

General

Profile

Actions

coordination #129931

open

openQA Project - coordination #154768: [saga][ux] State-of-art user experience for openQA

[qe-core] Tumbleweed & Leap tests - meeting follow ups

Added by szarate about 1 year ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Spike/Research
Target version:
Start date:
2023-05-26
Due date:
% Done:

0%

Estimated time:
Difficulty:
Sprint:
QE-Core: November Sprint 23 (Nov 15 - Dec 13)

Description

Define a set of tests that should always pass on pull-requests of os-autoinst-distri-opensuse

Status now

  • Dominque checks and sees if the person is there, wait for fix, if not revert.. about 25% get reverted due to time constraints (Broken TW) and the rest fix comes quite soon.
  • mean time to resolution about 1.5 days
  • ideal 1 day or less
  • some VRs are not up to date

The wish

  • Below ten failures per build

Staging Tumbleweed - Tests that should pass on PR's

  • At the moment 90 minutes is a lead time (not good)
  • None of the tests that are in staging can fail (ok, some... trim them down)

Leap

  • There is no staging openQA
    • We wait for Next year (15++)
  • Reevaluate last EOL (15.2 onwards -> same as sles)

Improvements to test scenarios

  • Milestones are not counted in the test execution (reevaluate)
    • Do we really need this? or should we rearrange the tests all together
  • We have the same problem on o3 that we have in osd (zypper log pacakes story)

    • Why do we test vim everywhere (example)
  • Brainstorm Offloading of tets from o3 to osd and reporting back to o3 (Proxy openQA jobs to osd) - left hanging

Desktop and GUI testing

  • Trim down Firefox (from sles -if -) changes every 6 weeks :D
  • Tomcat test check again (websockts) - smbd something
  • Multi window applications should accept ctrl+w, applications with a single one is alt+f4

open discussion

  • PPC is Pain, GRU is deleting images

Extra notes

Actions #1

Updated by szarate about 1 year ago

  • Tags set to platform-team
Actions #2

Updated by szarate about 1 year ago

  • Parent task set to #124625
Actions #3

Updated by okurz about 1 year ago

  • Target version set to future

I am selecting "future" target version as it does not look like something that SUSE QE Tools can usefully contribute to. You could move it to "openQA Tests" though, it's specific to that after all, right?

Actions #4

Updated by szarate about 1 year ago

  • Project changed from QA to openQA Tests

okurz wrote:

I am selecting "future" target version as it does not look like something that SUSE QE Tools can usefully contribute to. You could move it to "openQA Tests" though, it's specific to that, right?

It goes a bit beyond openQA I think. Hence it is being put into the QA project instead... but I don't care where it lives for now (there's no direct actionable stuff for tools, other than #48641 for now, and things like displaying & counting the time spent on snapshots (no ticket yet) and others.

Actions #5

Updated by okurz about 1 year ago

  • Category set to New test
Actions #6

Updated by szarate about 1 year ago

  • Category changed from New test to Spike/Research

This isn't a new test

Actions #7

Updated by szarate 9 months ago

  • Tags changed from platform-team to platform-team, qe-core-november-sprint
  • Tracker changed from action to coordination
Actions #8

Updated by szarate 8 months ago

  • Sprint set to QE-Core: November Sprint 23 (Nov 15 - Dec 13)
Actions #9

Updated by szarate 5 months ago

Actions #10

Updated by szarate about 2 months ago

  • Parent task changed from #124625 to #154768
Actions

Also available in: Atom PDF