QA (public) » openQA Project (public) » openQA Tests (public)

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)
  • gnome
  • microos/readonly filesystem
  • JeOS Should be Minimal VM - Minimal VM

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¶

• To call attention from QE-Core, aside from using [qe-core] in the title of a ticket, bugbusters, see also https://progress.opensuse.org/projects/qa/wiki/Core#TLDR
• foursixnine sometimes hangs out on matrix (PO for QE-Core)