action #30583
closedcoordination #30580: [sle][functional][u][epic]Test for keyboard layout switching
[sle][functional][medium]keyboard layout switching - installer
0%
Description
Acceptance criteria¶
- AC1: Test for installer UI (graphical + textmode) changing keyboard layout(done)
- AC2: Including check for right layout during installer(done)
Tasks¶
- Read the "Motivation" section in #30580 for proposal how to do it (0.1-0.5h)
- Introduce new test variable which if set changes the layout, e.g.
INSTALL_KEYBOARD_LAYOUT=fr
(0.2-1h) - Change they keyboard layout in welcome page (0.5-2h)
- Experiment if sending any special key behaves different in qemu than on the default layout (1-6h)
Updated by okurz almost 7 years ago
- Copied to action #30586: [sle][functional][easy]keyboard layout switching - check for keyboard layout in console after first_boot added
Updated by okurz almost 7 years ago
- Copied to deleted (action #30586: [sle][functional][easy]keyboard layout switching - check for keyboard layout in console after first_boot)
Updated by JERiveraMoya almost 7 years ago
- Status changed from Workable to In Progress
- Assignee set to JERiveraMoya
Updated by JERiveraMoya almost 7 years ago
Reading the motivation section of this task.
Updated by SLindoMansilla almost 7 years ago
Updated by JERiveraMoya almost 7 years ago
- Status changed from In Progress to Feedback
Updated by JERiveraMoya almost 7 years ago
- Status changed from Feedback to In Progress
Added as a test module for SLE15 and TW.
Updated by JERiveraMoya almost 7 years ago
- Status changed from In Progress to Feedback
Updated by okurz almost 7 years ago
PR merged. IIUC the test will only be active based on the new test variable. I recommend to add scenarios with START_AFTER_TEST=gnome
or START_AFTER_TEST=textmode
respectively and EXIT_AFTER_START_INSTALL=1
for TW, Leap, SLE15 and SLE12SP4.
Updated by JERiveraMoya almost 7 years ago
- Status changed from Feedback to In Progress
Creating scenario.
Updated by okurz almost 7 years ago
I meant:
- Add new test suite on OSD for GUI with parameters
START_AFTER_TEST=gnome
andEXIT_AFTER_START_INSTALL=1
- Schedule test suite for product, e.g. in SLE15 development job group for x86_64
- See if it works
- After confirmation repeat the above for other archs, SLE12SP4, TW, Leap15
Updated by JERiveraMoya almost 7 years ago
- Subject changed from [sle][functional][easy]keyboard layout switching - installer to [sle][functional][medium]keyboard layout switching - installer
This is a verification in my local, which mimics all settings from osd using "client isos post":
http://dhcp227/tests/457
http://dhcp227/tests/456
osd is updated regarding previous configuration (Test suites, Jobs groups)
New module keyboard_selection is scheduled right after welcome module, so test suites with START_AFTER_TEST=gnome are not suitable, as they are children jobs without welcome (the system is already installed) that boot from image. The setting need to be included on a job where the installation takes place as the examples above.
Waiting for new build in osd to see if it works.
Updated by JERiveraMoya almost 7 years ago
- Status changed from In Progress to Feedback
Added schedule in Development group for the rest of archs. in sle15: Watching development group for sle15: https://openqa.suse.de/tests/overview?distri=sle&version=15&build=450.1&groupid=96 (aarch64 now is available and looks good).
Added schedule in Development group for sle12sp4, Tumbleweed and Leap only for 64bit.
Waiting for new builds in all mentioned products (in order to not mess up this groups forcing running with isos post).
Updated by JERiveraMoya almost 7 years ago
Creating this ticket relating with future implementation where I could reflect findings: https://progress.opensuse.org/issues/31585
Updated by riafarov almost 7 years ago
- Due date changed from 2018-02-13 to 2018-02-27
What is missing here?
Updated by JERiveraMoya almost 7 years ago
- Status changed from Feedback to In Progress
Still waiting for verification in Test Development groups:
https://openqa.suse.de/tests/overview?distri=sle&version=12-SP4&build=0229&groupid=132 (created needles for sle12sp4)
https://openqa.suse.de/tests/overview?distri=sle&version=15&build=450.1&groupid=96
https://openqa.opensuse.org/tests/overview?distri=opensuse&version=TumbleweedTest&build=33.185&groupid=38
Updated by JERiveraMoya almost 7 years ago
- Status changed from In Progress to Feedback
Updated by okurz almost 7 years ago
I think your test schedule for Development Tumbleweed is wrong. You should use the Medium "opensuse-DVD" and not "TumbleweedTest-DVD".
Updated by JERiveraMoya almost 7 years ago
Fixed for TW.
Probably this ticket will require to be moved to the next sprint due to the new test suites are scheduled with START_AFTER_TEST=gnome and gnome test suite is failing in most cases for sle15, sle12sp4 and TW, so we are not yet confident enough to move the test suites to prod groups.
Updated by riafarov almost 7 years ago
- Description updated (diff)
- Due date changed from 2018-02-27 to 2018-03-13
Is not yet in Functional job group
Updated by JERiveraMoya almost 7 years ago
- Status changed from Feedback to Resolved
Now both test suites are ready to be scheduled:
sle15 -> https://openqa.suse.de/admin/job_templates/110
sle12sp4 -> https://openqa.suse.de/admin/job_templates/139
tw: https://openqa.opensuse.org/admin/job_templates/1
leap: https://openqa.opensuse.org/admin/job_templates/50