Skip to content

Platform Acceptance Test for Web

Jump to bottom
Joshua Horton edited this page Nov 24, 2023 · 7 revisions

Warning

These acceptance tests are now deprecated as the source for formal testing. Formal testing is done against regression tests stored in a test suite managed by the test team. Developers can update acceptance tests here on the wiki, however, if the developer recommends a test needs to be added to the formal tests contact the test team.

Keyman for Web Acceptance Test Procedures

  1. These test procedures are to be run before moving from alpha to beta, or beta to stable, or before PRs are merged into stable branches.
  2. Copy these lists of tests into a new issue (for tier transitions) or a comment on the PR.
  3. Use User Testing format for documenting tests.

Remember that KeymanWeb is embedded into the iOS and Android apps, thus we need to ensure that those work properly with a KeymanWeb release as well. See the Android and iOS instructions for details.

User Testing

SUITE_INSPECT: Visual Inspection of master branch

  • TEST_CI_WEB_MASTER: Build Status Verify latest CI build of the KeymanWeb master is successful
  • TEST_CI_ANDROID_MASTER: Build Status Verify latest CI build of the Android master is successful
  • TEST_CI_IOS_MASTER: Build Status Verify latest CI build of the iOS master is successful
  • TEST_VERIFY_HISTORY: Verify web/history.md contains information on all the current changes.

SUITE_DESKTOP: Desktop Platforms

Ensure that all tests in the selections below are run on a representative set of the following browsers and setups:

  • GROUP_WINDOWS_FIREFOX
  • GROUP_WINDOWS_CHROME
  • GROUP_MACOS_SAFARI
  • GROUP_MACOS_CHROME
  • GROUP_MACOS_FIREFOX
  • GROUP_LINUX_FIREFOX

Baseline Tests

From the testing index page, use the first link ("View Keymanweb use samples") and then select "Example 1" for the following tests.

  • TEST_BASELINE_ADD_SIL_IPA: Using the "Add a keyboard by keyboard name" section, add sil_ipa.

    • Ensure the key sequence n> produces ŋ.

  • TEST_BASELINE_ADD_KM: Using the "Add a keyboard by BCP-47 language code" section, add km. A Khmer keyboard should be added (perhaps khmer_basic, but not necessarily).

  • TEST_BASELINE_ADD_KHMER_ANGKOR: Using the "Add a keyboard by keyboard name" section, add khmer_angkor.

    • Ensure the key combination Ctrl+AltB produces ឞ. Delete the character again.
    • Type the following (US) keys in sequence: s u j r k. You should see ស្រុក.
    • Continuing from the last test, hit Backspace, checking each time to ensure the output is as expected. As this is a reorder (keyboard) rule test, you should see:
      • ស្រុ
      • ស្រ
      • ស្
      • ស
      • empty text area.

  • TEST_BASELINE_ADD_SPANISH: Using the "Add a keyboard by language name(s) section", add spanish. Verify that a Spanish keyboard is added to the list.

  • TEST_BASELINE_SWEDISH: Swap to the Swedish keyboard.

    • Ensure the key sequence ' e produces é and that o \ e produces œ.

Text Selection Tests

