Project

General

Profile

Wiki » History » Version 410

okurz, 2022-01-21 08:55
SUSE QE Tools: Add feedback from yearly workshop review 2022-01-21

1 27 okurz
{{toc}}
2
3
# Test results overview
4 257 livdywan
* Latest report based on openQA test results for [OSD](https://openqa.io.suse.de/openqa-review/openqa_suse_de_status.html) and [SLE15](https://openqa.io.suse.de/openqa-review/openqa_sle15_status.html)
5 259 okurz
  * Find more reports on https://openqa.io.suse.de/openqa-review/
6 36 okurz
* only "blocker" or "shipstopper" bugs on "interesting products" for SLE: http://s.qa.suse.de/qa_sle_bugs_sle , SLE15: http://s.qa.suse.de/qa_sle_bugs_sle15_all, SLE12: http://s.qa/qa_sle_bugs_sle12_2
7 1 mgriessmeier
8 64 okurz
# QE tools - Team description
9 1 mgriessmeier
10 84 okurz
"The easiest way to provide complete quality for your software"
11
12 150 okurz
We provide the most complete free-software system-level testing solution to ensure high quality of operating systems, complete software stacks and multi-machine services for software distribution builders, system integration engineers and release teams. We continuously develop, maintain and release our software to be readily used by anyone while we offer a friendly community to support you in your needs. We maintain the main public and SUSE internal openQA server as well as supporting tools in the surrounding ecosystem.
13 84 okurz
14 27 okurz
## Team responsibilities
15 1 mgriessmeier
16 363 okurz
* Develop and maintain upstream openQA including the backend os-autoinst
17 27 okurz
* Administration of openqa.suse.de and workers (But not physical hardware, as these belong to the departments that purchased them and we merely facilitate)
18
* Helps administrating and maintaining openqa.opensuse.org, including coordination of efforts aiming at solving problems affecting o3
19 317 okurz
* Develop and maintain SUSE maintenance QA tools (SMELT, template generator, MTUI, openQA QAM bot, etc, e.g. from https://confluence.suse.com/display/maintenanceqa/Toolchain+for+maintenance+quality+engineering)
20 364 okurz
* Help with the investigation of specific issues, especially when they are likely related to generic or backend problems
21 27 okurz
* Support colleagues, team members and open source community
22 1 mgriessmeier
23 27 okurz
## Out of scope
24 1 mgriessmeier
25 364 okurz
* Maintenance and recurring review of individual tests
26 27 okurz
* Maintenance of physical hardware
27 333 okurz
* Maintenance of special worker addendums needed for tests, e.g. external hypervisor hosts for s390x, powerVM, xen, hyperv, IPMI, VMWare (Clarification: We maintain the code for all backends but we are no experts in specific domains. So we always try to help but it's a case by case decision based on what we realistically can provide based on our competence.)
28 27 okurz
* Ticket triaging of http://progress.opensuse.org/projects/openqatests/
29 214 okurz
* Setup of configuration for individual products to test, e.g. new job groups in openQA
30 27 okurz
* Feature development within the backend for single teams (commonly provided by teams themselves)
31
32 95 okurz
## Our common userbase
33
34 332 okurz
Known users of our products: Most SUSE QA engineers, SUSE SLE release managers and release engineers, every SLE developer submitting "submit requests" in OBS/IBS where product changes are tested as part of the "staging" process before changes are accepted in either SLE or openSUSE (staging tests must be green before packages are accepted), same for all openSUSE contributors submitting to either openSUSE:Factory (for Tumbleweed, SLE, future Leap versions) or Leap, other GNU/Linux distributions like Fedora https://openqa.fedoraproject.org/ , Debian https://openqa.debian.net/ , https://openqa.qubes-os.org/ , https://openqa.endlessm.com/ , the GNOME project https://openqa.gnome.org, https://www.codethink.co.uk/articles/2021/automated-linux-kernel-testing/, openSUSE KDE contributors (with their own workflows, https://openqa.opensuse.org/group_overview/23 ), openSUSE GNOME contributors (https://openqa.opensuse.org/group_overview/35 ), OBS developers (https://openqa.opensuse.org/parent_group_overview/7#grouped_by_build) , wicked developers (https://gitlab.suse.de/wicked-maintainers/wicked-ci#openqa), and of course our team itself for "openQA-in-openQA Tests" :) https://openqa.opensuse.org/group_overview/24
35 95 okurz
Keep in mind: "Users of openQA" and talking about "openSUSE release managers and engineers" means SUSE employees but also employees of other companies, also development partners of SUSE.
36
In summary our products, for example openQA, are a critical part of many development processes hence outages and regressions are disruptive and costly. Hence we need to ensure a high quality in production hence we practice DevOps with a slight tendency to a conservative approach for introducing changes while still ensuring a high development velocity.
37
38 27 okurz
## How we work
39
40 187 okurz
The QE Tools team is following the DevOps approach working using a lightweight Agile approach also inspired by [Extreme Programming](https://extremeprogramming.org/) and [Kanban](https://en.wikipedia.org/wiki/Kanban_(development)) and of course the original http://agilemanifesto.org/. We plan and track our works using tickets on https://progress.opensuse.org . We pick tickets based on priority and planning decisions. We use weekly meetings as checkpoints for progress and also track cycle and lead times to crosscheck progress against expectations.
41 27 okurz
42 83 okurz
* [tools team - backlog](https://progress.opensuse.org/issues?query_id=230): The complete backlog of the team
43 86 okurz
* [tools team - backlog, high-level view](https://progress.opensuse.org/issues?query_id=526): A high-level view of the backlog, all epics and higher (an "epic" includes multiple stories)
44
* [tools team - backlog, top-level view](https://progress.opensuse.org/issues?query_id=524): A top-level view of the backlog, only sagas and higher (a "saga" is bigger than an epic and can include multiple epics, i.e.  "epic of epics")
45 67 okurz
* [tools team - what members of the team are working on](https://progress.opensuse.org/issues?query_id=400): To check progress and know what the team is currently occupied with
46 116 okurz
* [tools team - closed within last 60 days](https://progress.opensuse.org/issues?query_id=541): What was recently resolved
47 1 mgriessmeier
48 184 okurz
*Be aware:* Custom queries in the right-hand sidebar of individual projects, e.g. https://progress.opensuse.org/projects/openqav3/issues , show queries with the same name but are limited to the scope of the specific projects so can show only a subset of all relevant tickets.
49 1 mgriessmeier
50 185 okurz
### What we expect from team members
51
52 222 okurz
* Actively show visible contributions to our products every workday *(pull requests, code review, ticket updates in decending priority, i.e. if you are very active in pull requests + code review ticket updates are much less important)*
53 186 okurz
* Be responsive over usual communication platforms and channels *(user questions, team discussions)*
54
* Stick to our rules *(this wiki, SLOs, alert handling)*
55 185 okurz
56 32 okurz
### Common tasks for team members
57
58
This is a list of common tasks that we follow, e.g. reviewing daily based on individual steps in the DevOps Process ![DevOps Process](devops-process_25p.png)
59
60
* **Plan**:
61
 * State daily learning and planned tasks in internal chat room
62
 * Review backlog for time-critical, triage new tickets, pick tickets from backlog; see https://progress.opensuse.org/projects/qa/wiki#How-we-work-on-our-backlog
63
* **Code**:
64 1 mgriessmeier
 * See project specific contribution instructions
65 390 mkittler
 * Provide peer-review following https://github.com/notifications based on projects within the scope of https://github.com/os-autoinst with the exception of test code repositories, especially https://github.com/os-autoinst/openQA, https://github.com/os-autoinst/os-autoinst, https://github.com/os-autoinst/scripts, https://github.com/os-autoinst/os-autoinst-distri-openQA, https://github.com/os-autoinst/openqa-trigger-from-obs, https://github.com/os-autoinst/openqa_review as well as other projects like https://github.com/openSUSE/Mojo-IOLoop-ReadWriteProcess and https://gitlab.suse.de/qa-maintenance/openQABot
66 32 okurz
* **Build**:
67
 * See project specific contribution instructions
68
* **Test**:
69
 * Monitor failures on https://travis-ci.org/ relying on https://build.opensuse.org/package/show/devel:openQA/os-autoinst_dev for os-autoinst (email notifications)
70
 * Monitor failures on https://app.circleci.com/pipelines/github/os-autoinst/openQA?branch=master relying on https://build.opensuse.org/project/show/devel:openQA:ci for openQA (email notifications)
71
* **Release**:
72
 * By default we use the rolling-release model for all projects unless specified otherwise
73 260 tinita
 * Monitor [devel:openQA on OBS](https://build.opensuse.org/project/show/devel:openQA) (all packages and all subprojects) for failures, ensure packages are published on http://download.opensuse.org/repositories/devel:/openQA/, ensure to be added as a Maintainer for that project (members need to be added individually, you can ask existing team members, e.g. the SM)
74 32 okurz
 * Monitor http://jenkins.qa.suse.de/view/openQA-in-openQA/ for the openQA-in-openQA Tests and automatic submissions of os-autoinst and openQA to openSUSE:Factory through https://build.opensuse.org/project/show/devel:openQA:tested
75
* **Deploy**:
76
 * o3 is automatically deployed (daily), see https://progress.opensuse.org/projects/openqav3/wiki/Wiki#Automatic-update-of-o3
77 198 mkittler
 * osd is automatically deployed (multiple times per week), monitor https://gitlab.suse.de/openqa/osd-deployment/pipelines and watch for notification email to openqa@suse.de
78 32 okurz
* **Operate**:
79
 * Apply infrastructure changes from https://gitlab.suse.de/openqa/salt-states-openqa (osd) or manually over sshd (o3)
80 37 okurz
 * Monitor for backup, see https://gitlab.suse.de/qa-sle/backup-server-salt
81 32 okurz
config changes in salt (osd), backups, job group configuration changes
82 61 okurz
 * Ensure old unused/non-matching needles are cleaned up (osd+o3), see #73387
83 217 okurz
 * Maintain https://gitlab.suse.de/qa-maintenance/qamops and https://confluence.suse.com/display/maintenanceqa/qam.suse.de
84 32 okurz
* **Monitor**:
85 106 livdywan
 * React on alerts from [stats.openqa-monitor.qa.suse.de](https://stats.openqa-monitor.qa.suse.de/alerting/list?state=not_ok) (emails on [osd-admins@suse.de](http://mailman.suse.de/mailman/listinfo/osd-admins) and login via LDAP credentials, you must be an *editor* to edit panels and hooks via the web UI)
86
 * Look for incomplete jobs or scheduled not being worked on o3 and osd (API or webUI) - see also #81058 for *power*
87 44 okurz
 * React on alerts from https://gitlab.suse.de/openqa/auto-review/, https://gitlab.suse.de/openqa/openqa-review/, https://gitlab.suse.de/openqa/monitor-o3 (subscribe to projects for notifications)
88 400 livdywan
 * Be responsive on #opensuse-factory (irc://irc.libera.chat/opensuse-factory, formerly irc://chat.freenode.net/opensuse-factory) for help, support and collaboration (Unless you have a better solution it is suggested to use [Element.io](https://matrix.to/#/!ilXMcHXPOjTZeauZcg:libera.chat) for a sustainable presence; you also need a [registered IRC account](https://libera.chat/guides/registration), formerly [freenode](https://freenode.net/kb/answer/registration))
89 283 livdywan
 * Be responsive on [#qa-tools in Rocket.Chat](https://chat.suse.de/channel/qa-tools) for internal coordination and alarm handling, fallback to #suse-qe-tools:opensuse.org (matrix) as backup if other channels are temporarily down, alternatively public channels on matrix/ IRC if the topics are not confidential
90 1 mgriessmeier
 * Be responsive on [#testing](https://chat.suse.de/channel/testing) for help, support and collaboration
91 50 okurz
 * Be responsive on mailing lists opensuse-factory@opensuse.org and openqa@suse.de (see https://en.opensuse.org/openSUSE:Mailing_lists_subscription)
92 142 okurz
 * Be responsive in https://matrix.to/#/#openqa:opensuse.org or the bridged room [#openqa](https://discord.com/channels/366985425371398146/817367056956653621) on https://discord.gg/opensuse if you have a discord account
93 31 okurz
94 27 okurz
### How we work on our backlog
95 1 mgriessmeier
96 27 okurz
* "due dates" are only used as exception or reminders
97
* every team member can pick up tickets themselves
98
* everybody can set priority, PO can help to resolve conflicts
99 321 okurz
* consider the [ready, not assigned/blocked/low](https://progress.opensuse.org/issues?query_id=490) query as preferred. It is suggested to pick up tickets based on priority. "Workable" tickets are often convenient and hence preferred.
100 60 livdywan
* ask questions in tickets, even potentially "stupid" questions, oftentimes descriptions are unclear and should be improved
101 62 okurz
* There are "low-level infrastructure tasks" only conducted by some team members, the "DevOps" aspect does not include that but focusses on the joint development and operation of our main products
102 74 okurz
* Consider tickets with the subject keyword or tag "learning" as good learning opportunities for people new to a certain area. Experts in the specific area should prefer helping others but not work on the ticket
103 91 okurz
* For tickets which are out of the scope of the team remove from backlog, delegate to corresponding teams or persons but be nice and supportive, e.g. [SUSE-IT](https://sd.suse.com/), [EngInfra](https://infra.nue.suse.com/) also see [SLA](https://confluence.suse.com/display/qasle/Service+Level+Agreements), [test maintainer](https://progress.opensuse.org/projects/openqatests/), QE-LSG PrjMgr/mgmt
104 358 okurz
 * For [EngInfra tickets](https://sd.suse.com/servicedesk/customer/portal/1) ensure there's a ticket for it in [openQA Infrastructure](https://progress.opensuse.org/projects/openqa-infrastructure/issues), use `EngInfra` under **Select a system**, use `[openqa] …` in the subject, reference the progress ticket and instead of a "Private request" (locked icon) select "Share with OSD-Admins" (unlocked icon). For already created tickets **Share** with `OSD-Admins` (the icon with two figures, not a single gray avatar) after creating the ticket. Use the tracker ticket for internal notes
105 112 okurz
* Whenever we apply changes to the infrastructure we should have a ticket
106 88 okurz
* Refactoring and general improvements are conducted while we work on features or regression fixes
107 89 okurz
* For every regression or bigger issue that we encounter try to come up with at least two improvements, e.g. the actual issue is fixed and similar cases are prevented in the future with better tests and optionally also monitoring is improved
108 368 okurz
* For critical issues and very big problems especially when we were informed by users about outages collect "lessons learned", e.g. in notes in the ticket or a meeting with minutes in the ticket, consider https://en.wikipedia.org/wiki/Five_whys and answer at least the following questions: "User impact, outwards-facing communication and mitigation, upstream improvement ideas, Why did the issue appear, can we reduce our detection time, can we prevent similar issues in the future, what can we improve technically, what can we improve in our processes". Also see https://youtu.be/_Dv4M39Arec
109 194 okurz
* okurz proposes to use "#NoEstimates". Though that topic is controversial and often misunderstood. https://ronjeffries.com/xprog/articles/the-noestimates-movement/ describes it nicely :) Hence tickets should be evenly sized and no estimation numbers should be provided on tickets
110 203 okurz
* If you really want you can look at the [burndown chart](https://progress.opensuse.org/agile/charts?utf8=%E2%9C%93&set_filter=1&f%5B%5D=chart_period&op%5Bchart_period%5D=%3E%3Ct-&v%5Bchart_period%5D%5B%5D=90&f%5B%5D=fixed_version_id&op%5Bfixed_version_id%5D=%3D&v%5Bfixed_version_id%5D%5B%5D=418&f%5B%5D=&chart=burndown_chart&chart_unit=issues&interval_size=day) (some people wish to have this) but we consider it unnecessary due to the continuous development, not a project with defined end. Also an [agile board](https://progress.opensuse.org/agile/board?utf8=%E2%9C%93&set_filter=1&f%5B%5D=fixed_version_id&op%5Bfixed_version_id%5D=%3D&v%5Bfixed_version_id%5D%5B%5D=418&f%5B%5D=status_id&op%5Bstatus_id%5D=%3D&f_status%5B%5D=1&f_status%5B%5D=12&f_status%5B%5D=2&f_status%5B%5D=15&f_status%5B%5D=4&c%5B%5D=tracker&c%5B%5D=assigned_to&c%5B%5D=cf_16) is available but likely due to problems within the redmine installation ordering cards is not reliable.
111 229 okurz
* Write to qa-team@suse.de as well for critical changes as well as chat channels
112
* Everyone should propose reverts of features if we find problems that can not be immediately fixed or worked around in production
113 112 okurz
114 55 okurz
#### Definition of DONE
115 1 mgriessmeier
116 322 dheidler
Also see https://web.archive.org/web/20110308065330/http://www.allaboutagile.com/definition-of-done-10-point-checklist/ and https://web.archive.org/web/20170214020537/https://www.scrumalliance.org/community/articles/2008/september/what-is-definition-of-done-(dod)
117 55 okurz
118
* Code changes are made available via a pull request on a version control repository, e.g. github for openQA
119
* [Guidelines for git commits](http://chris.beams.io/posts/git-commit/) have been followed
120
* Code has been reviewed (e.g. in the github PR)
121 1 mgriessmeier
* Depending on criticality/complexity/size/feature: A local verification test has been run, e.g. post link to a local openQA machine or screenshot or logfile
122 268 okurz
* For regressions: A regression fix is provided, flaws in the design, monitoring, process have been considered
123 55 okurz
* Potentially impacted package builds have been considered, e.g. openSUSE Tumbleweed and Leap, Fedora, etc.
124
* Code has been merged (either by reviewer or "mergify" bot or reviewee after 'LGTM' from others)
125
* Code has been deployed to osd and o3 (monitor automatic deployment, apply necessary config or infrastructure changes)
126
127 56 okurz
#### Definition of READY for new features
128 55 okurz
129
The following points should be considered before a new feature ticket is READY to be implemented:
130
131
* Follow the ticket template from https://progress.opensuse.org/projects/openqav3/wiki/#Feature-requests
132
* A clear motivation or user expressing a wish is available
133 266 okurz
* Acceptance criteria are stated (see ticket template) or use `[timeboxed:<nr>h]` with `<nr>` hours for tasks that should be limited in time, e.g. a research task with `[timeboxed:20h] research …`
134 55 okurz
* add tasks as a hint where to start
135
136 1 mgriessmeier
#### WIP-limits (reference "Kanban development")
137 28 okurz
138 79 livdywan
* global limit of 10 tickets, and 3 tickets per person respectively [In Progress](https://progress.opensuse.org/issues?query_id=505)
139
* limit of 20 tickets per person in [Feedback](https://progress.opensuse.org/issues?query_id=520)
140 27 okurz
141 1 mgriessmeier
#### Target numbers or "guideline", "should be", in priorities
142
143 172 okurz
1. *New, untriaged QA (openQA, etc.):* [0 (daily)](https://progress.opensuse.org/projects/qa/issues?query_id=576) . Every ticket should have a target version, e.g. "Ready" for QE tools team, "future" if unplanned, others for other teams
144 64 okurz
1. *Untriaged "tools" tagged:* [0 (daily)](https://progress.opensuse.org/issues?query_id=481) . Every ticket should have a target version, e.g. "Ready" for QE tools team, "future" if unplanned, others for other teams
145 273 okurz
1. *Workable (properly defined):* [10-40](https://progress.opensuse.org/issues?query_id=478) . Enough tickets to reflect a proper plan but not too many to limit unfinished data (see "waste")
146 82 okurz
1. *Overall backlog length:* [ideally less than 100](https://progress.opensuse.org/issues?query_id=230) . Similar as for "Workable". Enough tickets to reflect a proper roadmap as well as give enough flexibility for all unfinished work but limited to a feasible number that can still be overlooked by the team without loosing overview. One more reason for a maximum of 100 are that pagination in redmine UI allows to show only up to 100 issues on one page at a time, same for redmine API access.
147 71 okurz
1. *Within due-date:* [0 (daily/weekly)](https://progress.opensuse.org/issues?query_id=514) . We should take due-dates serious, finish tickets fast and at the very least update tickets with an explanation why the due-date could not be hold and update to a reasonable time in the future based on usual cycle time expectations
148 27 okurz
149
#### SLOs (service level objectives)
150
151
* for picking up tickets based on priority, first goal is "urgency removal":
152 123 okurz
 * **immediate**: [<1 day](https://progress.opensuse.org/issues?query_id=542)
153
 * **urgent**: [<1 week](https://progress.opensuse.org/issues?query_id=543)
154
 * **high**: [<1 month](https://progress.opensuse.org/issues?query_id=544)
155 124 okurz
 * **normal**: [<1 year](https://progress.opensuse.org/issues?query_id=545)
156 118 livdywan
 * **low**: undefined
157 1 mgriessmeier
158 123 okurz
* aim for cycle time of individual tickets (not epics or sagas): 1h-2w
159 31 okurz
160 331 okurz
* reference for SLOs and related topics: https://sre.google/sre-book/table-of-contents/
161
162 54 mkittler
#### Backlog prioritization
163 47 okurz
164
When we prioritize tickets we assess:
165
1. What the main use cases of openQA are among all users, be it SUSE QA engineers, other SUSE employees, openSUSE contributors as well as any other outside user of openQA
166
2. We try to understand how many persons and products are affected by feature requests as well as regressions (or "concrete bugs" as the ticket category is called within the openQA Project) and prioritize issues affecting more persons and products and use cases over limited issues
167
3. We prioritize regressions higher than work on (new) feature requests
168
4. If a workaround or alternative exists then this lowers priority. We prioritize tasks that need deep understanding of the architecture and an efficient low-level implementation over convenience additions that other contributors are more likely to be able to implement themselves.
169
170 330 okurz
#### Periodic backlog grooming
171
172
These queries can be used as help to organize our work efficiently
173
174
* [QE tools team - backlog - sorted by update time](https://progress.opensuse.org/issues?query_id=654) ensure all tickets are reasonably up-to-date and don't keep hanging around
175
* [QE tools team - due date forecast](https://progress.opensuse.org/issues?query_id=651) prevent running into due-dates proactively
176
177 38 okurz
### Team meetings
178
179 344 okurz
**NOTICE: Until further notice we will use https://meet.jit.si/suse_qa_tools due to recurring technical problems on https://meet.opensuse.org/suse_qa_tools**
180
181 341 okurz
* **Daily:** Use (internal) chat actively, e.g. formulate your findings or achievements and plans for the day, "think out loud" while working on individual problems. Optionally join [m.o.o/suse_qa_tools](https://meet.opensuse.org/suse_qa_tools) every Monday, Tuesday and Thursday 1030-1045 CET/CEST
182 359 okurz
  * *Goal*: Emergency responses, clarify next steps or blockers on current work items, asking and answering questions on tickets that would be ignored otherwise, ticket estimations (after the regular daily) (compare to [Daily Scrum](https://www.scrumguides.org/scrum-guide.html#events-daily))
183 354 livdywan
* **Ticket estimations:** Every Thursday 1110-1210 CET/CEST in [m.o.o/suse_qa_tools](https://meet.opensuse.org/suse_qa_tools) Estimate t-shirt sizes for our tickets
184 1 mgriessmeier
  * *Goal*: Ensure tickets are workable. Refine and split tickets for larger estimates.
185 354 livdywan
* **Midweekly unblock:** Every Wednesday 1110-1210 CET/CEST in [m.o.o/suse_qa_tools](https://meet.opensuse.org/suse_qa_tools) ([fallback](https://meet.jit.si/suse_qa_tools)).
186 359 okurz
  * *Goal*: Discuss tasks in progress in more detail, unblock people.
187 354 livdywan
* **Weekly coordination:** Every Friday 1110-1140(-1210) CET/CEST in [m.o.o/suse_qa_tools](https://meet.opensuse.org/suse_qa_tools) ([fallback](https://meet.jit.si/suse_qa_tools)). Community members and guests are particularly welcome to join this meeting.
188 158 okurz
  * *Goal*: Demo of features, Team backlog coordination and design decisions of bigger topics (compare to [Sprint Planning](https://www.scrumguides.org/scrum-guide.html#events-planning)).
189 166 okurz
  * *Conduction*: Demo recently finished feature work depending on [last closed](https://progress.opensuse.org/issues?query_id=572), crosscheck status of team, discuss blocked tasks and upcoming work
190 354 livdywan
* **Fortnightly Retrospective:** Friday 1140-1210 CET/CEST every odd week, same room as the weekly meeting. On these days the weekly has hard time limit of 1110-1140.
191 1 mgriessmeier
  * *Goal*: Inspect and adapt, learn and improve (compare to [Sprint Retrospective](https://www.scrumguides.org/scrum-guide.html#events-retro))
192 110 livdywan
  * *Announcements*: Create a new *discussion* with all team members in Rocket Chat and a new [retrospected game](retrospected.com) which can be filled in all week. Specific actions will be recorded as tickets.
193 329 livdywan
* **Virtual coffee:** Weekly every Monday 1100-1120 CET/CEST, same room as the weekly.
194 58 livdywan
  * *Goal*: Connect and bond as a team, understand each other (compare to [Informal Communication in an all-remote environment](https://about.gitlab.com/company/culture/all-remote/informal-communication))
195
* **extension on-demand:** Optional meeting on invitation in the suggested time slot Thursday 1000-1200 CET/CEST, in the same room as the weekly, on-demand or replacing the *Virtual coffee talk*.
196 1 mgriessmeier
  * *Goal*: Introduce, research and discuss bigger topics, e.g. backlog overview, processes and workflows
197 341 okurz
* **Workshop:** Friday 0900-0950 CET/CEST every week in [m.o.o/suse_qa_tools](https://meet.opensuse.org/suse_qa_tools) especially for community members and users! We will run this every week with the plan to move to a fortnightly cadence every even week.
198 110 livdywan
  * *Goal*: Demonstrate new and important features, explain already existing, but less well-known features, and discuss questions from the user community. All your questions are welcome!
199
  * *Announcements*: Drop a reminder with a teaser in [#testing](https://chat.suse.de/channel/testing).
200 267 okurz
  * *Recordings*: Consider recording, e.g. using OBS, and upload to youtube, link on topics link. SUSE internal topics can be published on http://streaming.nue.suse.com/i/QE-Tools-Workshops/ by ssh-uploading to ftp@streaming.nue.suse.com:~/i/QE-Tools-Workshops/ (get your SSH key added by existing team members, e.g. okurz)
201 144 livdywan
202 177 okurz
#### Best practices for meetings
203
* Meetings concerning the whole team are moderated by the scrum master by default, who should join the call early and verify that the meeting itself and any tools used are working or e.g. advise the use of the fallback option.
204
* We would prefer UTC for meeting times to be globally fair but as many other SUSE meetings are bound to European time we need to stick to that as well.
205
* It is recommended to use the Jitsi Audio-feedback feature, blue/green circles depending on microphone volume. Everybody should ensure that at least "two green balls" show up
206
* Hand signals over video can be used, e.g. "waving/circling hands": "I am lost, please bring me into discussion again"; "T-Sign": "I need a break"; "Raised hand": "I would like to speak"
207 193 okurz
* Discuss topics relevant for all within the common meetings, continue discussions pro-actively over asynchronous communication, e.g. tickets, as well as conduct topic centered follow-up meetings with only relevant attendees
208 372 kodymo
* Reminders in Slack correct for summer/winter time automatically but if you make changes on them the time might be shifted by one hour e.g. if you scheduled a reminder on 10:30 am CEST, it will become 9:30 CET after the switch
209 375 okurz
* Use https://etherpad.opensuse.org/p/suse_qe_tools for collaborative editing and put the content back into tickets or wikis
210 144 livdywan
211
#### Workshop Topics
212
213 145 livdywan
* *SUSE QE Tools roadmap*: Recent achievements, mid-term plan and future outlook. Every first Friday every month (Idea based on discussion between okurz and vpelcak 2021-02-09)
214 151 okurz
* **2021-01-15:** *DONE* [openqa-auto-review and openqa-investigate](https://youtu.be/_t3THhdiDag)
215
* **2021-01-29:** *DONE* overview of development repositories on https://github.com/os-autoinst/
216
* **2021-02-05:** *DONE* [powerpc](https://youtu.be/q1CM2AH5aKY) (@nicksinger)
217
* **2021-02-12:** *DONE* [job templates](https://youtu.be/YPuH0bcr524) (@tinita, @cdywan)
218
* **2021-02-19:** *DONE* [SUSE QEM review workflow discussions](https://youtu.be/nCIAcvD7SA8) (@dzedro, @mgrifalconi)
219
* **2021-02-26:** *DONE* open conversation
220 247 okurz
* **2021-03-05:** *DONE* [SUSE QE Tools roadmap - 2021-03](https://youtu.be/vIqBIEMH0O0) (@okurz, @mkittler)
221 164 okurz
* **2021-03-12:** *DONE* [openqa-mon](https://youtu.be/CNLihgMKt30) @ph03nix
222 151 okurz
* **2021-03-19:** *DONE* [multi-machine tests](https://youtu.be/9j-NgNTzJ0w) (@okurz; topic proposal by zluo, initially brought up as: "high RAM and storage requirements")
223 154 okurz
* **2021-03-26:** *skipped due to SUSE Hack Week*
224
* **2021-04-02:** *public holiday*
225 157 okurz
* **2021-04-09:** *DONE* [SUSE QE Tools roadmap - 2021-04](https://youtu.be/nfMilLcCosQ) (@okurz, @cdywan)
226 165 okurz
* **2021-04-16:** *DONE* [openqa.opensuse.org infrastructure overview](https://youtu.be/G5bQKI2tURk) (see question in #88831#note-19 , @okurz)
227 168 okurz
* **2021-04-23:** *DONE* [openQA tests written in Python](https://youtu.be/GjKZ51lnCh0) (@okurz, @cdywan)
228 189 okurz
* **2021-04-30:** *DONE* [openqa-review: A review helper script for openQA with complete test overview reports](https://youtu.be/J2eI0gKnQNM) (@okurz)
229 191 okurz
* **2021-05-07:** *DONE* [SUSE QE Tools roadmap - 2021-05](https://youtu.be/J2eI0gKnQNM) (@okurz, @cdywan)
230 195 okurz
* **2021-05-14:** *DONE* [Review badges and recent changes related to them](https://youtu.be/rduc1z1HB-4) (@mkittler)
231 202 okurz
* **2021-05-21:** *DONE* [openQA API Playground](https://youtu.be/EfXZKbQS-Kg) (@okurz)
232 205 okurz
* **2021-05-28:** *DONE* [Tumbleweed workflows focussed on openQA](https://youtu.be/YiiuNqRPGAk) (proposal by okurz motivated by https://chat.suse.de/channel/testing?msg=EysbgG5kFrHbmjvcy , e.g. impact of failing tests, to-test manager, etc.; by okurz, dimstar?)*
233 220 okurz
* **2021-06-04:** *DONE* SUSE QE Tools roadmap - 2021-06
234
* **2021-06-11:** *DONE* [intro to os-autoinst development (demo how to investigate and test a small fix)](https://youtu.be/IeXaVb5dqy8) (@okurz, @mkittler)
235 227 okurz
* **2021-06-18:** *DONE* [How to be prepared when we introduce openQA features](https://youtu.be/wERuChD-88Y) (@cdywan, @okurz)
236 240 okurz
* **2021-06-25:** *DONE* Workflow discussions: SUSE QE aggregate tests (Proposed by okurz: We would like to learn from others how these are included in the workflow; no recording) (@okurz)
237 249 okurz
* **2021-07-02:** *DONE* [SUSE QE Tools roadmap - 2021-07](https://youtu.be/bppQFEhlfic) (@okurz, @cdywan)
238 276 okurz
* **2021-07-09:** *DONE* A glimpse into the QE Core workflow (@geor, @ilausuch)
239
* **2021-07-16:** *DONE* Testing SLES+HA & SAP Clusters with openQA (@acarvajal)
240 277 okurz
* **2021-07-23:** *DONE* [Sporadic failures](https://youtu.be/TB-QO3Ipo1E) (@punkioudi)
241 279 okurz
* **2021-07-30:** *DONE* [An Overview of the HANA Performance Continuous Integration](https://youtu.be/R4f4Lxr0-zk) (@jgwang)
242 282 livdywan
* **2021-08-06:** *DONE* [SUSE QE Tools roadmap - 2021-08](https://youtu.be/6SVV3Kb0lSI) (@tinita, @cdywan)
243 288 okurz
* **2021-08-13:** *DONE* A proposal to maintain testsuites through a [GitLab CI pipeline](https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/merge_requests/163) @apappas
244
* **2021-08-20:** *DONE* [Space management](https://youtu.be/g331EIPd_jQ) (@mkittler)
245 291 okurz
* **2021-08-27:** *DONE* [openQA soft-fails (what are they, how to use, when to use, limitations)](https://youtu.be/HZAvYw86-lw) (@okurz)
246 307 okurz
* **2021-09-03:** *DONE* [SUSE QE Tools roadmap - 2021-09](https://youtu.be/5o6hUkEfrsA) (@okurz)
247 320 okurz
* **2021-09-10:** *DONE* open conversation (@okurz)
248
* **2021-09-17:** *DONE* [discussing new openQA features (openqa-review, priorities, module search)](https://youtu.be/0-QiVh1qBbI) (@okurz)
249 324 okurz
* **2021-09-24:** *DONE* [Scripting openQA from top to bottom by phoenix](https://youtu.be/RUVtn6unMfs) (@cdywan, Felix)
250 334 okurz
* **2021-10-01:** *DONE* [SUSE QE Tools roadmap - 2021-10](https://youtu.be/n75pvgPO2L0) (@okurz)
251 345 okurz
* **2021-10-08:** *DONE* [Brainstorming and ideas for better connecting OBS+openQA (outgoing webhooks)](https://youtu.be/iRkZiNVSeKM) (@okurz, @hennevogel)
252 349 okurz
* **2021-10-15:** *DONE* [lessons learned from "Published QCOW images appear to be uncompressed" - #99579](https://youtu.be/DYe3C1HFHDQ) (@okurz)
253 360 okurz
* **2021-10-22:** *DONE* [Follow up to Testing SLES+HA & SAP Clusters with openQA: Test Results & Known Issues](https://youtu.be/nAVg_COmE5M) (@acarvajal, @okurz)
254 365 okurz
* **2021-10-29:** *DONE* [Override openQA job results with special comments](https://youtu.be/Ki_G6kR0c-o) (@okurz)
255 1 mgriessmeier
* **2021-11-05:** *DONE* [SUSE QE Tools roadmap - 2021-11](https://youtu.be/VkDkw2cE1Gg) (@mkittler)
256 374 okurz
* **2021-11-12:** *DONE* Explore integration of other tools, test frameworks, Integration, e.g. Selenium based tests in openQA (recording n/a) (@okurz, @ybonatakis)
257
* **2021-11-19:** *DONE* [Discussion & brainstorming: terraform provider for openQA (to manage machine, test suites, job groups, etc., essentially everything that lives in the database)](https://youtu.be/i1FvOishUEw) (@dancermak)
258 377 okurz
* **2021-11-26:** *DONE* [QA best practices (brainstorming session, proposal by ybonatakis)](https://youtu.be/NDD1Ku2FL04) (@okurz)
259 378 okurz
* **2021-12-03:** *DONE* [SUSE QE Tools roadmap - 2021-12](https://youtu.be/pfhXDPSCmjk) (@okurz)
260 392 okurz
* **2021-12-10:** *DONE* open conversation - Investigating failed openQA jobs, how to influence project decisions, how to learn about upcoming changes (no recording) (@cdywan)
261 409 tinita
* **2021-12-17:** *DONE* [mergify - automatic merges of pull requests and more](https://youtu.be/hhfmQCfP5tc) (@okurz)
262 387 okurz
* **2021-12-24:** *skipped due to holiday*
263
* **2021-12-31:** *skipped due to holiday*
264
* **2022-01-07:** *skipped due to holiday*
265 401 okurz
* **2022-01-14:** *open conversation* (@cdywan)
266
* **2022-01-21:** *One year of SUSE QE Tools Workshop! Let's celebrate the success and have a good plan for the future* (@okurz)
267 407 okurz
* **2022-01-28:** *auto-review with force-result* (@tinita)
268 410 okurz
* **2022-02-04:** SUSE QE Tools roadmap - 2022-02 (@okurz)
269 407 okurz
* *proposal by okurz: How we review openQA test results, by SUSE QE teams: Who volunteers from each team to present? Propose a speaker and a date!*
270
* *proposal by okurz: openQA test review best practices and recent related feature development*
271
* *SMELT showcase (@vanastasiadis)*
272
* *proposal by okurz: Scaling up: openQA result archiving and more (#64746) (@mkittler, maybe start of 2022?)*
273
* *proposal by okurz: openQA feature: Retry of jobs based on test variables (#104007) (@okurz)*
274
* *periodic proposal by okurz: How to report tickets, investigate issues, etc. (#104805)*
275 1 mgriessmeier
* *general proposal: if there are no further topics make it an "open conversation", at least from time to time :)*
276 410 okurz
* feedback from yearly workshop review: run it every second week but maybe longer, more interactive, more technical sessions, about backends and more openQA internals, from jlausuch: maybe understanding how svirt backend boots VMs in s390x, VMWare, etc?   Highlight the differences between how qemu backend spawns VMs and how others do
277 111 livdywan
278
#### Announcements
279
280
- For every meeting, regular or one-off, desired attendants should be invited to make sure a slot blocked in their calendar and reminders with the correct local time will show up when it's time to join the meeting
281
  - Create a new event, for example in Thunderbird via the *Calendar* tab or `New > Event` via the menu.
282
  - Pick your audience, for example `qa-team@suse.de` will reach test developers and reviewers, or you can select individual attendants via their respective email addresses.
283
  - Add attendees accordingly.
284
  - Specify the time of the meeting
285
  - Set a schedule to repeat the event if applicable.
286
  - Add a location, e.g. https://meet.opensuse.org/suse_qa_tools
287
  - Don't worry if any of the details might change - you can update the invitation later and participants will be notified.
288
- See the respective meeting for regular actions such as communication via chat
289 73 okurz
290
### Team
291
292 339 livdywan
The team is comprised of engineers from different teams, some only partially available:
293 209 okurz
* Cris Dywan (Scrum Master) @cdywan / [@kalikiana](https://github.com/kalikiana)
294 326 dheidler
* Oliver Kurz (Product Owner)
295 1 mgriessmeier
* Marius Kittler
296 315 kraih
* Nick Singer (only OPS)
297 380 livdywan
* Sebastian Riedel (Part time, **no alert duty**) @kraih / [@kraih](https://github.com/kraih)
298 343 VANASTASIADIS
* Tina Müller (Part time (35h)) @tinita / [@perlpunk](https://github.com/perlpunk)
299 382 okurz
* Jan Baier (part time, QEM-dedicated work areas)
300 396 livdywan
* Ondřej Súkup (dedicated work areas) @osukup / [@mimi1vx](https://github.com/mimi1vx)
301 398 livdywan
* Moritz Kodytek @kodymo / [@FruitFly638](https://github.com/FruitFly638)
302 107 livdywan
303
### Onboarding for new joiners
304
305 389 mkittler
* Request to get added to the [tools team on GitHub](https://github.com/orgs/os-autoinst/teams/tools-team) and subscribe to notifications for projects within that organization
306
* Subscribe to notifications of the [Mojo-IOLoop-ReadWriteProcess project on GitHub](https://github.com/openSUSE/Mojo-IOLoop-ReadWriteProcess) as it is also closely related to openQA development
307 255 okurz
* Login at [stats.openqa-monitor.qa.suse.de](https://stats.openqa-monitor.qa.suse.de/alerting/list) with NIS/LDAP credentials and ask to be given the *admin* role
308 107 livdywan
* Watch this wiki page (click "Watch" button on top of this page)
309 302 livdywan
* Subscribe to [osd-admins@suse.de](http://mailman.suse.de/mailman/listinfo/osd-admins), [openqa@suse.de](http://mailman.suse.de/mailman/listinfo/openqa) and [opensuse-factory@opensuse.org](https://lists.opensuse.org/archives/list/factory@lists.opensuse.org)
310 234 livdywan
* Join #suse-qe-tools:opensuse.org (matrix) and [team-qa-tools on Slack](https://suse.slack.com/archives/C02AJ1E568M)
311 395 tinita
* Request to join [devel:openQA on OBS](https://build.opensuse.org/project/show/devel:openQA) and check that you have `Request created`, `New comment for request created`, `New comment for project created`, `New comment for package created` enabled for `Maintainer of the target` in your [OBS notification settings](https://build.opensuse.org/my/subscriptions) (staging bot writes reminder comments on open reviews)
312 393 tinita
* Add [devel:openQA on OBS](https://build.opensuse.org/project/show/devel:openQA) to your watchlist
313 107 livdywan
* Connect to `#opensuse-factory` on *libera.chat*, see "Common tasks for team members - Monitor" above
314 262 livdywan
* Request admin access on [osd](http://openqa.suse.de/) and [o3](http://openqa.opensuse.org/)
315 200 livdywan
* Request to get added to the [QA project in Progress](https://progress.opensuse.org/projects/qa/settings/members) and *enable notifications for the openQA project* in [your account settings](https://progress.opensuse.org/my/account)
316 1 mgriessmeier
* Request to get added to the [openqa team in GitLab](https://gitlab.suse.de/groups/openqa/-/group_members)
317 351 okurz
* Add your ssh key to https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/sshd/users.sls with a merge request
318 162 okurz
* Add your ssh key to gitlab.suse.de/qa-maintenance/qamops/-/blob/master/ansible/books/vars/main.yml with a merge request
319 352 okurz
* Ask an existing admin, e.g. other members of the team, to add your username and ssh key to o3, see https://progress.opensuse.org/projects/openqav3/wiki/#SSH-configuration
320 253 tinita
* Ensure you are subscribed to all projects referenced in https://progress.opensuse.org/projects/qa/wiki#Common-tasks-for-team-members
321 238 livdywan
* ~~Ensure you have access to https://gitlab.suse.de/OPS-Service/monitoring (create EngInfra ticket otherwise) and add yourself in https://gitlab.suse.de/OPS-Service/monitoring/-/tree/master/icinga/shared/contacts to receive monitoring information~~ EngInfra does not grant access to additional people currently. That might change again in the future.
322 355 livdywan
* Ask for access to the vacations calendar (on demand, via invitation)
323
* Ask for access to the meetings calendar (on demand, via invitation)
324 107 livdywan
* *Watch* [qa-tools-backlog-assistant](https://github.com/os-autoinst/qa-tools-backlog-assistant) and choose *All Activity*
325 370 livdywan
* Ensure you can access thruk.suse.de via NIS/LDAP credentials
326 45 okurz
327
### Alert handling
328
329
#### Best practices
330
331
* "if it hurts, do it more often": https://www.martinfowler.com/bliki/FrequencyReducesDifficulty.html
332
* Reduce [Mean-time-to-Detect (MTTD)](https://searchitoperations.techtarget.com/definition/mean-time-to-detect-MTTD) and [Mean-time-to-Recovery](https://raygun.com/blog/what-is-mttr/)
333
334
#### Process
335 294 okurz
336
* React on any alert or report of an outage
337
* If users report outages of components of our infrastructure
338
  * Consider forming a task force and work together
339
  * Inform the affected users about the impact, mitigation/workarounds and ETA for resolution
340 316 okurz
* For each failing alert, e.g. grafana
341 45 okurz
 * Create a ticket for the issue (with a tag "alert"; create ticket unless the alert is trivial to resolve and needs no improvement; if an alert is unhandled for at least 4h then a ticket must be created; even create a ticket if alerts turn to "ok" to prevent these issues in the future and to improve the alter)
342
 * Link the corresponding grafana panel in the ticket
343 381 okurz
 * Respond to the notification email with a link to the ticket or forward the email to a corresponding mailing list, e.g. o3-admins@suse.de or osd-admins@suse.de (Caveat: gitlab@suse.de as sender seems to be able to receive emails and swallow them without any useful response or error message)
344 51 okurz
 * Optional: Inform in chat
345 46 okurz
 * Optional: Add "annotation" in corresponding grafana panel with a link to the corresponding ticket 
346 45 okurz
 * Pause the alert if you think further alerting the team does not help (e.g. you can work on fixing the problem, alert is non-critical but problem can not be fixed within minutes)
347
* If you consider an alert non-actionable then change it accordingly
348 335 okurz
* If you do not know how to handle an alert ask the team for help
349 45 okurz
* We must always strive for an accepted hypothesis when we want to change alerts or call an issue resolved
350
* After resolving the issue add explanation in ticket, unpause alert and verify it going to "ok" again, resolve ticket
351
352
#### References
353
354
* https://nl.devoteam.com/en/blog-post/monitoring-reduce-mean-time-recovery-mttr/
355 297 tinita
356
#### Gitlab Pipeline Notifications
357
358 305 okurz
Currently, the following projects are configured to write an email to osd-admins@suse.de if a pipeline fails:
359 383 livdywan
* [openqa/auto-review](https://gitlab.suse.de/openqa/auto-review/-/services/pipelines_email/edit)
360
* [openqa/grafana-webhook-actions](https://gitlab.suse.de/openqa/grafana-webhook-actions/-/services/pipelines_email/edit)
361
* [openqa/monitor-o3](https://gitlab.suse.de/openqa/monitor-o3/-/services/pipelines_email/edit)
362
* [openqa/openqa-review](https://gitlab.suse.de/openqa/openqa-review/-/services/pipelines_email/edit)
363
* [openqa/osd-deployment](https://gitlab.suse.de/openqa/osd-deployment/-/services/pipelines_email/edit)
364
* [openqa/salt-states-openqa](https://gitlab.suse.de/openqa/salt-states-openqa/-/services/pipelines_email/edit)
365
* [openqa/salt-pillars-openqa](https://gitlab.suse.de/openqa/salt-pillars-openqa/-/services/pipelines_email/edit)
366
* [qa-maintenance/bot-ng](https://gitlab.suse.de/qa-maintenance/bot-ng/-/services/pipelines_email/edit)
367
* [qa-maintenance/openQABot](https://gitlab.suse.de/qa-maintenance/openQABot/-/services/pipelines_email/edit)
368 297 tinita
369 383 livdywan
- The configuration can be found by going to **Settings** > **Integrations** > **Pipeline Status Emails** (for any new projects the plugin will need to be enabled first)
370
- There's no way to subscribe as a user - instead an email address must be added
371 336 okurz
372
#### Weekly alert duty
373 337 okurz
374 336 okurz
We all should react on alert but additionally we can have one person on "alert duty" for one week each to ensure quicker reaction times when other team members are focussed on development work. For this the person on duty should do the following:
375 337 okurz
376
* React quickly (e.g. within some minutes or at latest hours) on any unhandled alerts
377
* Hand over to the next person on the beginning of the week, going by the order of team members in the wiki
378 336 okurz
* Asks for standin on unavailabilities
379
380 224 okurz
### Things to try
381 223 okurz
* Everybody can be "Product Owner" or "Scrum Master" or "Admin" or "Developer" for some time to get the different perspective
382 1 mgriessmeier
* From time to time ask stakeholders for their list of priorities regarding our tasks
383 361 okurz
384
### Literature references
385
386
* https://xahteiwi.eu/resources/presentations/no-we-wont-have-a-video-call-for-that/
387 99 okurz
388
### Extra-ordinary "hack-week" 2020-W51
389
390 105 okurz
SUSE QE Tools plans to have an internal "hack-week": Condition: We close 30 tickets from our backlog within the time frame 2020-12-03 until 2020-12-11 start of weekly meeting. No cheating! :) See [this query](https://progress.opensuse.org/issues?utf8=%E2%9C%93&set_filter=1&sort=priority%3Adesc%2Cid%3Adesc&f%5B%5D=status_id&op%5Bstatus_id%5D=c&f%5B%5D=fixed_version_id&op%5Bfixed_version_id%5D=%3D&v%5Bfixed_version_id%5D%5B%5D=418&f%5B%5D=closed_on&op%5Bclosed_on%5D=%3E%3C&v%5Bclosed_on%5D%5B%5D=2020-12-03&v%5Bclosed_on%5D%5B%5D=2020-12-11&f%5B%5D=&c%5B%5D=subject&c%5B%5D=project&c%5B%5D=status&c%5B%5D=assigned_to&c%5B%5D=relations&c%5B%5D=priority&c%5B%5D=category&c%5B%5D=cf_16&group_by=status&t%5B%5D=). During week 2020-W51 everyone is allowed to work on any hack-week project, it should just have a reasonable, "explainable" connection to our normal work. okurz volunteers to take over ops-duty for the week.
391
392 115 okurz
Result during meeting 2020-12-11: We missed the goal (by a slight amount) but we are motivated to try again in the next year :) Everybody, put some easy tickets aside for the next time!
393
394
### Extra-ordinary "hack-week" 2021-W8
395
396 129 okurz
Similar as our attempt for 2020-W51 with same rules, except condition: We close 30 tickets from our backlog within the time frame 2021-02-05 until 2021-02-19 start of weekly meeting. No cheating! See [this query](https://progress.opensuse.org/issues?utf8=%E2%9C%93&set_filter=1&sort=priority%3Adesc%2Cid%3Adesc&f%5B%5D=status_id&op%5Bstatus_id%5D=c&f%5B%5D=fixed_version_id&op%5Bfixed_version_id%5D=%3D&v%5Bfixed_version_id%5D%5B%5D=418&f%5B%5D=closed_on&op%5Bclosed_on%5D=%3E%3C&v%5Bclosed_on%5D%5B%5D=2021-02-05&v%5Bclosed_on%5D%5B%5D=2021-02-19&f%5B%5D=&c%5B%5D=subject&c%5B%5D=project&c%5B%5D=status&c%5B%5D=assigned_to&c%5B%5D=relations&c%5B%5D=priority&c%5B%5D=category&c%5B%5D=cf_16&group_by=status&t%5B%5D=).
397
398 31 okurz
Result during meeting 2021-02-19: We missed the goal (25/30 tickets resolved) but again we are open to try again, maybe after next SUSE hack week.
399
400 64 okurz
### Historical
401 62 okurz
402 27 okurz
Previously the former QA tools team used target versions "Ready" (to be planned into individual milestone periods or sprints), "Current Sprint" and "Done". However the team never really did use proper time-limited sprints so the distinction was rather vague. After having tickets "Resolved" after some time the PO or someone else would also update the target version to "Done" to signal that the result has been reviewed. This was causing a lot of ticket update noise for not much value considering that the [Definition-of-Done](https://progress.opensuse.org/projects/openqav3/wiki/#ticket-workflow) when properly followed already has rather strict requirements on when something can be considered really "Resolved" hence the team eventually decided to not use the "Done" target version anymore. Since about 2019-05 (and since okurz is doing more backlog management) the team uses priorities more as well as the status "Workable" together with an explicit team member list for "What the team is working on" to better visualize what is making team members busy regardless of what was "officially" planned to be part of the team's work. So we closed the target version. On 2020-07-03 okurz subsequently closed "Current Sprint" as also this one was in most cases equivalent to just picking an assignee for a ticket or setting to "In Progress". We can just distinguish between "(no version)" meaning untriaged, "Ready" meaning tools team should consider picking up these issues and "future" meaning that there is no plan for this to be picked up. Everything else is defined by status and priority.
403 128 okurz
In 2020-10-27 we discussed together to find out the history of the team. We clarified that the team started out as a not well defined "Dev+Ops" team. "team responsibilities" have been mainly unchanged since at least beginning of 2019. We agreed that learning from users and production about our "Dev" contributions is good, so this part of "Ops" is responsibility of everyone.
404
405 104 okurz
Also see #73060 for more details about how the responsibilities were setup.
406
407 258 okurz
## Change announcements
408 104 okurz
409 69 tjyrinki_suse
For new, cool features or disruptive changes consider providing according notifications to our common userbase as well as potential future users, for example create post on opensuse-factory@opensuse.org , link to post on openqa@suse.de , invite for workshop, post on one.suse.com, #opensuse-factory (IRC) (irc://irc.libera.chat/opensuse-factory), [#testing (RC)](https://chat.suse.de/testing)
410 1 mgriessmeier
411 70 tjyrinki_suse
# QE Core and QE Yast - Team descriptions
412 68 tjyrinki_suse
413 70 tjyrinki_suse
(this chapter has seen changes in 2020-11 regarding QSF -> QE Core / QE Yast change)
414 7 szarate
415 237 tjyrinki_suse
**QE Core** (formerly QSF, QA SLE Functional) and **QE Yast** are squads focusing on Quality Engineering of the core and yast functionality of the SUSE SLE products. The squad is comprised of members of QE Integration - [SUSE QA SLE Nbg](https://wiki.suse.net/index.php/SUSE-Quality_Assurance/Organization/Members_and_Responsibilities#QA_SLE_NBG_Team), including [SUSE QA SLE Prg](https://wiki.suse.net/index.php/SUSE-Quality_Assurance/Organization/Members_and_Responsibilities#QA_SLE_PRG_Team) - and QE Maintenance people (formerly "QAM"). The [SLE Departement](https://wiki.suse.net/index.php/SUSE-Quality_Assurance/SLE_Department#QSF_.28QA_SLE_Functional.29) page describes our QA responsibilities. We focus on our automatic tests running in [openQA](https://openqa.suse.de) under the job groups "Functional" as well as "Autoyast" for the respective products, for example [SLE 15 / Functional](https://openqa.suse.de/group_overview/110) and [SLE 15 / Autoyast](https://openqa.suse.de/group_overview/129). We back our automatic tests with exploratory manual tests, especially for the product milestone builds. Additionally we care about corresponding openSUSE openQA tests (see as well https://openqa.opensuse.org).
416 1 mgriessmeier
417
* More recent scope of QE Core's testing (under work, hopefully to be replicated here later) https://confluence.suse.com/display/qasle/Tests+Maintained+by+QE+Core
418
* long-term roadmap: http://s.qa.suse.de/qa-long-term
419
* overview of current openQA SLE12SP5 tests with progress ticket references: https://openqa.suse.de/tests/overview?distri=sle&version=12-SP5&groupid=139&groupid=142
420 3 szarate
* fate tickets for SLE12SP5 feature testing: based on http://s.qa.suse.de/qa_sle_functional_feature_tests_sle12sp5 new report based on all tickets with milestone before SLE12SP5 GM, http://s.qa.suse.de/qa_sle_functional_feature_tests_sle15sp1 for SLE15SP1
421 1 mgriessmeier
* only "blocker" or "shipstopper" bugs on "interesting products" for SLE15 http://s.qa.suse.de/qa_sle_functional_bug_query_sle15_2, http://s.qa/qa_sle_bugs_sle12_2 for SLE12
422 27 okurz
* Better organization of planned work can be seen at the [SUSE QA](https://progress.opensuse.org/projects/suseqa) project (which is not public).
423 1 mgriessmeier
424
## Test plan
425
426 19 okurz
When looking for coverage of certain components or use cases keep the [openQA glossary](http://open.qa/docs/#concept) in mind. It is important to understand that "tests in openQA" could be a scenario, for example a "textmode installation run", a combined multi-machine scenario, for example "a remote ssh based installation using X-forwarding", or a test module, for example "vim", which checks if the vim editor is correctly installed, provides correct rendering and basic functionality. You are welcome to contact any member of the team to ask for more clarification about this.
427
428 1 mgriessmeier
In detail the following areas are tested as part of "SLE functional":
429
430
* different hardware setups (UEFI, acpi)
431
* support for localization
432 26 riafarov
* openSUSE: virtualization - some "virtualization" tests are active on o3 with reduced set compared to SLE coverage (on behalf of QA SLE virtualization due to team capacity constraints, clarified in QA SLE coordination meeting 2018-03-28)
433
* openSUSE: migration - comparable to "virtualization", a reduced set compared to SLE coverage is active on o3 (on behalf of QA SLE migration due to team capacity constraints, clarified in QA SLE coordination meeting 2018-04)
434 69 tjyrinki_suse
435
### QE Yast
436 1 mgriessmeier
437 384 maritawerner
https://confluence.suse.com/display/QYT/QE+YaST+Team
438 1 mgriessmeier
439
### QE Core
440
441 264 szarate
"Testing is the future, and the future starts with you"
442
443
* Current definitions can be found at https://confluence.suse.com/display/qasle/Tests+Maintained+by+QE+Core, 
444 6 okurz
445
Note: Link mentioned above is WIP; QE-Core's work has impact on the openSUSE community as well, to keep the community in sync, either https://progress.opensuse.org/projects/qa/wiki#QE-Core or a better place has to be used to share what is the scope of work, always keeping to a unique source of truth, that is available to the community, keeping SLE's specific information, available to SUSE employees only. 
446 1 mgriessmeier
447 221 okurz
* Latest report based on openQA test results SLE12: http://s.qa.suse.de/test-status-sle12-functional , SLE15: http://s.qa.suse.de/test-status-sle15-functional
448 1 mgriessmeier
449
## In new organization also covered by QE Core and others
450
451 27 okurz
* quarterly updated media: former QA Maintenance (QAM) is now part of the various QE squads. However, QU media does happen together with Maintenance Coordination that is not part of these squads.
452 1 mgriessmeier
453
## What we do
454 12 okurz
455 27 okurz
We collected opinions, personal experiences and preferences starting with the following four topics: What are fun-tasks ("new tests", "collaborate", "do it right"), what parts are annoying ("old & sporadic issues"), what do we think is expected from qsf-u ("be quick", "keep stuff running", "assess quality") and what we should definitely keep doing to prevent stakeholders becoming disappointed ("build validation", "communication & support").
456 12 okurz
457
### How we work on our backlog
458
459 1 mgriessmeier
* no "due date"
460 14 okurz
* we pick up tickets that have not been previously discussed
461
* more flexible choice
462
* WIP-limits:
463
 * global limit of 10 tickets "In Progress"
464 12 okurz
465
* target numbers or "guideline", "should be", in priorities:
466 69 tjyrinki_suse
 1. New, untriaged: 0
467 1 mgriessmeier
 2. Workable: 40
468
 3. New, assigned to [qe-core] or [qe-yast]: ideally less than 200 (should not stop you from triaging)
469
470
* SLAs for priority tickets - how to ensure to work on tickets which are more urgent?
471 12 okurz
 * "taken": <1d: immediate -> looking daily
472 1 mgriessmeier
 * 2-3d: urgent
473 12 okurz
 * first goal is "urgency removal": <1d: immediate, 1w: urgent
474 1 mgriessmeier
475
* our current "cycle time" is 1h - 1y (maximum, with interruptions)
476
477 27 okurz
* everybody should set priority + milestone in obvious cases, e.g. new reproducible test failures in multiple critical scenarios, in general case the PO decides
478 1 mgriessmeier
479
### How we like to choose our battles
480
481
We self-assessed our tasks on a scale from "administrative" to "creative" and found in the following descending order: daily test review (very "administrative"), ticket triaging, milestone validation, code review, create needles, infrastructure issues, fix and cleanup tests, find bugs while fixing failing tests, find bugs while designing new tests, new automated tests (very "creative"). Then we found we appreciate if our work has a fair share of both sides. Probably a good ratio is 60% creative plus 40% administrative tasks. Both types have their advantages and we should try to keep the healthy balance.
482 27 okurz
483 1 mgriessmeier
484
### What "product(s)" do we (really) *care* about?
485
486
Brainstorming results:
487
488
* openSUSE Krypton -> good example of something that we only remotely care about or not at all even though we see the connection point, e.g. test plasma changes early before they reach TW or Leap as operating systems we rely on or SLE+packagehub which SUSE does not receive direct revenue from but indirect benefit. Should be "community only", that includes members from QSF though
489
* openQA -> (like OBS), helps to provide ROI for SUSE
490
* SLE(S) (in development versions)
491
* Tumbleweed
492
* Leap, because we use it
493
* SLES HA
494
* SLE migration
495
* os-autoinst-distri-opensuse+backend+needles
496
497
From this list strictly no "product" gives us direct revenue however most likely SLE(S) (as well as SLES HA and SLE migration) are good examples of direct connection to revenue (based on SLE subscriptions). Conducting a poll in the team has revealed that 3 persons see "SLE(S)" as our main product and 3 see "os-autoinst-distri-opensuse+backend+needles" as the main product. We mainly agreed that however we can not *own* a product like "SLE" because that product is mainly not under our control.
498
499 27 okurz
Visualizing "cost of testing" vs. "risk of business impact" showed that both metrics have an inverse dependency, e.g. on a range from "upstream source code" over "package self-tests", "openSUSE Factory staging", "Tumbleweed", "SLE" we consider SLE to have the highest business risk attached and therefore defines our priority however testing at upstream source level is considered most effective to prevent higher cost of bugs or issues. Our conclusion is that we must ensure that the high-risk SLE base has its quality assured while supporting a quality assurance process as early as possible in the development process. package self-tests as well as the openQA staging tests are seen as a useful approach in that direction as well as "domain specfic specialist QA engineers" working closely together with according in-house development parties.
500 1 mgriessmeier
501
## Documentation
502
503
This documentation should only be interesting for the team QA SLE functional. If you find that some of the following topics are interesting for other people, please extract those topics to another wiki section.
504
505
### QA SLE functional Dashboards
506 4 szarate
507 1 mgriessmeier
In room 3.2.15 from Nuremberg office are two dedicated laptops each with a monitor attached showing a selected overview of openQA test resuls with important builds from SLE and openSUSE.
508
Such laptops are configured with a root account with the default password for production machines. First point of contact: [slindomansilla.suse.com](mailto:slindomansilla@suse.com), (okurz@suse.de)[mailto:okurz@suse.de]
509
510
* ''dashboard-osd-3215.suse.de'': Showing current view of openqa.suse.de filtered for some job group results, e.g. "Functional"
511 24 dheidler
* ''dashboard-o3-3215.suse.de'': Showing current view of openqa.opensuse.org filtered for some job group results which we took responsibility to review and are mostly interested in
512 1 mgriessmeier
513
### dashboard-osd-3215
514
515
* OS: openSUSE Tumbleweed
516
* Services: ssh, mosh, vnc, x2x
517
* Users:
518
** root
519
** dashboard
520
* VNC: `vncviewer dashboard-osd-3215`
521
* X2X: `ssh -XC dashboard@dashboard-osd-3215 x2x -west -to :0.0`
522
** (attaches the dashboard monitor as an extra display to the left of your screens. Then move the mouse over and the attached X11 server will capture mouse and keyboard)
523
524 3 szarate
#### Content of /home/dashboard/.xinitrc
525 1 mgriessmeier
526
```
527
#
528
# Source common code shared between the
529
# X session and X init scripts
530
#
531
. /etc/X11/xinit/xinitrc.common
532
533
xset -dpms
534
xset s off
535
xset s noblank
536
[...]
537
#
538
# Add your own lines here...
539 3 szarate
#
540 1 mgriessmeier
$HOME/bin/osd_dashboard &
541
```
542
543 3 szarate
#### Content of /home/dashboard/bin/osd_dashboard
544 1 mgriessmeier
545
```
546
#!/bin/bash
547
548
DISPLAY=:0 unclutter &
549
550
DISPLAY=:0 xset -dpms
551
DISPLAY=:0 xset s off
552
DISPLAY=:0 xset s noblank
553 20 dheidler
554 3 szarate
url="${url:-"https://openqa.suse.de/?group=SLE+15+%2F+%28Functional%7CAutoyast%29&default_expanded=1&limit_builds=3&time_limit_days=14&show_tags=1&fullscreen=1#"}"
555 1 mgriessmeier
DISPLAY=:0 chromium --kiosk "$url"
556
```
557
558 3 szarate
#### Cron job:
559 1 mgriessmeier
560 23 dheidler
```
561 3 szarate
Min     H       DoM     Mo      DoW     Command
562 1 mgriessmeier
*	*	*	*	*	/home/dashboard/bin/reload_chromium
563 21 dheidler
```
564 1 mgriessmeier
565 3 szarate
#### Content of /home/dashboard/bin/reload_chromium
566 1 mgriessmeier
567
```
568
#!/bin/bash
569
570
DISPLAY=:0 xset -dpms
571
DISPLAY=:0 xset s off
572 22 dheidler
DISPLAY=:0 xset s noblank
573 21 dheidler
574
DISPLAY=:0 xdotool windowactivate $(DISPLAY=:0 xdotool search --class Chromium)
575 3 szarate
DISPLAY=:0 xdotool key F5
576 1 mgriessmeier
DISPLAY=:0 xdotool windowactivate $(DISPLAY=:0 xdotool getactivewindow)
577
```
578
579
#### Issues:
580
581
* ''When the screen shows a different part of the web page''
582
** a simple mouse scroll through vnc or x2x may suffice.
583
* ''When the builds displayed are freeze without showing a new build, it usually means that midori, the browser displaying the info on the screen, crashed.''
584
** you can try to restart midori this way:
585
*** ps aux | grep midori
586
*** kill $pid
587 25 dheidler
*** /home/dashboard/bin/osd_dashboard
588
** If this also doesn't work, restart the machine.
589
590
591
### dashboard-o3
592
593
* Raspberry Pi 3B+
594
* IP: `10.160.65.207`
595
596
#### Content of /home/tux/.xinitrc
597
```
598
#!/bin/bash
599
600
unclutter &
601
openbox &
602
xset s off
603
xset -dpms
604
sleep 5
605
url="https://openqa.opensuse.org?group=openSUSE Tumbleweed\$|openSUSE Leap [0-9]{2}.?[0-9]*\$|openSUSE Leap.\*JeOS\$|openSUSE Krypton|openQA|GNOME Next&limit_builds=2&time_limit_days=14&&show_tags=1&fullscreen=1#build-results"
606
chromium --kiosk "$url" &
607
608
while sleep 300 ; do
609
        xdotool windowactivate $(xdotool search --class Chromium)
610
        xdotool key F5
611
        xdotool windowactivate $(xdotool getactivewindow)
612
done
613
```
614
615
#### Content of /usr/share/lightdm/lightdm.conf.d/50-suse-defaults.conf
616
```
617
[Seat:*]
618
pam-service = lightdm
619
pam-autologin-service = lightdm-autologin
620
pam-greeter-service = lightdm-greeter
621
xserver-command=/usr/bin/X
622
session-wrapper=/etc/X11/xdm/Xsession
623
greeter-setup-script=/etc/X11/xdm/Xsetup
624
session-setup-script=/etc/X11/xdm/Xstartup
625
session-cleanup-script=/etc/X11/xdm/Xreset
626
autologin-user=tux
627 1 mgriessmeier
autologin-timeout=0
628
```