QA » openQA Project » openQA Tests

Discussed in the daily 2018-10-30 with QSF. Updated https://wiki.microfocus.net/index.php?title=RD-OPS_QA%2FopenQA_review&type=revision&diff=375641&oldid=375317 including a schedule proposal. So the first suggestion about renaming the "autoyast" section is actually done already.

Further proposals:

We try to focus the subteams ''QSF-u'' and ''QSF-y'' more which should also be reflected by daily test review domains. The following options (''O'') are considered:

• O1: We emphasize the ''areas of expertise'' including the YaST job group as one of them but keep a QSF team-wide weekly-schedule with overlap of u-/y-team members
• O2a: Have a shared, overlap weekly-schedule for o3 and per subteam for osd
• O2b: Have a schedule per subteam and let ''QSF-u'' handle o3 review (''con:'' y-team would loose early feedback from new YaST development related changes, especially when SLE products go into hardening phase, ''pro:'' more focus for y-team)
• O3c: As above but ''QSF-y'' handles o3 (''pro:'' y-team closer to YaST development as they would like to be, ''con:'' userspace failures challenging for QSF-y)
• O4: No daily review of o3 anymore, just areas of expertise -> okurz: Not acceptable as the very efficient openSUSE test review approach where oS RMs do the main share of the work should not be hindered by additional frustration when they need to handle the test breakages we introduce or the yast related changes that we already know about

@team WDYT? Feedback welcome!

TBD in today's retro.

waiting for feedback on my proposal. Maybe we can cover it in one of the next retrospective meetings.

@oorlov, @riafarov, you wanted to come up with a new schedule proposal, right?

Team members are on vacation, so planning for the second week of January.

https://wiki.microfocus.net/index.php/RD-OPS_QA/openQA_review#YaST

Wiki page updated.