These tests are all run with the web_context_tests keyboard on the Test unminified Keymanweb test page. They should be run on both INPUT and TEXTAREA elements. Press Ctrl+F5 to reload the page between tests.

  • TEST_SELECTION: Type abcx. Select bc and type q. The output after the final key should be aqx. (This is testing selection replacement with no matching keyboard rule.)

  • TEST_SELECTION_2: Type abcx. Select bc and type p. The output after the final key should be aqx. (This is testing selection replacement with a matching keyboard rule.)

  • TEST_CONTEXT_BASE: Type abcd. The output after the final key should be !.

  • TEST_CONTEXT_SELECTION: Type abcx. Select the x character, and type d. The output after the final key should be abcd.

  • TEST_CONTEXT_SELECTION_2: Type abcx. Select the x character, and delete it with Backspace. Type d. The output after the final key should be !.

  • TEST_CONTEXT_SELECTION_3: Type abcx. Select the x character, and type y. Press Backspace, and type d. The output after the final key should be !.

  • TEST_CONTEXT_SELECTION_4: Type xabcx. Select the abc characters, and type d. The output after the final key should be xdx.

  • TEST_SELECTION_SHIFT: Type abcx. Select bc and then press the left Shift key on the OSK. The output after pressing shift should be abcx, with bc still selected.

  • TEST_TYPING_AUTOSCROLL: Type a very long string of text into the "input field" element using the "English - English" keyboard until the text reaches its right-hand side.

    • Type three additional letters.
    • Verify that the text is automatically scrolled so that the last three characters and the caret (the thin, blinking | mark for text position) are visible.

Element Attachment Tests

  • TEST_ATTACHMENT_API: Utilize the Attachment/Enablement API functionality samples page to test the following:
    • 'auto' attachment mode properly and automatically attaches to each dynamically-added control.
    • 'manual' attachment mode results in a page with no KMW-activated controls.
    • Each 'attached' control functions as expected for the keyboard(s) selected.
    • KeymanWeb properly attaches to and detaches from each relevant type of control with the page's API-interface controls.
    • Confirm that the independent-keyboard management API functions correctly.

Site-based tests of attachment API

All behavior exhibited here should feel "normal". These tests are solely to ensure that nothing got accidentally broken.

For each of these, make use of the Attachment/Enablement API functionality test page.

  • TEST_NORMAL_USE: Ensure that the keyboard displays and works correctly when first loaded up.

    1. Click the "Create Inputs" button one time.
    2. Click / touch the new page element. The OSK should display.
    3. Use the OSK to type one or two keys. The keys should produce their expected output.
    4. Click / touch a blank area of the page. The OSK should automatically hide.

  • TEST_ELEMENT_HOPPING:

    1. Click the "Create Inputs" button one time and the "Create Textarea" button one time.
    2. Click / touch the first of the new page elements. The OSK should display.
    3. Click / touch the other page element. The OSK should remain visible.
    4. Click / tough the first element again. The OSK should remain visible.
    5. Click / touch a blank area of the page. The OSK should automatically hide.

  • TEST_SPECIFIC_KEYBOARDS:

    1. Click the "Create Inputs" button three times.
    2. Click / touch Dynamic area #0.
    3. Click the element's "Set to Dzongkha" button.
    4. Change the keyboard to French.
    5. Click Dynamic area #1's "Set to Dzongkha button.
    6. Click Dynamic area #1. The Dzongkha keyboard should be displayed.
    7. Click Dynamic area #2.
    8. Change the keyboard to Lao.
    9. Click Dynamic area #0. The French keyboard should be displayed.
    10. Click Dynamic area #2. The Lao keyboard should be displayed.
    11. Click Dynamic area #1. The Dzongkha keyboard should be displayed.
    12. Click Dynamic area #0's "Clear Keyboard" button.
    13. Click Dynamic area #0. The Lao keyboard should be displayed.

Tests CJK keyboard functionality

Use the standard Test unminified Keymanweb test page.

  • TEST_JAPANESE_TYPING: Verify that a CJK keyboard still works.

    1. Under "Add a keyboard by keyboard name", type japanese, then click Add.
    2. Select the Japanese keyboard. The OSK should change shape notably:
    image
    1. Type a. A "picker" displaying a few options should display:
    image
    1. Type 2. The second option should replace the context.

  • TEST_JAPANESE_FOCUS: Verify that a CJK keyboard is shown and hidden properly without interfering with a page's UX.

    1. Select the page's textarea element. The OSK's title bar should appear (as with step 2 for the _TYPING test).
    2. Click a blank area on the page. The OSK should automatically hide and the caret should disappear from the textarea.
    • Just in case, "caret": the blinking vertical line segment that lets you know where new characters will appear in the context.
    1. Select the page's input field (the second editable control). The OSK should reappear under the newly-selected control.
    2. Select the page's textarea element again. The OSK should remain visible, and the caret should move from the input control to the textarea control.

