Feature #10261

Test that the correct keyboard layout is set

Added by kytv 2015-09-26 06:37:41 . Updated 2020-05-05 16:02:11 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Start date:
2015-09-26
Due date:
% Done:

0%

Feature Branch:
spriver:feature/10261-test-correct-keyboard-layout
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Subtasks

Related issues

Blocked by Tails - Bug #13635: German Greeter translation uses "s" accelerator twice Resolved 2017-08-16

History

#1 Updated by kytv 2015-09-26 06:37:54

#2 Updated by spriver 2017-05-30 12:22:37

The in the Greeter set keyboard layout kann be checked with gsettings get org.gnome.desktop.input-sources sources | awk -F"'" {'print $4'}.
Example output (Arabic was set in the Greeter):
amnesiaamnesia:~$ gsettings get org.gnome.desktop.input-sources sources | awk -F"‘" {’print $4’}
ara@

#3 Updated by spriver 2017-05-30 12:24:22

  • Assignee set to spriver

#4 Updated by spriver 2017-05-31 11:38:27

  • Feature Branch set to spriver:feature/10261-test-correct-keyboard-layout

First code work is done, currently the keyboard layout is test if being set correctly to German.

#5 Updated by spriver 2017-06-01 17:24:55

  • Assignee changed from spriver to anonym
  • QA Check set to Ready for QA

Implemented now also a test that English is set as the default keyboard layout after logging in without altering any settings in the Greeter.

#6 Updated by intrigeri 2017-06-28 15:14:38

  • Target version set to Tails_3.2

#7 Updated by anonym 2017-06-29 13:33:02

  • blocks Feature #13239: Core work 2017Q3: Test suite maintenance added

#8 Updated by anonym 2017-08-16 15:32:05

  • blocked by Bug #13635: German Greeter translation uses "s" accelerator twice added

#9 Updated by anonym 2017-08-16 15:32:53

Currently I cannot test this due to Bug #13635. But I looked at the code, and it looks great! My only remark is:

Then /^the keyboard layout must be set to "(.+)" after logging in$/ do |keyboard_layout|

This step has nothing to do with “after logging in” in itself. What you try to describe is already described by running this step after the I log in to a new session step. So just kill the part I quoted.

#10 Updated by anonym 2017-09-24 07:10:38

  • Target version changed from Tails_3.2 to Tails_3.3

Postponing thanks to blocker.

#11 Updated by intrigeri 2017-09-24 09:45:43

  • blocked by deleted (Feature #13239: Core work 2017Q3: Test suite maintenance)

#12 Updated by intrigeri 2017-11-06 15:29:24

  • Target version changed from Tails_3.3 to Tails_3.5

(making anonym’s plate lighter; this can wait a bit more and is blocked anyway)

#13 Updated by intrigeri 2017-12-07 12:44:16

  • Target version deleted (Tails_3.5)

#14 Updated by intrigeri 2019-04-29 09:00:12

  • Assignee deleted (anonym)
  • QA Check deleted (Ready for QA)

Last reviewer requested code changes.

#15 Updated by sajolida 2020-05-05 16:02:12