Project

General

Profile

Wiki » History » Version 15

okurz, 2019-05-21 11:35
fix link to "SLE Departement", was "suse3.net" instead of "suse.net"

1 1 mgriessmeier
# QA SLE Functional - Team description
2
3 10 okurz
{{toc}}
4
5 15 okurz
**QSF (QA SLE Functional)** is a virtual team focusing on QA of the "functional" domain of the SUSE SLE products. The virtual team is mainly comprised of members of [SUSE QA SLE Nbg](https://wiki.suse.net/index.php/SUSE-Quality_Assurance/Organization/Members_and_Responsibilities#QA_SLE_NBG_Team) including members from [SUSE QA SLE Prg](https://wiki.suse.net/index.php/SUSE-Quality_Assurance/Organization/Members_and_Responsibilities#QA_SLE_PRG_Team). 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).
6 1 mgriessmeier
7
* long-term roadmap: http://s.qa.suse.de/qa-long-term
8 8 okurz
* 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
9
* 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
10 11 okurz
* 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
11 1 mgriessmeier
* Latest report based on openQA test results http://s.qa.suse.de/test-status , SLE12: http://s.qa.suse.de/test-status-sle12 , SLE15: http://s.qa.suse.de/test-status-sle15
12 7 szarate
* Better organization of planned work can be seen at the [SUSE QA](https://progress.opensuse.org/projects/suseqa) project (which is not public).
13 1 mgriessmeier
14
# Test plan
15
16 3 szarate
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.
17 1 mgriessmeier
18
In detail the following areas are tested as part of "SLE functional":
19
20
* different hardware setups (UEFI, acpi)
21
* support for localization
22
23
24
## QSF-y
25
26
* Installation testing
27
* RAID (levels 0, 1, 10, 5, 6)
28
* USBinstall
29
* allpatterns
30
* autoyast (installer features, profile features, reinstall, tftp, …)
31
* filesystems (btrfs, ext4, xfs; btrfs features: snapper, qgroups, balancing, send-receive)
32
* lvm (+RAID, resize, full-encrypt, cryptlvm, activate existing)
33
* dud_sdk
34
* YaST configuration modules including services
35
* default installation (gnome installation)
36
* partition layouts (GPT)
37
* medium checks (rescue system, mediacheck with integrity, memtest)
38
* Addon, extension and module selection and registration (different repository sources)
39
* Basic install and functionality tests of SLE modules, for example public cloud module, etc.
40
* registration of installed system
41
* minimal server installation
42
* SMT (only installation)
43
* remote installation (VNC, SSH, SSH+X-Forwarding)
44
* PXE-Boot
45
* different system roles (KVM, XEN)
46
* installer self-update
47
* installation system features (activation of existing volumes, hostname setting, SSH key import, etc.)
48
* special network/disk devices (zfcp, nvme, multipath, iSCSI)
49 5 okurz
* the SLE product ["RT"](https://progress.opensuse.org/issues/43199)
50 1 mgriessmeier
51
52
## QSF-u
53
54 2 mgriessmeier
"Testing is the future, and the future starts with you"
55
56 1 mgriessmeier
* basic operations (firefox, zypper, logout/reboot/shutdown)
57
* boot_to_snapshot
58
* functional application tests (kdump, gpg, ipv6, java, git, openssl, openvswitch, VNC)
59
* NIS (server, client)
60
* toolchain (development module)
61
* systemd
62 6 okurz
* "transactional-updates" as part of the corresponding SLE server role, not CaaSP
63 1 mgriessmeier
64
65 6 okurz
## Explicitly not covered by QSF
66
67
* quarterly updated media: Expected to be covered by Maintenance + QAM
68
69
70 1 mgriessmeier
### What we do
71
72
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").
73
74
#### How we work on our backlog
75
76 12 okurz
* no "due date"
77
* we pick up tickets that have not been previously discussed
78
* more flexible choice
79
* WIP-limits:
80
 * global limit of 10 tickets "In Progress"
81 1 mgriessmeier
82 14 okurz
* target numbers or "guideline", "should be", in priorities:
83
 1. New, untriaged: 0
84
 2. Workable: 40
85
 3. New, assigned to [u]: ideally less than 200 (should not stop you from triaging)
86 12 okurz
87
* SLAs for priority tickets - how to ensure to work on tickets which are more urgent?
88 1 mgriessmeier
 * "taken": <1d: immediate -> looking daily
89
 * 2-3d: urgent
90
 * first goal is "urgency removal": <1d: immediate, 1w: urgent
91
92 12 okurz
* our current "cycle time" is 1h - 1y (maximum, with interruptions)
93
94 1 mgriessmeier
* everybody should set priority + milestone in obvious cases, e.g. new reproducible test failures in multiple critical scenarios, in general case the PO decides
95
96
#### How we like to choose our battles
97
98
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.
99
100
101
#### What "product(s)" do we (really) *care* about?
102
103
Brainstorming results:
104
105
* 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
106
* openQA -> (like OBS), helps to provide ROI for SUSE
107
* SLE(S) (in development versions)
108
* Tumbleweed
109
* Leap, because we use it
110
* SLES HA
111
* SLE migration
112
* os-autoinst-distri-opensuse+backend+needles
113
114
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.
115
116
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.
117
118
119
# Documentation
120
121
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.
122
123
### QA SLE functional Dashboards
124
125
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.
126 4 szarate
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]
127 1 mgriessmeier
128
* ''dashboard-osd-3215.suse.de'': Showing current view of openqa.suse.de filtered for some job group results, e.g. "Functional"
129
* ''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
130
131
132
#### dashboard-osd-3215
133
134
* OS: openSUSE Tumbleweed
135
* Services: ssh, mosh, vnc, x2x
136
* Users:
137
** root
138
** dashboard
139
* VNC: `vncviewer dashboard-osd-3215`
140
* X2X: `ssh -XC dashboard@dashboard-osd-3215 x2x -west -to :0.0`
141
** (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)
142
143
144
#### Content of /home/dashboard/.xinitrc
145
146 3 szarate
```
147 1 mgriessmeier
#
148
# Source common code shared between the
149
# X session and X init scripts
150
#
151
. /etc/X11/xinit/xinitrc.common
152
153
xset -dpms
154
xset s off
155
xset s noblank
156
[...]
157
#
158
# Add your own lines here...
159
#
160
$HOME/bin/osd_dashboard &
161 3 szarate
```
162 1 mgriessmeier
163
164
#### Content of /home/dashboard/bin/osd_dashboard
165
166 3 szarate
```
167 1 mgriessmeier
#!/bin/bash
168
169
DISPLAY=:0 unclutter &
170
171
DISPLAY=:0 xset -dpms
172
DISPLAY=:0 xset s off
173
DISPLAY=:0 xset s noblank
174
175
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#"}"
176
for i in `seq 1 10`; do
177
  zoom=$zoom"-e ZoomIn "
178
done
179
DISPLAY=:0 midori -e Fullscreen -e Navigationbar $zoom -a "$url"
180 3 szarate
```
181 1 mgriessmeier
182
#### Cron job:
183
184 3 szarate
```
185 1 mgriessmeier
Min     H       DoM     Mo      DoW     Command
186
*	*	*	*	*	/home/dashboard/bin/reload_midori
187 3 szarate
```
188 1 mgriessmeier
189
#### Content of /home/dashboard/bin/reload_midori
190
191 3 szarate
```
192 1 mgriessmeier
#!/bin/bash
193
194
DISPLAY=:0 xset -dpms
195
DISPLAY=:0 xset s off
196
DISPLAY=:0 xset s noblank
197
198
DISPLAY=:0 xdotool search --onlyvisible --any midori windowactivate --sync key F5
199 3 szarate
```
200 1 mgriessmeier
201
#### Issues:
202
203
* ''When the screen shows a different part of the web page''
204
** a simple mouse scroll through vnc or x2x may suffice.
205
* ''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.''
206
** you can try to restart midori this way:
207
*** ps aux | grep midori
208
*** kill $pid
209
*** /home/dashboard/bin/osd_dashboard
210
** If this also doesn't work, restart the machine.