SUITE_TOUCH: Touch platform tests

Ensure that all tests in the selections below are run on a representative set of the following browsers and setups:

  • GROUP_ANDROID_CHROME_TOUCH
  • GROUP_ANDROID_CHROME_HARDWARE
  • GROUP_IPHONE_SAFARI_TOUCH
  • GROUP_IPHONE_SAFARI_HARDWARE
  • GROUP_IPAD_SAFARI_TOUCH
  • GROUP_IPAD_SAFARI_HARDWARE

Baseline Tests

From the testing index page, use the first link ("View Keymanweb use samples") and then select "Example 1" for the following tests.

  • TEST_BASELINE_ADD_SIL_IPA: Using the "Add a keyboard by keyboard name" section, add sil_ipa.

    • For physical devices, ensure the key sequence n> produces ŋ.
    • For touch devices, ŋ should be a subkey of n - ensure it works.

  • TEST_BASELINE_ADD_KM: Using the "Add a keyboard by BCP-47 language code" section, add km. A Khmer keyboard should be added (perhaps khmer_basic, but not necessarily).

  • TEST_BASELINE_ADD_KHMER_ANGKOR: Using the "Add a keyboard by keyboard name" section, add khmer_angkor.

    • If using a physical keyboard, ensure the key combination Ctrl+AltB produces ឞ. Delete the character again.
    • If the keyboard has four rows (phone form-factor): Type in the following sequence on touch: ស ុ ្រ (subkey of រ) ក. You should see ស្រុក.
    • If the keyboard has five rows (tablet form-factor): s u j r k. You should see ស្រុក.
      • If the number of rows shown does not match the type of device you're using, fail the test for this.
    • Continuing from the last test, hit Backspace, checking each time to ensure the output is as expected. As this is a reorder (keyboard) rule test, you should see:
      • ស្រុ
      • ស្រ
      • ស
      • empty text area.

  • TEST_BASELINE_ADD_SPANISH: Using the "Add a keyboard by language name(s) section", add spanish. Verify that a Spanish keyboard is added to the list.

  • TEST_BASELINE_SWEDISH: Swap to the Swedish keyboard.

    • If using a physical keyboard, ensure the key sequence ' e produces é and that o \ e produces œ.
    • If using a touch-based keyboard, use long-press . to output ' and then press e. The two characters should not combine.
    • If using a touch-based keyboard, ensure that long-press p and long-press G displays properly and that the subkeys produce the expected output.

  • TEST_BASELINE_CAMEROON: If using a touch-based keyboard, add the following keyboard by name: "sil_cameroon_qwerty"

    • Ensure the top two rows of the symbol layer work correctly. (These have unusual 'layer' settings.)
    • Ensure that the tri-color key (on both 'default' and 'shift' layers) changes layer appropriately and that keys pressed automatically transition back to the default layer. (The 'default' layer's variant is very unusual, as it matches a keyboard rule and changes layer, but doesn't generate direct output!)
    • Test that a subkey on the 'default' and on the 'shift' layers output the expected character.

  • TEST_BASELINE_AUTOSCROLL: Type a very long string of text into the "input field" element using the "English - English" keyboard until the text reaches its right-hand side.

    • Type three additional letters.
    • Verify that the text is automatically scrolled so that the last three characters and the caret (the thin, blinking | mark for text position) are visible.
    • Verify that the keyboard does not disappear at any point while typing and that it is still visible.

  • TEST_ROTATION: Put the test device into 'portrait' orientation - with the longer dimension held vertically.

    • Type a into the input field.
    • Rotate your device to a landscape (horizontal) orientation.
    • Verify that the OSK repositions itself at the bottom of the screen and occupies the full width of the device.
    • Rotate the device back to a portrait (vertical) orientation.
    • Again, verify that the OSK repositions itself at the bottom of the screen and occupies the full width of the device.
      • After rotation, it is possible that the previously-typed 'a' will not be visible.
      • If so, please create a separate issue for this, but do not fail the test. (It appears to be a 16.0 issue, too.)

