action #45404
closed
coordination #30580: [sle][functional][u][epic]Test for keyboard layout switching
[functional][y] keyboard layout switching - check for *changed* keyboard layout in console after first_boot
Added by okurz over 5 years ago.
Updated about 5 years ago.
Target version:
SUSE QA - Milestone 25+
Description
Acceptance criteria¶
- AC1: Like #30586 but with actually changed layout
Suggestions¶
- Due date set to 2019-02-26
we need to understand what the test modules already support because IIUC keymap_or_locale already supports different languages to crosscheck for but never exercises anything different than us. How about using simply autoyast to install a system with a different language? Shouldn't need a lot different language specific needles
Do we already have single installation which uses non-default keyboard layout? As I believe it might not work straight away.
riafarov wrote:
Do we already have single installation which uses non-default keyboard layout? As I believe it might not work straight away.
We do not have that. This is why I suggested autoyast as the actual check should only happen in console after first_boot
- Status changed from New to Workable
I believe that we will have issues with typing, so pre-conditional things like consoletest_setup will fail. But if we don't change installer language, it should be fine to at least finish the installation. We might need to exclude logs collection method too.
So I would propose to evaluate how feasible it is and if it's too complex, not much value, we could use yast module instead.
- Description updated (diff)
- Estimated time set to 8.00 h
- Description updated (diff)
- Related to action #46508: [qe-core][functional] Ensure to use a clean "extra" console for keymap_or_locale and / or do not try to login (at least on local backends) added
- Due date changed from 2019-02-26 to 2019-03-12
- Copied to action #47996: [functional][y][timeboxed:4h][spike] keyboard layout switching - check for *changed* keyboard layout in console after first_boot added
- Due date deleted (
2019-03-12)
- Status changed from Workable to Blocked
- Assignee set to okurz
- Target version changed from Milestone 23 to Milestone 25+
hm, with an estimate as high as 8 I would recommend to first conduct a "spike"-task -> #47996
- Due date set to 2019-06-30
setting a later due-date to not get reminders on epic
- Due date changed from 2019-06-30 to 2019-02-26
- Status changed from Blocked to Feedback
- Assignee changed from okurz to JERiveraMoya
- Status changed from Feedback to Resolved
Also available in: Atom
PDF