Project

General

Profile

Actions

action #92851

closed

coordination #91646: [saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release

openQA Project - coordination #89062: [epic] Simplify review for SUSE QAM

Workshop series proposal "How SUSE QE teams review openQA test results"

Added by okurz about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Target version:
Start date:
2021-05-19
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Many people are busy every day with Changes to the review process are proposed https://confluence.suse.com/display/~vpelcak/Draft+-+Change+in+openQA+QE+Maintenance+Review

I created a proposal on https://progress.opensuse.org/projects/qa/wiki/Wiki#Workshop-Topics for "How we review openQA test results, by SUSE QE teams". I think it would be great if people from every QE team would present how they do the daily openQA test result review. We all could learn from each other this way to improve, find new ways, learn how certain features are used, which ones are unused or unknown, where to extend, etc.

Suggestions

Find person from each team, propose date and speaker for each team.

Actions #1

Updated by livdywan about 3 years ago

  • Status changed from Workable to In Progress
  • Assignee set to livdywan

I'm starting some conversations to see who might like to volunteer.

To be clear, the conversation referred to is not especially relevant here. No context required. This should be something like:

  • This is what we do in the squad
  • This is a typical task during the day
  • Workflows and tools around openQA test review

The idea being that this can provide perspective to others who may have no or little knowledge of what people do. This could help put bug reports and feature requests into context.

Actions #2

Updated by okurz about 3 years ago

I haven't seen conversations by you for this topic although I am in quite some communication channels. If you do direct messaging, care to shift more to group chats?

Actions #3

Updated by livdywan about 3 years ago

okurz wrote:

I haven't seen conversations by you for this topic although I am in quite some communication channels. If you do direct messaging, care to shift more to group chats?

Correct. I was chatting to Orestis first to sanity-check the idea and phrasing. Next step inviting people in various channels.

Actions #4

Updated by livdywan about 3 years ago

Brief update. I got some feedback and questions after posting the invite on different squad channels. I had to clarify that any open slot is fine, and also there's no particular rush. Whenever people are available we'll make it work. It's a request, not a demand :-D

Actions #5

Updated by livdywan about 3 years ago

  • Status changed from In Progress to Feedback
  • Invited update validation squad (RC, some feedback)
  • Invited yast squad (RC)
  • Invited kernel squad (RC+email, some feedback)
  • Invited the virt squad (RC)
  • Invited the core squad (RC)

Got also migration, container, security on my list but not sure where to send invites

Actions #6

Updated by okurz about 3 years ago

cdywan wrote:

  • Invited update validation squad (RC, some feedback)
  • Invited yast squad (RC)
  • Invited kernel squad (RC+email, some feedback)
  • Invited the virt squad (RC)
  • Invited the core squad (RC)

Got also migration, container, security on my list but not sure where to send invites

Send to qa-team@suse.de and invite a representative of every squad. If no one speaks up for a squad escalate to QE mgmt that a squad completely vanished ;)

It looks very unprofessional but I assume nowadays https://confluence.suse.com/display/qasle/QE+squads+-+new+structure is the best reference for you to see the current setup of squads. Why do I consider it unprofessional? Well, a page that says "new structure" sounds like someone only made a very short-term decision to draft up a page to describe a change in organisation while existing references like https://progress.opensuse.org/projects/suseqa/ and https://wiki.suse.net/index.php?title=SUSE-Quality_Assurance/SLE_Department are not updated. Then the "new structure" page is the current one until there will be a "new new structure" or "new structure - final v.2, for real!" ;)

Actions #7

Updated by maritawerner about 3 years ago

Oli, you are very right that the wiki page will not be updated anymore. The confluence area of QE LSG is the main source of information. And to make you happy, I have removed the "neW" in new structure.

Actions #8

Updated by livdywan about 3 years ago

  • Project changed from 46 to QA
Actions #9

Updated by livdywan about 3 years ago

  • Due date set to 2021-07-09
  • Private changed from No to Yes

Setting a due date for the end of the week, let's try and make those proposals firm

Actions #10

Updated by livdywan about 3 years ago

  • Private changed from Yes to No
Actions #11

Updated by livdywan about 3 years ago

  • Status changed from Feedback to Resolved

So we got another topic this morning, two more firm submissions and another couple promises. And there have been repeated invitations on different channels. Perhaps this can be considered resolved.

Actions #12

Updated by okurz almost 3 years ago

  • Due date deleted (2021-07-09)
Actions

Also available in: Atom PDF