Element Attachment Tests

  • TEST_ATTACHMENT_API: Utilize the Attachment/Enablement API functionality test page to test the following:
    • 'auto' attachment mode properly and automatically attaches to each dynamically-added control.
    • 'manual' attachment mode results in a page with no KMW-activated controls.
    • Each 'attached' control functions as expected for the keyboard(s) selected.
    • KeymanWeb properly attaches to and detaches from each relevant type of control with the page's API-interface controls.
    • Confirm that the independent-keyboard management API functions correctly.

Site-based tests of attachment API

All behavior exhibited here should feel "normal". These tests are solely to ensure that nothing got accidentally broken.

For each of these, make use of the Attachment/Enablement API functionality test page.

  • TEST_NORMAL_USE: Ensure that the keyboard displays and works correctly when first loaded up.

    1. Click the "Create Inputs" button one time.
    2. Click / touch the new page element. The OSK should display.
    3. Use the OSK to type one or two keys. The keys should produce their expected output.
    4. Click / touch a blank area of the page. The OSK should automatically hide.

  • TEST_ELEMENT_HOPPING:

    1. Click the "Create Inputs" button one time and the "Create Textarea" button one time.
    2. Click / touch the first of the new page elements. The OSK should display.
    3. Click / touch the other page element. The OSK should remain visible.
    4. Click / tough the first element again. The OSK should remain visible.
    5. Click / touch a blank area of the page. The OSK should automatically hide.

  • TEST_SPECIFIC_KEYBOARDS:

    1. Click the "Create Inputs" button three times.
    2. Click / touch Dynamic area #0.
    3. Click the element's "Set to Dzongkha" button.
    4. Change the keyboard to French.
    5. Click Dynamic area #1's "Set to Dzongkha button.
    6. Click Dynamic area #1. The Dzongkha keyboard should be displayed.
    7. Click Dynamic area #2.
    8. Change the keyboard to Lao.
    9. Click Dynamic area #0. The French keyboard should be displayed.
    10. Click Dynamic area #2. The Lao keyboard should be displayed.
    11. Click Dynamic area #1. The Dzongkha keyboard should be displayed.
    12. Click Dynamic area #0's "Clear Keyboard" button.
    13. Click Dynamic area #0. The Lao keyboard should be displayed.

SUITE_TOUCH_GESTURES: Gesture-oriented touch platform tests (new in 17.0, from feature-gestures)

Ensure that all tests in the selections below are run on a representative set of the following browsers and setups:

  • GROUP_ANDROID_CHROME_TOUCH
  • GROUP_IPHONE_SAFARI_TOUCH
  • GROUP_IPAD_SAFARI_TOUCH

Baseline Tests

TEST_10_KEY_ROTA: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select "English...", then "Classic 10-key".
  2. Verify that all of the keys numbered 1-9 aside from 7 have three or more lowercase letters as key hints.
  3. Tap the 8 key once, then wait for a second.
  4. Tap the 8 key twice in quick succession, then wait for a second.
    • Expected output: 8a.
  5. Tap the 8 key continuously for at least 2 seconds.
    • it should rotate through: 8a8, 8aa, 8ab, 8ac, 8aA, 8aB, 8aC, then back to 8a8 (and continue from there)
    • stop tapping when the new character is a capital letter.
  6. Verify that the key hints are now capitalized.
  7. Double-tap the 9 key once. A D should be emitted as the result.
  8. Repeatedly tap 9 for at least five seconds, paying attention to the key hints.
    • Whenever a lowercase letter is the result, the key hints should be lowercase
    • Whenever an uppercase letter is the result, the key hints should be uppercase

