-
-
Notifications
You must be signed in to change notification settings - Fork 130
chore(windows): this is a dummy PR to allow testing #15383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
User Test ResultsTest specification and instructions 🟥 SUITE_CAPSLOCK:
Results TemplateRetesting TemplateTest Artifacts |
Test ResultsTesting this PR in the "keyman-19.0.183-alpha-test-15383" build on Windows 11 arm with SUITE_CAPSLOCKGROUP_WIN11_ARM
|
|
(PR shouldn't be closed with failed tests) |
|
I have tested GROUP_WIN11_ARM in my testing I found Notepad suffered from #15333. I had the same results initially as @sze2st, however restarting Notepad and the tests in TEST_CAPSLOCK and TEST_CAPSOFF all passed. So please restart Notepad and try again. Test-bot: retest SUITE_CAPSLOCK GROUP_WIN11_ARM TEST_CAPSLOCK-1 TEST_CAPSLOCK-2 TEST_CAPSLOCK-3 TEST_CAPSLOCK-4 TEST_CAPSLOCK-5 TEST_CAPSOFF-1 TEST_CAPSOFF-2 TEST_CAPSOFF-3 TEST_CAPSOFF-4 TEST_CAPSOFF-5 Some tests in TEST_CAPSONLY failed in TSF applications. I then tested the on Windows 10 x86 and they failed there also. Win 11 x86 had failures however for me that is in a VM which has known issues for this tests. These will requre further investigation I will start with checking the latest regression tests in Dokimion in case these are out of date. |
TODO:
This is just to get ES a check list to do some extra Windows on Arm testing
Note I got these test cases from the wiki and not dokimion so they may need some updating.
User Testing
SUITE_CAPSLOCK:
Caps Lock
The test keyboard layouts are found in the keyman repo at
app/windows/src/test/manual-tests/caps-lock-stores. There is a project file for the 3 keyboards used in this test. The project file can be used to build the keyboard packages, but you can conveniently use the.kmpfile zipped and included respectively below.The test cases below expect the usage of the
capslock.kmp.zipkeyboard. That keyboard outputs pass or fail if following the test cases.Prerequisites before each test
capslock.kmp.Test cases
click to expand
TEST_CAPSLOCK-1: uppercase with virtual key
aExpected result:
pass.(with other keyboards uppercaseA)TEST_CAPSLOCK-2: lowercase with virtual key
bShiftExpected result:
pass.(with other keyboards lowercaseb)TEST_CAPSLOCK-3: capslock ignored for numbers
3ShiftExpected result:
pass.(with other keyboards#)TEST_CAPSLOCK-4: uppercase
cExpected result:
pass.(with other keyboards uppercaseC)TEST_CAPSLOCK-5: lowercase
dShiftExpected result:
pass.(with other keyboards lowercased)CapsAlwaysOff
For these tests, use a keyboard with the
caps_always_off.kmp.zipstore set. We call this keyboard capsalwaysoff below.Any keyboard with that store set will work; if you don't have one at hand you can use the
caps_always_off.kmpkeyboard. The caps_always_off.kmp keyboard will prevent switching caps lock on. As a sanity check to verify that Keyman is actually active, pressing the keyawill outputncaps_little_a, andShift+awill outputncaps_shift_A.Note: When testing in a virtual machine, use an on-screen keyboard (in VirtualBox: Input/Keyboard/Soft Keyboard) and observe the caps lock indicator of the on-screen keyboard. Using the hardware keyboard might show side effects with caps lock.
Prerequisites before each test
CapsAlwaysOffstore set, e.g.caps_always_off.kmp.Test cases
click to expand
TEST_CAPSOFF-1: sanity check
aExpected result:
ncaps_little_aTEST_CAPSOFF-2: caps lock stays off
CapsLockkeyaExpected result:
ncaps_little_aTEST_CAPSOFF-3: no caps lock while holding capslock key
CapsLockkeyaCapsLockkeyExpected result:
ncaps_little_aTEST_CAPSOFF-4: no caps lock while holding capslock key
CapsLockkeyShiftkeyaCapsLockandShiftkeysExpected result:
ncaps_shift_ATEST_CAPSOFF-5: switching turns off caps lock
aExpected result:
ncaps_little_aSHIFT: CapsOnOnly/ShiftFreesCaps
For these tests, use a keyboard with the
CapsOnOnlyandShiftFreesCapsstores set. We call this keyboard shift_frees_caps below.Any keyboard with these stores set will work; if you don't have one at hand you can use the
shift_frees_caps.kmp.zipkeyboard.The shift_frees_caps.kmp keyboard will enable caps lock by pressing the
CapsLockkey, and will turn capslock off by pressing theShiftkey. The keyboard outputs pass or fail if following the test cases.Note: When testing in a virtual machine, use an on-screen keyboard (in VirtualBox: Input/Keyboard/Soft Keyboard) and observe the caps lock indicator of the on-screen keyboard. Using the hardware keyboard might show side effects with caps lock. Except for TEST_CAPSONLY-5 which can only be reliably tested on a hardware keyboard on host OS (not a VM). For windows 10 and windows 11 with a virtual box vm-onscreen keyboard, the following happens. The VM soft keyboard does NOT actually send the Shift Shift Key Stroke through but rather will change the keys pressed for example if an
ais pressed the soft keyboard itself will change that key to aA. This means we can't Test TEST_CAPONLY-5 on a soft keyboard.Prerequisites before each test
CapsOnOnlyandShiftFreesCapsstores set, e.g.shift_frees_caps.kmp.Test cases
click to expand
TEST_CAPSONLY-1: no caps
1Expected result:
pass.TEST_CAPSONLY-2: caps
CapsLock2Expected result:
pass.TEST_CAPSONLY-3: caps doesn't toggle
CapsLockCapsLock6Expected result:
pass.TEST_CAPSONLY-4: shift turns off
CapsLockShift3ShiftExpected result:
pass.TEST_CAPSONLY-5: shift by itself turns off
Be aware of limitations when testing this on virtual machines as noted above.
CapsLockShiftExpected result: