Project

General

Profile

Feature #10261

Bug #10250: Eliminate manual test suite

Test that the correct keyboard layout is set

Added by kytv about 2 years ago. Updated 4 days ago.

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

0%

QA Check:
Ready for QA
Feature Branch:
spriver:feature/10261-test-correct-keyboard-layout
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Related issues

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

History

#1 Updated by kytv about 2 years ago

  • Parent task set to #10250

#2 Updated by spriver 6 months ago

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):
amnesia@amnesia:~$ gsettings get org.gnome.desktop.input-sources sources | awk -F"'" {'print $4'}
ara

#3 Updated by spriver 6 months ago

  • Assignee set to spriver

#4 Updated by spriver 6 months ago

  • 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 6 months ago

  • 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 6 months ago

  • Target version set to Tails_3.2

#7 Updated by anonym 5 months ago

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

#8 Updated by anonym 4 months ago

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

#9 Updated by anonym 4 months ago

Currently I cannot test this due to #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 3 months ago

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

Postponing thanks to blocker.

#11 Updated by intrigeri 3 months ago

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

#12 Updated by intrigeri about 1 month ago

  • 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 4 days ago

  • Target version deleted (Tails_3.5)

Also available in: Atom PDF