TEST_10_KEY_DIACRITICS: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select the text-area element - the first input-accepting element on the page.
    • Placeholder text: "Type here".
    • Is directly underneath "Type in your language in this text area:"
  2. Select "English...", then "Diacritic 10-key Rota".
  3. Tap the '◌̀' key. (The key between backspace [above] and enter [below], representing a diacritic)
  4. Double-tap the 8 key.
    • Expected result: à
  5. Triple-tap the '◌̀' key - a circumflex diacritic should appear over the à.
  6. Triple-tap the 9 key.
    • Expected total result: àê
  7. Tap the '◌̀' key. A diacritic should appear over the ê.
  8. Deselect the text-area element.
  9. Reselect the text-area element, placing the point of text entry (the caret) at the end, after the ê.
    • Note for future test-maintenance: the point is to trigger a context-reset.
  10. Double-tap the 8 key.
    • Expected final result: àềa image
    • For clarity:
      • With a copy of the à's accent-mark on top the original ê, as in the cropped screenshot above.
        • It looks different in raw-text form here due to GitHub's font / rendering.
      • Note: there is no matching accent-mark on the second a.

TEST_APP_10_KEY_DIACRITICS: Using the Keyman for Android test artifact...

  1. Download this KMP: https://jahorton.github.io/diacritic_rota.kmp
  2. Open / install it for use within the Keyman app.
  3. Tap the 7 key twice; verify that 77 is output.
  4. Tap the '◌̀' key. (The key between backspace [above] and enter [below], representing a diacritic)
  5. Double-tap the 8 key.
    • Expected total result: 77à
  6. Triple-tap the '◌̀' key - a circumflex diacritic should appear over the à.
  7. Triple-tap the 9 key.
    • Expected total result: 77àê
  8. Tap the '◌̀' key. A diacritic should appear over the ê.
  9. Open the in-app Settings menu.
    • Note, for test maintenance: the point of this step and the next one is to trigger a context-reset.
  10. Close the in-app Settings menu.
  11. Double-tap the 8 key.
    • Expected final result: 77àềa image
    • For clarity:
      • With a copy of the à's accent-mark on top the original ê, as in the cropped screenshot above.
        • It looks different in raw-text form here due to GitHub's font / rendering.
      • Note: there is no matching accent-mark on the second a.

TEST_BASIC_SIMPLE_SHIFT: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select "Norwegian" (for the SIL EuroLatin keyboard)
  2. Tap the spacebar. (The keyboard should be on the default [lowercase] layer after this.)
  3. Tap the shift key once.
  4. Verify that the keyboard changes to, and stays on, the shift layer.

TEST_BASIC_MODIPRESS: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select "Norwegian" (for the SIL EuroLatin keyboard)
  2. Tap the spacebar. (The keyboard should be on the default [lowercase] layer after this.)
  3. Tap and hold the shift key.
  4. Verify that the keyboard changes to the shift layer.
  5. Tap the A key, verifying that it produces an A.
  6. Release the shift key.
  7. Verify that the keyboard changes to the default layer as a result of step 6.
  8. Repeat steps 3 through 7 quickly, holding shift just long enough to tap the shift layer's A key, then releasing quickly.

TEST_BASIC_MODIPRESS_HOLD: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select "Norwegian" (for the SIL EuroLatin keyboard)
  2. Tap the spacebar. (The keyboard should be on the default [lowercase] layer after this.)
  3. Tap and hold the shift key.
  4. Verify that the keyboard changes to the shift layer.
  5. Wait at least one second.
  6. Release the shift key.
  7. Verify that the keyboard changes to the default layer as a result of step 6.

