action #23628
closedcoordination #23454: [sle][functional][epic][sle15] Adapt former SDK tests to something equivalent for SLE15
[sle][functional][medium] Add SLE15 test corresponding to former "sdk+allpatterns" test suite
0%
Description
acceptance criteria¶
- AC1 must work for SLE12SP3/4 still
- AC2 name of the testsuite has to be relevant for all product versions
- AC3 must work on SLE15 or escalated
- AC4 state the goal of the test suite in test suite description
tasks¶
- Based on #23628#note-14 add the test suite "installation_gnome+all_patterns+all_modules" to development group
- Verify for all architectures
- Add to "Functional" group after verified
Updated by SLindoMansilla over 6 years ago
- Status changed from Workable to In Progress
- Assignee set to SLindoMansilla
Updated by SLindoMansilla over 6 years ago
- Status changed from In Progress to Blocked
- Assignee deleted (
SLindoMansilla)
Blocked by: https://progress.opensuse.org/issues/29733
Updated by SLindoMansilla over 6 years ago
- Blocked by coordination #29733: [epic][functional][u] Test suites that use "all patterns" boot from created qcow2 image added
Updated by okurz over 6 years ago
- Target version changed from Milestone 12 to Milestone 13
Updated by riafarov about 6 years ago
- Due date changed from 2018-01-30 to 2018-02-13
- Target version changed from Milestone 13 to Milestone 14
Revisit along with blocking task.
Updated by okurz about 6 years ago
- Status changed from Blocked to Workable
I don't see how it's blocked. If unclear let's discuss in person together.
Updated by okurz about 6 years ago
- Blocked by deleted (coordination #29733: [epic][functional][u] Test suites that use "all patterns" boot from created qcow2 image)
Updated by okurz about 6 years ago
- Related to coordination #29733: [epic][functional][u] Test suites that use "all patterns" boot from created qcow2 image added
Updated by okurz about 6 years ago
- Subject changed from [sle][functional] Fix and readd sdk+allpatterns test suite to [sle][functional][medium] Fix and readd sdk+allpatterns test suite
"medium" because there are some "unknowns" how it behaves e.g. regarding how to access which repos, addons, modules, etc.
Updated by jorauch about 6 years ago
Since SDK is not available for SLE15 we want to do something equivalent for SLE15, meaning installing all patterns and all modules.
We already have such a test_suite: installation_gnome+all_patterns+all_modules
The goal of this is to test if all patterns and modules can be installed and additionally how good a high load is handled
Updated by okurz about 6 years ago
- Subject changed from [sle][functional][medium] Fix and readd sdk+allpatterns test suite to [sle][functional][medium] Add SLE15 test corresponding to former "sdk+allpatterns" test suite
- Description updated (diff)
Updated by zluo about 6 years ago
- Status changed from Workable to In Progress
- Assignee set to zluo
sles 15
on test suite available atm.
sles 12 sp4
http://openqa.suse.de/tests/1408180
atm it looks good.
Updated by zluo about 6 years ago
we call former sdk for sles 15 development tools (module):
development+allpatterns (?)
we found in /lib/main_common.pm:
SCC_ADDONS sdk
question is: should we change this name??
select_patterns_and_packages.pm is an example...
Updated by zluo about 6 years ago
sudo /var/lib/openqa/script/clone_job.pl --skip-chained-deps --from http://openqa.suse.de 1459365 VNC_TYPING_LIMIT=40 WORKER_CLASS=remote_worker-x86_64 PATTERNS=all SCC_ADDONS=sdk
Updated by zluo about 6 years ago
sudo /var/lib/openqa/script/clone_job.pl --skip-chained-deps --from http://openqa.suse.de 1459365 --host http://openqa.suse.de VNC_TYPING_LIMIT=40 WORKER_CLASS=remote_worker-x86_64 PATTERNS=all SCC_ADDONS=sdk TEST=developmenttools+allpatterns
it looks good:
http://e13.suse.de/tests/353
job created:
http://openqa.suse.de/t1465967
Updated by zluo about 6 years ago
https://openqa.suse.de/tests/1468433#
created another one by using current build. the former one doesn't start at all. WORKER_CLASS=qemu_x86_64 should be correct?
Updated by zluo about 6 years ago
- Status changed from In Progress to Resolved
https://openqa.suse.de/tests/1468433
resolved