TEST_NUMERIC_FROM_SHIFT: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select "Norwegian" (for the SIL EuroLatin keyboard)
  2. Tap the spacebar. (The keyboard should be on the default [lowercase] layer after this.)
  3. Tap the shift key, making the shift layer active.
  4. Tap and hold the numeric key (123) underneath the shift key.
  5. Verify that the keyboard changes to the numeric layer - numbers in the top row, mathematical symbols elsewhere.
  6. Longpress the % key and select the ‱ subkey.
  7. Verify that ‱ is emitted as text.
  8. Release the numeric key.
  9. Verify that the keyboard changes back to the shift layer.
  10. Tap the numeric key, releasing it immediately.
  11. Repeat steps 6 and 7, longpressing the % key and select the ‱ subkey.
  12. Verify that the keyboard automatically changes back to the default (lowercase) layer.

TEST_DELAYED_SUBKEY: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select "Norwegian" (for the SIL EuroLatin keyboard)
  2. Tap the spacebar. (The keyboard should be on the default [lowercase] layer after this.)
  3. Tap the shift key, making the shift layer active.
  4. Tap and hold the numeric key (123) underneath the shift key.
  5. Verify that the keyboard changes to the numeric layer - numbers in the top row, mathematical symbols elsewhere.
  6. Longpress the % key, but do not select a subkey yet.
  7. Release the numeric key.
  8. Verify that the keyboard changes remains on the numeric layer, with the subkey menu still displayed.
  9. Select the ‱ subkey.
  10. Verify that ‱ is emitted as text and that the layer has changed back to the shift layer.

TEST_DOUBLETAP_CAPS: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select "Norwegian" - you should then see "Norwegian - EuroLatin (SIL)" in the space bar.
  2. Type All .
  3. Double-tap the shift key. Afterward, the shift key should be highlighted, and its up-arrow should have a thin line underneath, as if underlining it.
  4. Without touching the shift key at any point, type CAPS .
    • If this is impossible - i.e., the layer shifted out from underneath you - FAIL the test.
  5. Single-tap the shift key. Afterward, you should be returned to the base layer.
  6. Type work .
  7. Tap the shift key once.
  8. Without touching the shift key at any point, type Well.
    • If this is impossible - i.e., the layer did not drop the the base layer when expected - FAIL the test.
    • Expected final result, in total: All CAPS work Well

TEST_CUSTOM_MULTITAP_MODIFIER: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select "English...", then "Gesture Prototyping".
  2. Tap and hold the ◌́ key. (The key between the spacebar [left] and the Enter key [right].)
  3. A number of letters, including all of the vowels, should change to versions using the ◌́ accent mark.
  4. Tap the á and verify that the corresponding letter is output.
  5. Release the ◌́ key; you should be returned to the default layer.
  6. Note the hints on the ◌́, then triple-tap it, holding on the third tap.
  7. A number of letters, including all of the vowels, should change to versions using the ◌̂ mark
    • This corresponds to the second diacritic from the ◌́-key's hint.
  8. Tap the â and verify that the corresponding letter is output.
  9. Release the ◌́ key; you should be returned to the default layer.

TEST_ALTERNATING_SHIFT_AND_KEY: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select "English...", then "Gesture Prototyping".
  2. Tap and hold the SHIFT key
  3. Tap the H key and release it.
  4. Release the SHIFT key.
  5. Verify that an H is output and that the layer returns to default after step 4.
  6. Repeat steps 2-5 five times.
  7. Repeat steps 2-4 quickly for at least 10 seconds.
    • Do not bother checking the result layer; the priority is to be quick here.
    • FAIL this test if any output text is replaced or removed during these repetitions.
    • FAIL this test if text (either h or H) is not output each time you press the h / H key.
  8. When done with step 7's repetitions, tap the numeric (123) key and verify that the layer switches properly to keys with numbers in the top row and symbols in the middle two rows.

TEST_FLICKS_BASIC: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select "English...", then "Gesture Prototyping".
  2. Tap and hold the u key.
  3. Drag it in an northwest direction (up and to the left) for at least a key-width.
  4. Release it.
  5. Expected result: ù
  6. Tap the u key again and drag it in a northeast direction for at least a key-width before releasing it.
  7. Expected result: ú (does not replace the previous output)
  8. Tap u again and drag north (straight up) in the same manner.
  9. Expected result: û.

TEST_FLICK_CORRECTION: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select "English...", then "Gesture Prototyping".
  2. Tap and hold the u key.
  3. Drag it in an purely west direction (straight left).
  4. Release it.
  5. Expected result: ù
  6. Tap and hold the u key.
  7. Drag it purely south (straight down).
  8. Release it.
  9. Expected result: u. The flick animation and key preview should disappear.
  10. Tap and hold the u key again.
  11. Drag it up just a few pixels / millimeters - a very short distance - then release it.
  12. Expected output: u.

TEST_FLICK_LOCKING: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select "English...", then "Gesture Prototyping".
  2. Tap and hold the u key.
  3. For the following steps, pay attention to the animated preview.
  4. Drag it purely north (straight up) - you should see the û key in the preview area (assuming it's not blocked by your finger).
    • If the animation was "jumpy" - if there was a lack of motion at the same time you moved your finger, then a big "jump" to catch up - FAIL this test.
    • If any such "jumps" were directly tied to you moving your finger quickly, do not fail this test.
  5. Return your finger to its original position; the 'u' key should slide back into place.
    • Note: "original position" is kind of important; if you return slightly to the left of the original position, the next step may not work well.
  6. Now, drag your finger in a up-and-right motion: you should also see a preview for ú as you do so.
    • Again, if the animation felt "jumpy" and not well connected to your input, FAIL this test.
  7. While the ú is visible and in the center, lift your finger and end the gesture.
  8. Verify that a ú is output.
  9. Repeat steps 2 through 6 for the a key; you should see similar previews and text there. (â, á)

TEST_MODIPRESS_MULTITAP_FLICK_PREVIEW: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select "English...", then "Gesture Prototyping".
  2. Double-tap and hold the SHIFT key, keeping it stationary for all following steps.
  3. Tap and hold the U key.
  4. Verify that the key preview is visible.
  5. Drag the finger on U purely north (straight up) - you should see the Û key in the preview area (assuming it's not blocked by your finger).
  6. Verify that the flick-animation in the preview scrolls to a Û.
  7. With the Û fully in-view, release the flick.
  8. Verify that a Û is output.
  9. Repeat steps 2 through 6 quickly three times, including the "verify" steps.

TEST_FLICK_DURING_MODIPRESS: Using the standard "Test unminified KeymanWeb" test page from a mobile device...

  1. Select "English...", then "Gesture Prototyping".
  2. Tap and hold the SHIFT key, keeping it stationary for all following steps.
  3. Tap and hold the U key.
  4. For the following steps, pay attention to the animated preview.
  5. Drag it purely north (straight up) - you should see the Û key in the preview area (assuming it's not blocked by your finger).
    • If the animation was "jumpy" - if there was a lack of motion at the same time you moved your finger, then a big "jump" to catch up - FAIL this test.
    • If any such "jumps" were directly tied to you moving your finger quickly, do not fail this test.
  6. Release the SHIFT key (held since step 2).
  7. Verify that the shift layer (all uppercase) remains visible and that the flick animation is still active.
  8. Return your finger to its original position; the 'U' key should slide back into place.
  9. Now, drag your finger in a up-and-right motion: you should also see a preview for Ú as you do so.
    • Again, if the animation felt "jumpy" and not well connected to your input, FAIL this test.
  10. While the Ú is visible and in the center, tap on the Q key.
  11. Verify that the keyboard returns to the default (lowercase) layer and that either Ú or Úq is output.
    • Úq is ideal, but if your a tap is quick, you may only get the Ú.
Clone this wiki locally