diff --git a/docs/tests/acceptance/README.md b/docs/tests/acceptance/README.md
new file mode 100644
index 0000000000..8bc5596902
--- /dev/null
+++ b/docs/tests/acceptance/README.md
@@ -0,0 +1,20 @@
+## Keyman Acceptance Tests
+
+This folder contains acceptance tests for Keyman products. These test procedures should be run, where possible, before moving a product from alpha to beta, or from beta to stable.
+
+A selection of these tests may also be added to pull requests as required regression tests before merging into the master branches.
+
+Each test has three main sections, with step-by-step instructions:
+
+`Setup` – prepares the environment for the test.
+
+`Action` – describes the steps required to perform the test.
+
+`Cleanup` – restores the environment to its original state.
+
+## History
+For a period of time, a test team operated separately to the Keyman development team. They used a test suite application to manage and run these acceptance tests.
+
+The test team added to the test suite as new features were introduced and bugs were fixed, helping to provide good coverage of the products.
+
+The tests were extracted on the 12th of May 2026 and converted back into Markdown format to match the Keyman User Testing syntax used on GitHub. They have been placed in /docs/tests/acceptance in the `keyman` GitHub repository.
diff --git a/docs/tests/acceptance/android.md b/docs/tests/acceptance/android.md
new file mode 100644
index 0000000000..48fea5ee75
--- /dev/null
+++ b/docs/tests/acceptance/android.md
@@ -0,0 +1,2688 @@
+# Android Acceptance Tests
+
+**TEST_106**
+
+Test case to verify History file that contains all the current changes,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `106`
+- Product: `Android`
+- Source files: `106.JSON`, `106.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC56
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click on the Keyman App from the Android device.
+2. Verify that the Keyman Application opens.
+3. Verify that the ‘Get Started’ pop up menu appears.
+4. Click the ‘More Info’ option.
+5. Verify that the Keyman for Android 15.0 Help page opens.
+6. Click the ‘Version History’ link.
+7. Verify that the Version History menu opens.
+8. Click the ‘help.keyman.com/version-history’ link.
+9. Verify that the Keyman Version History by platform page opens.
+10. Click the ‘Keyman for Android Version History’ link.
+11. Verify HISTORY.md contains all the current changes
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the the Keyman Uninstallation completed successfully
+
+
+**TEST_107**
+
+Test case for ‘Get Started’ menu from a fresh installation,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `107`
+- Product: `Android`
+- Source files: `107.JSON`, `107.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC57
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click on the Keyman App icon from the display
+2. Verify the "Get Started" menu is visible
+3. Touch "Add a keyboard for your language"
+4. Verify "Install Keyboard or Dictionary" menu appears
+5. Click the back arrow to return to "Get Started"
+6. Touch "Enable Keyman as system-wide keyboard"
+7. Verify Android system menus appear for controlling virtual keyboard
+8. Click or enable Keyman as a system keyboard.
+9. Verify that a Warning message appears on the Screen with the OK button.
+10. Click the "OK" button to dismiss the dialogs.
+11. Touch the ‘Back’ button
+12. Verify that the "Get Started" dialog box appears again.
+13. Verify "Enable Keyman as system-wide keyboard" now has a ticked checkbox.
+14. Touch "Set Keyman as default keyboard"
+15. Select ‘Keyman’ from the ‘Change Keyboard’ dialog.
+16. Verify on the "Get Started" menu that "Set Keyman as default keyboard" now has a ticked checkbox.
+17. Touch "More info" option.
+18. Verify the Info page appears with a version string at the bottom of the page.
+19. Touch the Back button (<-) to return to "Get Started" menu.
+20. Uncheck the last option 'Show "Get Started" on startup'
+21. Click the Close button from the Get Started menu dialog.
+22. Click the Back button from the Android device.
+23. Verify that the Keyman app closes from the Android device.
+24. Click the Keyman app from the Android device.
+25. Verify the "Get Started" menu does not appear.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_109**
+
+Test case for Keyman Settings menu,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `109`
+- Product: `Android`
+- Source files: `109.JSON`, `109.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC59
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes.
+6. Click the three dots button from the top right corner of the view.
+7. Click the ‘Settings’ option from the Keyman menu.
+8. Click the Installed languages option.
+9. Verify that the English keyboard appears in the menu list.
+10. Click the English Keyboard.
+11. Verify the English Settings menu appears.
+12. Click ‘EuroLatin (SIL) Keyboard option.
+13. Verify Info appears with keyboard version, help link, and QR code
+14. Click on version and verify update, if keyboard update is available,
+15. Click on Help link , if help link is available,
+16. Verify keyboard help documentation appears
+17. Click the OK button.
+18. Verify the page returns to English Settings menu
+19. Select Dictionary --> English dictionary (MTNT)
+20. Verify the Dictionary info appears
+21. Click the Back button on the English dictionary page.
+22. Verify it returns to the English Settings menu.
+23. Turn off 'Enable Predictions'
+24. Verify that the ‘Enable Corrections’ is automatically disabled.
+25. Click the Back button three times from the Keyman App.
+26. Verify that the ‘Predictive texts’ banner is not visible upon the OSK.
+27. Turn on ‘Enable Predictions’
+28. Verify that the ‘Enable Corrections’ is automatically enabled.
+29. Click the Back button three times from the Keyman App.
+30. Verify that the ‘Predictive texts banner’ is visible upon the OSK.
+31. Click ‘Dictionary’ (English dictionary (MTNT) in the English Settings view.
+32. Verify the English dictionaries view appears.
+33. Click on the ‘English dictionary (MTNT)’ option.
+34. Verify ‘Dictionary : English dictionary (MTNT) menu opens.
+35. Click the Uninstall dictionary option.
+36. Verify that a warning message ‘Would you like to delete this dictionary? Appears with Cancel and Delete buttons.
+37. Click the Delete button.
+38. Verify that the ‘Deleted’ message appears on the menu.
+39. Click the Back button three times from the Keyman app.
+40. Verify that the Predictive text banner is not visible upon the Keyboard.
+41. Click ‘Dictionary’ (English dictionary (MTNT) in the English Settings view.
+42. Verify the English dictionaries view appears.
+43. Click on the ‘English dictionary (MTNT)’ option.
+44. Verify that a warning message ‘ Dictionary added’ appears on the view.
+45. Click the Back button three times from the Keyman app.
+46. Verify that the English dictionary (Predictive text) banner appears upon the OSK.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_110**
+
+Test case for sharing a text to an external application (eg., Notes App),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `110`
+- Product: `Android`
+- Source files: `110.JSON`, `110.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC60
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes.
+6. Type ‘This is the first sentence’ in the text pane.
+7. Select ‘sentence’ text.
+8. Verify that a pop up menu displays with ‘SHARE’ option.
+9. Click the SHARE option.
+10. Verify that some apps like ‘Messages, Copy to clipboard, Gmail, Notes etc.,’ appear on the screen.
+11. Click the Notes app.
+12. Verify that a message ‘sentence’ appears on the Notes pane.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_112**
+
+Test case for verifying text size in the Keyman Text pane ,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `112`
+- Product: `Android`
+- Source files: `112.JSON`, `112.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC62
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes
+6. Type ‘This is the first sentence’ in the text pane.
+7. Click the three dots button which appear at the top right corner of the text pane.
+8. Click the ‘Text Size’ option.
+9. Verify that the Text Size dialog appear with the OK button.
+10. Verify that the default text size is 16.
+11. Set it to ‘’72’ maximum size
+12. Click the OK button.
+13. Verify that the text size of the text is changed to 72 the maximum size.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_113**
+
+Test case for Clearing text in the Keyman text pane,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `113`
+- Product: `Android`
+- Source files: `113.JSON`, `113.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC63
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes
+6. Type ‘This is the first sentence’ in the text pane.
+7. Click the three dots button which appears at the top right corner of the text pane.
+8. Verify that the Keyman menu opens.
+9. Click the Clear text option.
+10. Verify that the entire text has been removed from the text pane.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_114**
+
+Test case for verifying the Information document in Keyman,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `114`
+- Product: `Android`
+- Source files: `114.JSON`, `114.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC64
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the ‘More info’ option from the Get Started dialog box.
+5. Verify that the ‘Keyman for Android 15.0 Help’ documentation is displayed.
+6. Verify Keyman for Android version appears at the bottom of the screen.
+7. Click the Close button.
+8. Verify that the ‘Get Started’ dialog box appear on the screen.
+9. Click the Close button.
+10. Verify the ‘Get Started’ dialog closes.
+11. Click the three dots button which appear at the top right corner of the text pane.
+12. Verify that the keyman menu opens.
+13. Click the ‘Info’ option.
+14. Verify that the ‘Keyman for Android 15.0 Help’ documentation is displayed.
+15. Verify Keyman for Android version appears at the bottom of the screen.
+16. Click the Close button.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_116**
+
+Test case for CHANGING_DISPLAY_LANGUAGE,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `116`
+- Product: `Android`
+- Source files: `116.JSON`, `116.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC66
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes
+6. Click the three dots button which appears at the top right corner of the text pane.
+7. Click the Settings option.
+8. Click the ‘Display language’ option from the Settings dialog.
+9. Select ‘Khmer’
+10. Verify that the ‘Get Started’ dialog opens successfully.
+11. Verify that the UI has been changed to ‘Khmer’
+12. Verify menu selections in Khmer
+13. Click the three dots button which appears at the top right corner of the text pane.
+14. Verify the Keyman menu in Khmer.
+15. Verify Keyman text field has Khmer prompt (for “Start typing here”)
+16. Click the Settings option.
+17. Click the ‘Change Display Language’
+18. Select “English”
+19. Verify the application reloads in English language.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_117**
+
+Test case for adjust the OSK height for the current orientation (portrait or landscape),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `117`
+- Product: `Android`
+- Source files: `117.JSON`, `117.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC67
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes
+6. Click the three dots button which appears at the top right corner of the text pane.
+7. Click the Settings option.
+8. Click ‘Adjust keyboard height’ option
+9. Verify that the ‘Adjust keyboard height’ view opens.
+10. Drag the OSK height to change the keyboard height.
+11. Click back.
+12. Verify that OSK is refreshed to the selected height.
+13. Click the Settings option.
+14. Click ‘reset to defaults’ button.
+15. Click the Back button.
+16. Verify the OSK reverts to the original height.
+17. Rotate the device back to portrait orientation.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_118**
+
+Test case for SPACEBAR_CAPTION,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `118`
+- Product: `Android`
+- Source files: `118.JSON`, `118.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC68
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes
+6. Click the three dots button which appears at the top right corner of the text pane.
+7. Click the Settings option.
+8. Click ‘Spacebar caption’
+9. Verify the spacebar caption menu opens.
+10. Select the ‘Language’ radio button.
+11. Click the back button.
+12. Verify that the space bar label is ‘English’
+13. Click the Settings option.
+14. Click ‘Spacebar caption’
+15. Verify the spacebar caption menu opens.
+16. Select the ‘Keyboard’ radio button.
+17. Click the Back button.
+18. Verify the space bar label is ‘EuroLatin(SIL)’
+19. Click the Settings option.
+20. Click ‘Spacebar caption’
+21. Verify the spacebar caption menu opens.
+22. Select the ‘Language+Keyboard’’ radio button.
+23. Click the Back button.
+24. Verify the space bar label is ‘English - EuroLatin(SIL)’
+25. Click the Settings option.
+26. Click ‘Spacebar caption’
+27. Verify the spacebar caption menu opens.
+28. Select the ‘Blank’’ radio button.
+29. Click the Back button.
+30. Verify the space bar label is blank.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_120**
+
+Test case for verify OSK is visible and fills the width the bottom of the screen in Landscape orientation, [English (EuroLatin (SIL)],
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `120`
+- Product: `Android`
+- Source files: `120.JSON`, `120.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC70
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes
+6. Long-press on the q key
+7. Verify the sub key menu of the q key appears.
+8. Long-press the p key.
+9. Verify the sub key menu of the p key appears.
+10. Click the SHIFT key
+11. Verify uppercase layer appears on the Keyboard.
+12. Click the number (123) key.
+13. Verify number layer can be selected via 123
+14. Long press 1 key.
+15. Verify sub key menu of 1 appears.
+16. Long press 0 key
+17. Verify the sub key menu of 0 appears
+18. Click the Backspace key.
+19. Verify it deletes one letter or one step backward on the text pane.
+20. Click the Spacebar key.
+21. Verify it moves one step forward on the text pane.
+22. Click the Enter key.
+23. Verify the Cursor moves to the next line in the text pane.
+24. Click the three dots which appear at the top right corner of the text pane.
+25. Click the Installed Keyboard or Dictionary option from the Settings menu.
+26. Click Install from keyman.com option from the Install Keyboard or Dictionary view.
+27. Verify the Keyboard Search bar appear on the screen.
+28. Type ‘Khmer Angkor’ in the search bar.
+29. Verify the Khmer Angkor keyboard appears under results.
+30. Click on the Khmer Angkor.
+31. Verify the Install Keyboard green button appears.
+32. Click the Install Keyboard button.
+33. Verify a toast notification ‘downloading keyboard package khmer_angkor.kmp’ appears on the screen.
+34. Click the Install button from the Install Keyboard dialog.
+35. Verify the Khmer Angkor Keyboard Installed message appears.
+36. Verify the Welcome to khmer_angkor keyboard appears on the screen.
+37. Click the OK button.
+38. Verify the Khmer Angkor Keyboard appears as the active keyboard.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_121**
+
+Test case for type on the OSK would show the expected output English(EuroLatin SIL),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `121`
+- Product: `Android`
+- Source files: `121.JSON`, `121.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC71
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes
+6. Type ‘qwer’ using the OSK.
+7. Verify that ‘qwerty’ word should not appear on the suggestion banner.
+8. Type 'Run' using the OSK.
+9. Verify the word starts with 'Run' 'Running' appears on the suggestion banner.
+10. Select 'Run' word from the suggestion banner.
+11. Verify that the word 'Run' appears on the text input screen.
+12. Short-press a key ‘a’ from the OSK.
+13. Verify that the base key ‘a’ appears on the text pane.
+14. Long-press a key ‘a’.
+15. Verify that the Subkey menu of ‘a’ appears above the ‘a’ key.
+16. Select a long-press key from the menu and release it.
+17. Verify that the long-press key should appear on the text pane.
+18. Long-press a key, while keeping the finger down, move off the long-press options, and release the key.
+18. Verify it should output any letters on the text pane.
+19. Long press-press a key, while keeping the finger down, move off the long-press options, then move back on a long-press option so it’s highlighted,and release.
+20. Verify it should output the long-press key.
+21. Quickly type a long paragraph (eg., repeat the word “reply”).
+22. Verify long-press keys don’t get stuck (displayed when not touching a key).
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation is completed successfully.
+
+
+
+---
+
+**TEST_123**
+
+Test case for Portrait to Landscape Orientation in the Keyman app,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `123`
+- Product: `Android`
+- Source files: `123.JSON`, `123.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC73
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes
+6. Rotate the device to a landscape orientation.
+7. Verify the On Screen Keyboard rotates properly.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_124**
+
+Test case for Landscape to Portrait Orientation in the Keyman app,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `124`
+- Product: `Android`
+- Source files: `124.JSON`, `124.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC74
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes
+6. Rotate the device to portrait orientation.
+7. Verify the On Screen Keyboard rotates properly.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_126**
+
+Test case for verifying the System Keyboard in the Landscape mode (English (EuroLatin SIL),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `126`
+- Product: `Android`
+- Source files: `126.JSON`, `126.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC76
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes
+6. Long-press on the q key
+7. Verify the sub key menu of the q key appears.
+8. Long-press the p key.
+9. Verify the sub key menu of the p key appears.
+10. Click the SHIFT key
+11. Verify uppercase layer appears on the Keyboard.
+12. Click the number (123) key.
+13. Verify number layer can be selected via 123
+14. Long press 1 key.
+15. Verify sub key menu of 1 appears.
+16. Long press 0 key
+17. Verify the sub key menu of 0 appears
+18. Click the Backspace key.
+19. Verify it deletes one letter or one step backward on the text pane.
+20. Click the Spacebar key.
+21. Verify it moves one step forward on the text pane.
+22. Click the Enter key.
+23. Verify the Cursor moves to the next line in the text pane.
+24. Click the three dots which appear at the top right corner of the text pane.
+25. Click the Installed Keyboard or Dictionary option from the Settings menu.
+26. Click Install from keyman.com option from the Install Keyboard or Dictionary view.
+27. Verify the Keyboard Search bar appear on the screen.
+28. Type ‘Khmer Angkor’ in the search bar.
+29. Verify the Khmer Angkor keyboard appears under results.
+30. Click on the Khmer Angkor.
+31. Verify the Install Keyboard green button appears.
+32. Click the Install Keyboard button.
+33. Verify a toast notification ‘downloading keyboard package khmer_angkor.kmp’ appears on the screen.
+34. Click the Install button from the Install Keyboard dialog.
+35. Verify the Khmer Angkor Keyboard Installed message appears.
+36. Verify the Welcome to khmer_angkor keyboard appears on the screen.
+37. Click the OK button.
+38. Verify the Khmer Angkor Keyboard appears as the active keyboard.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_127**
+
+Test case for type on the System Keyboard would show the expected output English(EuroLatin SIL),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `127`
+- Product: `Android`
+- Source files: `127.JSON`, `127.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC77
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes
+6. Type ‘qwer’ using the OSK.
+7. Verify that ‘qwerty’ word should not appear on the suggestion banner.
+8. Type 'Run' using the OSK.
+9. Verify that the word starts with 'Run' 'Running' appears on the suggestion banner.
+10. Select 'Run' from the suggestion bar.
+11. Verify that the word 'Run' appears on the text input screen.
+12. Short-press a key ‘a’ from the OSK.
+13. Verify that the base key ‘a’ appears on the text pane.
+14. Long-press a key ‘a’.
+15. Verify that the Subkey menu of ‘a’ appears above the ‘a’ key.
+16. Select a long-press key from the menu and release it.
+17. Verify that the long-press key should appear on the text pane.
+18. Long-press a key, while keeping the finger down, move off the long-press options, and release the key.
+19. Verify it should output any letters on the text pane.
+20. Long press-press a key, while keeping the finger down, move off the long-press options, then move back on a long-press option so it’s highlighted,and release.
+21. Verify it should output the long-press key.
+22. Quickly type a long paragraph (eg., repeat the word “reply”).
+23. Verify long-press keys don’t get stuck (displayed when not touching a key).
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_129**
+
+Test case for Portrait to Landscape Orientation in the Keyman System Keyboard,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `129`
+- Product: `Android`
+- Source files: `129.JSON`, `129.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC79
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes
+6. Rotate the device to a landscape orientation.
+7. Verify the On Screen Keyboard rotates properly.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_130**
+
+Test case for Landscape to Portrait Orientation in the Keyman System Keyboard,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `130`
+- Product: `Android`
+- Source files: `130.JSON`, `130.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC80
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes
+6. Rotate the device to a landscape orientation.
+7. Verify the On Screen Keyboard rotates properly.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_132**
+
+Test case for verifying the External european AZERTY Keyboard,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `132`
+- Product: `Android`
+- Source files: `132.JSON`, `132.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC82
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman App from an Android device.
+2. Verify that the Keyman opens successfully
+3. Verify that the ‘Get Started’ dialog opens successfully.
+4. Click the close button from the Get Started dialog.
+5. Verify that the Get Started dialog closes.
+6. Install French Basic Keyboard.
+7. Verify the French Basic OSK appears on the Screen.
+8. Type on the top letter row ‘azerty’, from the physical keyboard.
+9. Verify ‘azerty’ appears on the text pane.
+10. Type on the 102 key.
+11. Verify < appears on the text pane.
+12. Type shift+102 Key
+13. Verify > appears on the text pane.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_133**
+
+Test case for verifying KMP distribution,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `133`
+- Product: `Android`
+- Source files: `133.JSON`, `133.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC83
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+3. Download KhmerAngkor.kmp file from keyman.com site.
+
+
+
+
+Action
+
+1. Click the Settings option from an Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Storage option from the Settings menu.
+4. Click the Apps option.
+5. Verify that it opens Apps storage menu.
+6. Click the Keyman Alpha option.
+7. Verify that Clear storage and Clear cache options are appearing in the Storage menu.
+8. Click the Clear Storage option.
+9. Verify that “Delete app data?” warning message appears with Cancel and OK buttons.
+10. Click the OK button.
+11. Verify that the Cache and User data should be cleared.
+12. Click the Keyman icon.
+13. Verify that the Keyman In-App opens.
+14. Click the “Get Started” close button.
+15. Click the Settings option.
+16. Verify that the Settings menu opens.
+17. Click the “Install Keyboard or Dictionary” option.
+18. Click the “Install from local file” option.
+19. Click the “khmer_angkor.kmp” file.
+20. Verify kmp distribution successfully installs.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_135**
+
+Test case for FLICKER_BANNER unnecessary flicker on banner while typing (7162)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `135`
+- Product: `Android`
+- Source files: `135.JSON`, `135.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC85
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. In the Keyman app with the default sil_euro_latin keyboard and lexical model enabled, start typing "Fascinating"
+2. observe whether or not the suggestion banner is flickering on each keystroke.
+3. If flickering happens, FAIL this test.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_137**
+
+Test case for BROKEN_SUGGESTION selecting the "undo" suggestion breaks subsequent input (7167)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `137`
+- Product: `Android`
+- Source files: `137.JSON`, `137.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC87
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Open Keyman In-App.
+2. Type P r o b in the text area using the touchpad.
+3. Verify that the predictive text “Problem” appears in the banner.
+4. Select Problem from banner.
+5. Press Backspace key.
+6. Select "Prob" (undoing the last suggestion).
+7. Press Spacebar.
+8. Verify the word Prob appears in the banner.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_140**
+
+Test case for Press_And_Hold_Backspace (Holding backspace appears to desync context between web and app (7172),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `140`
+- Product: `Android`
+- Source files: `140.JSON`, `140.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC90
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman icon from the Mobile device / emulator.
+2. Verify that the Keyman Application opens.
+3. Type “This is the first sentence”.
+4. Hold the Backspace key.
+5. Verify that all the letters are getting deleted one by one.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_141**
+
+Test case for Rapid_Typing (Rapid typing on first caps letter sometimes gives TWo cap letters) (7173),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `141`
+- Product: `Android`
+- Source files: `141.JSON`, `141.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC91
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+
+
+
+
+Action
+
+1. Click the Keyman icon from the Mobile device / emulator.
+2. Verify that the Keyman application opens.
+3. Type “T w o” rapidly and consecutively multiple times separated by a space. (while on the Shift layer either in the middle or beginning of the sentence).
+4. Verify “T w o” should appear multiple times on the text area.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_142**
+
+feat(android): Enhance how ENTER key is handled in apps #12125
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `142`
+- Product: `Android`
+- Source files: `142.JSON`, `142.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC276
+
+
+Setup
+
+1. Install the latest Keyman (.apk) build on an Android device / emulator.
+2. Accept android permission requests for storage
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Checked the "Enable Keyman as system-wide keyboard" box.
+6. Checked the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+1. Install the latest Keyman (.apk)build in Android device / emulator.
+2. Accept all the Android permission requests for storage
+3. Open the keyman app.
+4. Navigate to the settings page.
+5. Checked the "Enable Keyman as system-wide keyboard" box.
+6. Checked the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+Test_Google_Keep:
+1. Launch the Google Keep app.
+2. Open the empty note by clicking the "+" button.
+3. Verify that the keyman keyboard appeared on the Keep App.
+4. Enter a sentence using the keyman keyboard.
+5. Press the "Enter" key.
+6. Verify that an empty line was inserted under the sentence.
+Test_Facebook_Messaging:
+1. Launch the Facebook Messenger app.
+2. Select a person from the contact list.
+3. Verify that the keyman keyboard appeared on the Facebook Messenger app.
+4. Enter a sentence using the keyman keyboard.
+5. Press the "Enter" key.
+6. Verify that the empty line was inserted under the sentence.
+7. Click the arrow key.
+8. Verify that the message was sent to the user.
+9. Verify that the blank line was removed from the sent message.
+Test_Twitter_Search:
+1. Launch the Twitter app.
+2. Open the search box by clicking the eyeglass icon.
+3. Verify that the keyman keyboard appeared on the Twitter app.
+4. Enter a word in the search field.
+5. Press the "Enter" key.
+6. Verify that the search result appears after pressing the "Enter" key.
+1. Launch Keyman App.
+2. Navigate to the settings page by clicking the ellipsis button.
+3. Verify the Settings menu opens.
+4. Verify the "Adjust long-press delay" option appears.
+5. Click the "Adjust long-press delay" option.
+6. Verify that the "Adjustment point" and arrow buttons appear.
+7. Set the delay as 0.3 seconds.
+8. Verify that the "Delay Time" text shows after changing the delays.
+9. Navigate back to the keyman's notepad page.
+10. Verify that the default keyboard(e.g. EuroLatin SIL) appears
+11. Press any letter key and then hold it.
+12. Verify that the submenu appears after 0.3 seconds of delays.
+13. Navigate to the settings page by clicking the ellipsis button.
+14. Verify the Settings menu opens.
+15. Verify the "Adjust long-press delay" option appears.
+16. Click the "Adjust long-press delay" option.
+17. Verify that the "Adjustment point" and arrow buttons appear.
+18. Set the delay as 1.5 seconds.
+19. Verify that the "Delay Time" text shows after changing the delays.
+20. Navigate back to the keyman's notepad page.
+21. Verify that the default keyboard(e.g. EuroLatin SIL) appears
+22. Press any letter key and then hold it.
+23. Verify that the submenu appears after 1.5 seconds of delays.
+24. Select the letters from the submenu.
+25. Press any letter key and then pull down it.
+26. Verify that the letter appears after pulling down the letter.
+27. Verify that the flicker word is correct.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device or emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the keyman appears on the list.
+5. Click the Keyman option.
+6. Verify the Keyman menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation is completed successfully.
+4) feat(android): Add menu to specify long-press delay #12170
+1. Click the Settings icon from the Android device/emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman appears on the list.
+5. Click the Keyman option.
+6. Verify the Keyman menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation is completed successfully.
+
+
+
+---
+
+**TEST_144**
+
+fix(android): Auto-mirror back and forward arrows for RTL support ? #12227
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `144`
+- Product: `Android`
+- Source files: `144.JSON`, `144.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC278
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in the Android device or emulator.
+2. Accept all the Android permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Installed the "Arabic Phonetic(SIL)" keyboard by clicking Settings/Install Keyboard/Install from keyman.com.
+3. Verify the "Arabic Phonetic(SIL)" keyboard appears.
+4. Navigate to the settings page by clicking the ellipsis button.
+5. Verify the Settings menu opens.
+6. Change the UI language from English to Arabic by selecting the "Display language.".
+7. Verify the navigation and return back to the "Keyman" notepad.
+8. Verify the ellipsis and share buttons appear at the left side on top.
+9. Verify the keyman icon appears on the right side on top.
+10. Added a sentence to the notepad using the "Arabic Phonetic(SIL)" keyboard.
+11. Verify the text appears from right to left.
+12. Navigate to the settings page by clicking the ellipsis button.
+13. Verify that the "back arrow" appears on the right side.
+14. Go to "Installed Languages.".
+15. Verify that the "back arrow" appears on the right side.
+16. Verify that the "forward arrow" for installed keyboards points to the left side.
+17. Go to the EuroLatin (SIL) keyboard settings.
+18. Verify that the "back arrow" appears on the right side.
+19. Verify that the "forward arrow" for installed keyboards points to the left side.
+20. Go to the English dictionary (MTNT) Settings
+21. A blue tick appears on the right side.
+22. Verify that the "back arrow" appears on the right side
+23. Verify that the "forward arrow" for installed keyboards points to the left side.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device/emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the keyman appears on the list.
+5. Click the Keyman option.
+6. Verify the Keyman menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation is completed successfully.
+
+
+
+---
+
+**TEST_145**
+
+fix(android): Auto-mirror increment and decrement arrows for RTL support ? #12230
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `145`
+- Product: `Android`
+- Source files: `145.JSON`, `145.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC279
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build on an Android device/emulator.
+2. Accept all the Android permission requests for storage
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Installed the "Arabic Phonetic(SIL)" keyboard by clicking Settings/Install Keyboard/Install from keyman.com
+3. Verify the "Arabic Phonetic(SIL)" keyboard appears.
+4. Navigate to the settings page by clicking the ellipsis button.
+5. Verify the Settings menu opens.
+6. Change the UI language from English to Arabic by selecting the "Display language".
+7. Verify the navigation and return back to the "Keyman" notepad.
+8. Verify the ellipsis and share buttons appear on the left side at the top.
+9. Verify the keyman icon appears on the right side, on top.
+10. Added a sentence to the notepad using the "Arabic Phonetic(SIL)" keyboard.
+11. Verify the text appears from right to left.
+12. Open the "Text size" dialog by clicking the ellipsis button.
+13. Verify “A-” pointing right makes the text size smaller when clicking it.
+14. Verify “A+” pointing left makes the text size bigger when clicking it.
+15. Verify the text size changes when doing steps 13 and 14.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon on the Android device or emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the keyman appears on the list.
+5. Click the Keyman option.
+6. Verify the Keyman menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation is completed successfully.
+
+
+
+---
+
+**TEST_147**
+
+fix(android): Hide suggestion banner on password fields #12442
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `147`
+- Product: `Android`
+- Source files: `147.JSON`, `147.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC282
+
+
+Setup
+
+1. Install the latest Keyman (.apk) build in the Android device or emulator.
+2. Accept all the Android permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Verify the suggestion banner provides suggestions while typing text in the Keyman's Note app.
+3. Launch the Chrome browser.
+4. Verify the browser appears.
+5. Navigate to the "editpad.org" website.
+6. Enter some text on the page.
+7. Verify the keyman's keyboard appears.
+8. Verify the suggestion banner appears on the Keyman's banner.
+9. Open a new tab on the Chrome browser.
+10. Navigate to the https://darcywong00.github.io/examples/form.html page.
+11. Verify the test page appears.
+12. Click in the "Visible Text Field" box.
+13. Verify the OSK displays suggestions when typing text.
+14. Click in the "Password Field.".
+15. Verify the OSK disable suggestions.
+16. Verify the "Keyman banner" is showing on the OSK.
+17. Click on the "Search Field.".
+18. Verify the OSK re-enabled suggestions when typing text.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device/emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the keyman appears on the list.
+5. Click the Keyman option.
+6. Verify the Keyman menu opens.
+
+
+
+---
+
+**TEST_148**
+
+feat(android): Add controls for auto-correct #12443
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `148`
+- Product: `Android`
+- Source files: `148.JSON`, `148.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC283
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in the Android device or emulator.
+2. Accept all the Android permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Enter some text in the keyman's notepad.
+3. Verify the default "sil_euro_latin" keyboard displays suggestions.
+4. Launch the Chrome browser.
+5. Verify the browser appears.
+6. Navigate to the "editpad.org" website.
+7. Enter some text on the page.
+8. Verify the default "sil_euro_latin" keyboard displays suggestions.
+9. Return to the Keyman app --> Keyman settings --> Installed languages --> English to bring up the "English Settings" menu
+10. Verify the "Predictions with corrections" is set as the default suggestion radio selection.
+11. Select the "Predictions only"
+12. Verify "Predictions only" is the only selected option
+13. Select "Disable suggestions"
+14. Verify "Disable suggestions" is the only select option.
+15. Exit the menu and then return to Keyman Notepad.
+16. Verify the suggestion banner is now disabled and it is showing the Keyman banner.
+17. Launch the Chrome browser.
+18. Verify the browser appears.
+19. Navigate to the "editpad.org" website.
+20. Enter some text on the page.
+21. Verify the suggestion banner is now disable.
+22. Verify the Keyman banner is showing on the OSK.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device/emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the keyman appears on the list.
+5. Click the Keyman option.
+6. Verify the Keyman menu opens.
+
+
+
+---
+
+**TEST_307**
+
+Revert how keyboard picker menu launches
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `307`
+- Product: `Android`
+- Source files: `307.JSON`, `307.html`
+
+
+
+**Description**
+
+fix(android/engine): Revert how keyboard picker menu launches #12986
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in the Android device or emulator.
+2. Accept all the Android permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Chrome browser.
+2. Navigate to the "editpad.org" website.
+3. Verified that the website loaded.
+4. Click in the text area.
+5. Verified that the keyman keyboard appeared
+6. Long-press on the globe key to open the "Keyman Keyboard" picker menu.
+7. Verified that the "Keyman keyboard" list appeared
+8. Close the "Keyman Keyboard" picker menu by pressing the back button.
+9. Verified that It returns to the Chrome browser.
+10. Verified that the mouse cursor appeared in the text area.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_319**
+
+TC - fix(android): Catch WebView exceptions and prompt user to install WebView_TEST_INSTALL_CHROME
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `319`
+- Product: `Android`
+- Source files: `319.JSON`, `319.html`
+
+
+
+**Description**
+
+TC - fix(android): Catch WebView exceptions and prompt user to install WebView_TEST_INSTALL_CHROME #13140
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in the Android emulator of API 21 (Android 5.1)
+2. Enable the Android System WebView.
+3. Go to System Settings --> Apps --> All apps --> Android System WebView
+4. On the Android SystemWebView page.
+5. Click "Disable" as directed.
+6. Exit Settings
+
+
+
+
+Action
+
+1. Open the Keyman app.
+2. Dismiss the "Get Started" window.
+3. Verify that the keyboard does not display. (Ignore the keyboard Toast error which is a Javascript error )
+4. Verify that the Keyman app has a prompt for the user to "Update Chrome"
+5. Click the "Update Chrome" button on the keyman app.
+6. Verify that the device goes to the Play Store page for Chrome.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman Alpha appears on the list.
+5. Click the Keyman Alpha option.
+6. Verify the Keyman Alpha menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_321**
+
+Keyman website appeared when clicking the "+" button on the keyboard settings page.
+
+Status: `Deprecated`
+
+
+Metadata
+
+- Source ID: `321`
+- Product: `Android`
+- Source files: `321.JSON`, `321.html`
+
+
+
+**Description**
+
+TC - bug(android): Keyman website appeared when clicking the "+" button on the keyboard settings page. #12797
+
+
+Setup
+
+No steps recorded.
+
+
+
+
+Action
+
+No steps recorded.
+
+
+
+
+Cleanup
+
+No steps recorded.
+
+
+
+---
+
+**TEST_327**
+
+Handle banner overrides independently when device is locked and unlocked
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `327`
+- Product: `Android`
+- Source files: `327.JSON`, `327.html`
+
+
+
+**Description**
+
+TC - fix(android): Handle banner overrides independently when device is locked and unlocked #13546
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in the Android device or emulator.
+2. Accept all the Android permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+8. Install the basic Lao keyboard.
+
+
+
+
+Action
+
+1. Open the Keyman
+2. Select the sil_euro_latin keyboard by pressing the globe key.
+3. Verify that the suggestions appears on the banner
+4. Use the globe key to switch to the Basic Lao keyboard
+5. Verify that the image banner appears
+6. Launch Chrome and browse to "https://darcywong00.github.io/examples/form.html" test page. (It has basic text fields and a password text field)
+7. Verify that the page load correctly
+8. Click in the "Visible Text Field" box.
+9. Use the globe key to select the sil_euro_latin keyboard
+10. Verify suggestions appears on the banner
+11. Use the globe key to switch to the Basic Lao keyboard
+12. Verify that the image banner appears
+13. Use the globe key to select sil_euro_latin keyboard
+14. Verify suggestions appears on the banner
+15. Click in the "Password Field" box.
+16. Verify the suggestions are disable and the image banner appears
+17. Return the Keyman app
+18. Verify that the sil_euro_latin keyboard appeared
+19. Verify suggestions appears in the app
+20. Make sure the Keyman app is the active app
+21. Lock the device
+22. Unlock the device - use Keyman to enter the password.
+23. Verify suggestions are disable on the lock screen.
+24. When the device is unlock and the Keyman app is resume.
+25. Verify that the sil_euro_latin keyboard appears.
+26. Verify suggestions appears and showing the text.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman appears on the list.
+5. Click the Keyman option.
+6. Verify the Keyman menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_329**
+
+Re-order host page script load so Sentry can report script load failures
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `329`
+- Product: `Android`
+- Source files: `329.JSON`, `329.html`
+
+
+
+**Description**
+
+TC - change(android): re-order host page script load so Sentry can report script load failures #13333
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in the Android device or emulator.
+2. Accept all the Android permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Navigate to the "Search the keyboard" by pressing Keyman settings --> Install Keyboard or Dictionary --> Install from keyman.com.
+3. Installed multiple language keyboards. (Khmer_angkor, euro_latin. sil_ipa)
+4. Open the "Keyboard Picker" by pressing the "globe" key.
+5. Select another keyboard.
+6. Close the keyboard picker.
+7. Verify that the Keyman app does not close.
+8. Verify that the selected keyboard appears.
+9. Enter some sentences using the "EutoLatin" keyboard.
+10. Verify that the suggested words appear on the banner.
+11. Change the mobile view from portrait to landscape view.
+12. Verify that the Keyman keyboard appears in default size.
+13. Change the mobile view from landscape to portrait view.
+14. Launch the Chrome browser.
+15. Navigate to the Google search box(text area)
+16. Verify that the Keyman keyboard appeared.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon from the Android device / emulator.
+2. Verify the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman appears on the list.
+5. Click the Keyman option.
+6. Verify the Keyman menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_332**
+
+Check network access before trying to download keyboard
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `332`
+- Product: `Android`
+- Source files: `332.JSON`, `332.html`
+
+
+
+**Description**
+
+fix(android): Check network access before trying to download keyboard #13978
+
+
+Setup
+
+1. Install the latest Keymanan (.apk) build on the Android device or emulator.
+2. Accept all the Android permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Go to Settings> Installed Keyboard or Dictionary > Install from keyman.com,
+3. Verify that the keyboard search page appears.
+4. Search the 'Khmer Angkor' and install it
+5. Successfully download 'Khmer Angkor' keyboard and dictionaries
+6. Go to Settings> Installed Keyboard or Dictionary > Install from keyman.com, search for 'IPA (SIL)'
+7. Verify that the keyboard search page appears.
+8. Search for the 'IPA (SIL)' and install it.
+9. Successfully downloaded 'IPA (SIL)' keyboard and dictionaries
+10. Turn on airplane mode
+11. Click 'Install Keyboard'
+12. Verify a toast message as "No internet connection"
+
+
+
+
+Cleanup
+
+1. Click the Settings icon on the Android device/emulator.
+2. Verify that the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman appears on the list.
+5. Click the Keyman option.
+6. Verify that the Keyman menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message, “Do you want to uninstall this app?” appears with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman uninstallation completed successfully.
+
+
+
+---
+
+**TEST_334**
+
+Cancel flicks when both returning to and releasing at original tap location_TEST_FLICK_GENERAL_USE
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `334`
+- Product: `Android`
+- Source files: `334.JSON`, `334.html`
+
+
+
+**Description**
+
+TC - change(web): cancel flicks when both returning to and releasing at original tap location_TEST_FLICK_GENERAL_USE #13683
+
+
+Setup
+
+1. Install the latest Keymanan (.apk) build on the Android device or emulator.
+2. Accept all the Android permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Select the "Eurolatin" keyboard by clicking the globe key.
+3. Click on the "t" key and then pull down.
+4. Verify that the flick gesture is working fine and the output is correct.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon on the Android device/emulator.
+2. Verify that the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman appears on the list.
+5. Click the Keyman option.
+6. Verify that the Keyman menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message, “Do you want to uninstall this app?” appears with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman uninstallation completed successfully.
+
+
+
+---
+
+**TEST_337**
+
+Cancel flicks when both returning to and releasing at original tap location_TEST_FLICK_RESET_FULL
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `337`
+- Product: `Android`
+- Source files: `337.JSON`, `337.html`
+
+
+
+**Description**
+
+TC - change(web): cancel flicks when both returning to and releasing at original tap location_TEST_FLICK_RESET_FULL #13683
+
+
+Setup
+
+1. Install the latest Keymanan (.apk) build on the Android device or emulator.
+2. Accept all the Android permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Select the "Eurolatin" keyboard by clicking the globe key.
+3. Flick down the t key.
+4. Verify that the 5 appears.
+5. Flick back up to the center of the key and the 5 change back to t
+6. Flick down again, and the 5 appear in the preview again
+7. Release the key.
+8. Verify that the key has output 5.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon on the Android device/emulator.
+2. Verify that the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman appears on the list.
+5. Click the Keyman option.
+6. Verify that the Keyman menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message, “Do you want to uninstall this app?” appears with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman uninstallation completed successfully.
+
+
+
+---
+
+**TEST_344**
+
+Don't report missing kmp.json
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `344`
+- Product: `Android`
+- Source files: `344.JSON`, `344.html`
+
+
+
+**Description**
+
+TC - fix(android): Don't report missing kmp.json #13411
+
+
+Setup
+
+1. Install the latest Keymanan (.apk) build on the Android device or emulator.
+2. Accept all the Android permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+8. Download and save the file on your mobile device using the link below.
+https://darcywong00.github.io/examples/invalid/khmer10/khmer10_noJson.kmp
+
+
+
+
+Action
+
+1. Launch Keyman for Android.
+2. Install the downloaded *.kmp file by following these steps.
+3. From the Keyman settings --> Install Keyboard or Dictionary --> Install from local file --> browse to where khmer10_noJson.kmp was saved (in mobile).
+4. Verify that the toast notification appears and contains the message "No keyboards or predictive text to install."
+
+
+
+
+Cleanup
+
+1. Click the Settings icon on the Android device/emulator.
+2. Verify that the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman appears on the list.
+5. Click the Keyman option.
+6. Verify that the Keyman menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message, “Do you want to uninstall this app?” appears with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman uninstallation completed successfully.
+
+
+
+---
+
+**TEST_347**
+
+Add back button to "Adjust Keyboard Height "menu
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `347`
+- Product: `Android`
+- Source files: `347.JSON`, `347.html`
+
+
+
+**Description**
+
+TC - fix(android): Add back button to "Adjust Keyboard Height "menu #13645
+
+
+Setup
+
+1. Install the latest Keyman (.apk)build in the Android device or emulator.
+2. Accept all the Android permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch Keyman for Android.
+2. Dismiss the Get Started menu
+3. Open the "Adjust keyboard height" by clicking the Keyman's Settings --> Adjust keyboard height
+4. Verify that the "Adjust keyboard height" title bar has a back button on the left.
+5. Drag the keyboard to adjust the keyboard height and increase keyboard height.
+6. Verify that the keyboard height and observe it(note)
+7. Press the back button (<--) on the title bar to exit back to the app.
+8. Verify that the keyboard height now matches what was set in the "Adjust keyboard height" menu.
+9. Verify that the back button works to save the adjust of the keyboard height on the "Adjust keyboard height"
+
+
+
+
+Cleanup
+
+1. Click the Settings icon on the Android device/emulator.
+2. Verify that the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the first voice appears on the list.
+5. Click the first voice option.
+6. Verify that the first voice menu opens.
+7. Click the uninstall option.
+8. Verify that a first voice warning message “Do you want to uninstall this app?” with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the first voice Uninstallation completed successfully.
+
+
+
+---
+
diff --git a/docs/tests/acceptance/developer.md b/docs/tests/acceptance/developer.md
new file mode 100644
index 0000000000..b0a7c76213
--- /dev/null
+++ b/docs/tests/acceptance/developer.md
@@ -0,0 +1,855 @@
+# Developer Acceptance Tests
+
+**TEST_241**
+
+Test case for Debugger_Starts ,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `241`
+- Product: `Developer`
+- Source files: `241.JSON`, `241.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC152
+
+
+Setup
+
+1. Download Keyman Developer build from https://keyman.com/windows/ Site to the Desktop.
+2. Install Amharic Keyboard project .
+3. Install Keyman build.
+
+
+
+
+Action
+
+1. Open Keyman Developer application.
+2. Click the Keyboards tab.
+3. Verify ‘gff_amharic.kmn’ link button appears in the middle pane.
+4. Click the ‘gff_amharic.kmn’ link button.
+5. Verify the gff_amharic.kmn page opens.
+6. Press the F7 button.
+7. Verify the project is compiled successfully and the compiled message appears in the green color at the bottom of the page.
+8. Press the F5 button.
+9. Verify the ‘Debugger Mode’ view opens.
+10. Type with the keyboard in the debugger window.
+11. Verify any unexpected behavior or visual oddities.
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build.
+2. Uninstall Keyman Developer.
+3. Uninstall Amharic keyboard Project.
+4. Restart system.
+5. Install Updates.
+6. Clean up any broken installation artifacts (if they are available in the following folders)
+%ProgramFiles(x86)%\Keyman or %ProgramFiles%\Keyman
+%CommonProgramFiles(x86)%\Keyman or %CommonProgramFiles%\Keyman
+%ProgramData%\Keyman
+%AppData%\Keyman
+%LocalAppData%\Keyman
+HKCU\Software\Keyman
+HKLM\Software\Wow6432Node\Keyman
+7. Manually remove any remaining Keyman input methods from Windows Languages
+
+
+
+---
+
+**TEST_243**
+
+Test case for Debugger_Pause,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `243`
+- Product: `Developer`
+- Source files: `243.JSON`, `243.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC154
+
+
+Setup
+
+1. Download Keyman Developer build from https://keyman.com/windows/ Site to the Desktop.
+2. Install Amharic keyboard project.
+3. Install Keyman build.
+
+
+
+
+Action
+
+1. Open Keyman Developer application.
+2. Click the Keyboards tab.
+3. Verify ‘gff_amharic.kmn’ link button appears in the middle pane.
+4. Click the ‘gff_amharic.kmn’ link button.
+5. Verify the gff_amharic.kmn page opens.
+6. Press the F7 button.
+7. Verify the project is compiled successfully and the compiled message appears in the green color at the bottom of the page.
+8. Press the F5 button.
+9. Verify the ‘Debugger Mode’ view opens.
+10. Press the Pause button (||) in the Debugger toolbar.
+11. Verify that no input is possible in the debugger window.
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build.
+2. Uninstall Keyman Developer.
+3. Uninstall Amharic Keyboard project.
+4. Restart system.
+5. Install Updates.
+6. Clean up any broken installation artifacts (if they are available in the following folders)
+%ProgramFiles(x86)%\Keyman or %ProgramFiles%\Keyman
+%CommonProgramFiles(x86)%\Keyman or %CommonProgramFiles%\Keyman
+%ProgramData%\Keyman
+%AppData%\Keyman
+%LocalAppData%\Keyman
+HKCU\Software\Keyman
+HKLM\Software\Wow6432Node\Keyman
+8. Manually remove any remaining Keyman input methods from Windows Languages
+
+
+
+---
+
+**TEST_246**
+
+Test Case for Server_Starts,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `246`
+- Product: `Developer`
+- Source files: `246.JSON`, `246.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC157
+
+
+Setup
+
+1. Download Keyman Developer build from https://keyman.com/windows/ Site to the Desktop.
+2. Install Amharic keyboard project.
+3. Install Keyman build.
+
+
+
+
+Action
+
+1. Open Keyman Developer application.
+2. Click the Keyboards tab.
+3. Verify ‘gff_amharic.kmn’ link button appears in the middle pane.
+4. Click the ‘gff_amharic.kmn’ link button.
+5. Verify the gff_amharic.kmn page opens.
+6. Verify that the Server starts by examining the tool tray area.
+7. Click the ‘Build’ tab which appears in the left most column.
+8. Click the ‘Test Keyboard on web’ button under ‘Web and Mobile Targets’ pane.
+9. Verify that ‘http://localhost:8008’ link appears under the web address pane.
+10. Select http://localhost:8008 link.
+11. Click the ‘Open in browser’ button.
+12. Verify that the localhost page is open in the browser.
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build.
+2. Uninstall Keyman Developer.
+3. Uninstall Amharic keyboard project.
+4. Restart system.
+5. Install Updates.
+6. Clean up any broken installation artifacts (if they are available in the following folders)
+%ProgramFiles(x86)%\Keyman or %ProgramFiles%\Keyman
+%CommonProgramFiles(x86)%\Keyman or %CommonProgramFiles%\Keyman
+%ProgramData%\Keyman
+%AppData%\Keyman
+%LocalAppData%\Keyman
+HKCU\Software\Keyman
+HKLM\Software\Wow6432Node\Keyman
+7. Manually remove any remaining Keyman input methods from Windows Languages
+
+
+**TEST_248**
+
+Test Case for Server_Keep_Alive,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `248`
+- Product: `Developer`
+- Source files: `248.JSON`, `248.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC159
+
+
+Setup
+
+1. Download Keyman Developer build from https://keyman.com/windows/ Site to the Desktop.
+2. Install Amharic keyboard project.
+3. Install Keyman Stable build.
+
+
+
+
+Action
+
+1. Open Keyman Developer application.
+2. Click the Keyboards tab.
+3. Verify ‘gff_amharic.kmn’ link button appears in the middle pane.
+4. Click the ‘gff_amharic.kmn’ link button.
+5. Verify the gff_amharic.kmn page opens.
+6. Click the Tools menu.
+7. Click Options.
+8. Verify the Options dialog box opens.
+9. Click the Server tab.
+10. Check the ‘List Local URLs for Server’ option.
+11. Click the OK button.
+12. Click the Build tab.
+13. Click the ‘Test Keyboard on web’ button.
+14. Verify that the URL ‘ http://localhost:8008’ link appear under the web addresses pane.
+15. Click the ‘Open in browser’ in button.
+16. Verify that it opens in a local browser window.
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build.
+2. Uninstall Keyman Developer.
+3. Uninstall Amharic keyboard project.
+4. Restart system.
+5. Install Updates.
+6. Clean up any broken installation artifacts (if they are available in the following folders)
+%ProgramFiles(x86)%\Keyman or %ProgramFiles%\Keyman
+%CommonProgramFiles(x86)%\Keyman or %CommonProgramFiles%\Keyman
+%ProgramData%\Keyman
+%AppData%\Keyman
+%LocalAppData%\Keyman
+HKCU\Software\Keyman
+HKLM\Software\Wow6432Node\Keyman
+7. Manually remove any remaining Keyman input methods from Windows Languages
+
+
+
+---
+
+**TEST_251**
+
+fix(developer): handle KM_CORE_IT_INVALIDATE_CONTEXT in debugger #11488
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `251`
+- Product: `Developer`
+- Source files: `251.JSON`, `251.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC217
+
+
+Setup
+
+1. Download the Keyman Developer build from https://keyman.com/windows/site to the desktop.
+2. Install the Amharic keyboard project.
+3. Install the Keyman build.
+
+
+
+
+Action
+
+1. Open the Keyman Developer application.
+2. Click the Keyboards tab.
+3. Verify the "gff_amharic.kmn" link button appears in the middle pane.
+4. Click the ‘gff_amharic.kmn’ link button.
+5. Verify the gff_amharic.kmn page opens.
+6. Press the F7 button.
+7. Verify the project is compiled successfully and the compiled message appears in the green color at the bottom of the page.
+8. Press the F5 button.
+9. Verify the "Debugger Mode" view opens.
+10. Click the Platform tab.
+11. Select "Windows" from the Operating System drop-down list.
+12. Enter some text in an empty text box using the Amharic keyboard.
+13. Verify that the "Amharic" text appeared in the text box.
+14. Press the CTRL+A and then CTRL+C keys.
+15. Verify that the text is selected in the text box.
+16. Press CTRL+V.
+17. Press CTRL+Z.
+18. Verify that the text disappeared in the text box.
+19. Verify that no error message box appeared or no crash dialog appeared
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build.
+2. Uninstall Keyman Developer.
+3. Uninstall Amharic Keyboard Project.
+4. Restart system.
+5. Install Updates.
+6. Clean up any broken installation artifacts (if they are available in the following folders)
+%ProgramFiles(x86)%\Keyman or %ProgramFiles%\Keyman
+%CommonProgramFiles(x86)%\Keyman or %CommonProgramFiles%\Keyman
+%ProgramData%\Keyman
+%AppData%\Keyman
+%LocalAppData%\Keyman
+HKCU\Software\Keyman
+HKLM\Software\Wow6432Node\Keyman
+7. Manually remove any remaining Keyman input methods from Windows Languages
+
+
+
+---
+
+**TEST_253**
+
+feat(developer): kmc-copy #12555 (TEST_COPY_MODELS)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `253`
+- Product: `Developer`
+- Source files: `253.JSON`, `253.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC298
+
+
+Setup
+
+1. Install Keyman Developer latest stable build from Keyman.com site.(or state.keyman.com)
+2. Created a new folder under the Download folder.
+3. Created a new folder under the Temp folder.
+
+
+
+
+Action
+
+1. Navigate to the folder path that has GitHub's Lexical-models keyboard.
+(Get the latest changes from GitHub's in the local machine)
+2. Open the command prompt.
+3. Enter the below command in the window's prompt
+kmc copy "keyboard source file path\folder_name" -o "Keyboard destination folder path"
+E.g. kmc copy C:\Documents\GitHub\lexical-models\release\sil\sil.cmo.bw -o C:\Downloads\TestingKeyboard\LexicalModelKMCTesting1
+kmc copy "keyboard source file path\*.kpj" -o "Keyboard destination folder path"
+E.g kmc copy C:\Documents\GitHub\lexical-models\release\sil\sil.cmo.bw\sil.cmo.bw.kpj -o C:\Downloads\TestingKeyboard\LexicalModelKMCTesting
+4. Verify that the keyboard folder or *.kpj file was copied into a new folder.
+5. Verify that the keyboard file was renamed in the new folder.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the search bar (in the task bar)
+2. Verify that the ‘Control Panel’ appears in the menu list.
+3. Click the Control Panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman Developer version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully.
+
+
+
+---
+
+**TEST_256**
+
+fix(developer): handle paste of TSV into Wordlist grid #12594(TEST_PASTE_SIMPLE_STRING)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `256`
+- Product: `Developer`
+- Source files: `256.JSON`, `256.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC301
+
+
+Setup
+
+1. Install Keyman Developer latest stable build from Keyman.com site.(or state.keyman.com)
+2. Create a new "Wordlist Lexical Model" project.
+3. Enter an appropriate text in the "New Wordlist Lexical Model" project dialog.
+4. Project appeared in the new dialog.
+5. Navigate to the "Models" tab.
+6. Click the *.model.ts link.
+7. Navigate to the "wordlist.tsv" tab.
+
+
+
+
+Action
+
+1. Copy a word from a notepad file or clipboard.
+2. Click in the "Add word..." box.
+3. Paste the text by pressing the CTRL+V key.
+4. Verify the word appears in the "Add word..." box.
+5. Verify that no error appears after pasting a text in the "Add word..." box.
+6. Verify the new "Add word..." row added
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the search bar (in the taskbar).
+2. Verify that the ‘Control Panel’ appears in the menu list.
+3. Click the Control Panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman Developer version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully.
+
+
+
+---
+
+**TEST_258**
+
+feat(developer): kmc generate #11014(TEST_KEYMAN_KEYBOARD)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `258`
+- Product: `Developer`
+- Source files: `258.JSON`, `258.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC303
+
+
+Setup
+
+1. Install Keyman Developer latest stable build from Keyman.com site.(or state.keyman.com)
+2. Created a new folder under the download folder.
+3. Open the command prompt in this folder.
+4. Executed below commands to generate keyman keyboards.
+E.g. kmc generate keyman-keyboard "Folder_Name"
+kmc generate keyman-keyboard kmnkeyboard
+5. Verify that the keyboard folder was created with the specified name
+
+
+
+
+Action
+
+1. Go to the folder that had keyboards.
+2. Open the command prompt in this folder.
+3. Execute the "kmc build keyboard_folder_name" command.
+4. Verify that the build folder was created inside the keyboard's folder.
+5. Verify that the *.kmp file was created inside the build folder.
+6. Install the *.kmp file in Windows 10 or 11
+7. Verify that the keyboard was added under "English"
+8. Go to the source folder.
+9. Verify that the generated files.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the search bar (in the task bar)
+2. Verify that the ‘Control Panel’ appears in the menu list.
+3. Click the Control Panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman Developer version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully.
+
+
+
+---
+
+**TEST_260**
+
+feat(developer): kmc generate #11014(TEST_LEXICAL_MODEL)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `260`
+- Product: `Developer`
+- Source files: `260.JSON`, `260.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC305
+
+
+Setup
+
+1. Install Keyman Developer latest stable build from Keyman.com site.(or state.keyman.com)
+2. Created a new folder under the download folder.
+3. Open the command prompt in this folder.
+4. Executed below commands to generate keyman keyboards.
+E.g. kmc generate keyman-keyboard "Folder_Name"
+kmc generate lexical-model en.lexicalmodeluniq
+5. Verify that the keyboard folder was created with the specified name
+
+
+
+
+Action
+
+1. Go to the folder that had keyboards.
+2. Open the command prompt in this folder.
+3. Execute the "kmc build keyboard_folder_name" command.
+4. Verify that the build folder was created inside the keyboard's folder.
+5. Verify that the *.kmp file was created inside the build folder.
+6. Install the *.kmp file on an Android 12 mobile device.
+7. Verify that the keyboard was added under "English."
+8. Go to the source folder.
+9. Verify that the generated files.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the search bar (in the task bar)
+2. Verify that the ‘Control Panel’ appears in the menu list.
+3. Click the Control Panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman Developer version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully.
+
+
+
+---
+
+**TEST_314**
+
+TC - feat(developer): improve compiler messages and user interface_TEST_MESSAGE_RIGHT-CLICK
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `314`
+- Product: `Developer`
+- Source files: `314.JSON`, `314.html`
+
+
+
+**Description**
+
+TC - feat(developer): improve compiler messages and user interface_TEST_MESSAGE_RIGHT-CLICK #13156
+
+
+Setup
+
+1. Download Keyman Developer build from https://keyman.com/windows/ Site to the Desktop.
+2. Install "gautami_devanagari" keyboard project.
+3. Install Keyman build.
+
+
+
+
+Action
+
+1. Open the "gautami_devanagari" keyboard project loaded in the keyman developer.
+2. Verify that the project is loaded in the keyman developer window.
+3. Compile the keyboard by clicking the keyboard menu --> compile keyboard.
+4. Verify that the compile success message appears
+5. Right-click on the compiled message.
+6. Select the "Open documentation on selected message" option from the menu.
+7. Verify that the navigation redirects to the browser.
+8. Verify that the link appears on the browser.
+9. Verify the message details appears on the "help.keyman.com" website.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the search bar (in the taskbar).
+2. Verify that the ‘Control Panel’ appears in the menu list.
+3. Click the Control Panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman Developer version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully.
+
+
+
+---
+
+**TEST_317**
+
+TC - fix(developer): support &displayMap font in web debugger_TEST_DISPLAYMAP_FONT
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `317`
+- Product: `Developer`
+- Source files: `317.JSON`, `317.html`
+
+
+
+**Description**
+
+TC - fix(developer): support &displayMap font in web debugger_TEST_DISPLAYMAP_FONT #12929
+
+
+Setup
+
+1. Download Keyman Developer build from https://keyman.com/windows/ Site to the Desktop.
+2. Install KeymanDeveloper build.
+3. Install Keyman build.
+
+
+
+
+Action
+
+1. Open the "Khmer Angkor" keyboard project loaded in the keyman developer.
+2. Click the "*.knm" link and then a new tab opens.
+3. Verify that the new tab appears with *.kmn
+4. Click on the "Layout" tab.
+5. Open the Font by clicking the Keyboard --> Fonts.
+6. Verify that the "DisplayMap target font" has the "kbdKhmr" font.
+7. Close the font dialog by clicking the "Ok" button.
+8. Click on the "Build" tab. Click the "Compile Keyboard" button.
+9. Click on the "Test Keyboard on Web" button.
+10. Select the "http://localhost:8008" in the server-listed pane.
+11. Click on the "Open in browser" button.
+12. Verify that the web keyboard appears on the browser.
+13. Select the "Khmer_Angkor" keyboard and then select Windows by clicking the device button.
+14. Press on the SHIFT+A
+15. Verify that the "A" key shows the single dot khmer letter.
+16. Change the device from Windows to Mobile by clicking the "Device" button.
+17. Long press the "A" key.
+18. Verify that the "A" subkey is showing the single dot khmer letter.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the search bar (in the taskbar).
+2. Verify that the ‘Control Panel’ appears in the menu list.
+3. Click the Control Panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman Developer version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully.
+
+
+
+---
+
+**TEST_339**
+
+Evaluate and apply npm audit fix (without forced changes)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `339`
+- Product: `Developer`
+- Source files: `339.JSON`, `339.html`
+
+
+
+**Description**
+
+TC - maint(common): evaluate and apply npm audit fix (without forced changes) #13897
+
+
+Setup
+
+1. Download Keyman Developer build from https://keyman.com/windows/ Site to the Desktop.
+2. Install KeymanDeveloper build.
+3. Install the Keyman build.
+
+
+
+
+Action
+
+1. Open the "Khmer Angkor"(or Tamil) keyboard project loaded in the Keyman Developer.
+2. On the keyboards tab: Click the "Build keyboards" button to build the keyboard.
+3. Click the "*.knm" link, and a new tab opens.
+4. Verified that the new tab appeared with *.kmn
+5. Click on the "Build" tab. Click the "Compile Keyboard" button.
+6. Click on the "Start Debugging" button.
+7. Enter some text in the debug window.
+8. Return to the "Build" tab.
+9. Click on the "Test Keyboard on Web" button.
+10. Select "http://localhost:8008" in the server-listed pane.
+11. Click on the "Open in browser" button.
+12. Verified that the web keyboard appeared on the browser.
+13. Select the "Khmer_Angkor"(or Tamil) keyboard and then select Windows by clicking the device button.
+14. Press some keys on the OSK.
+15. Verified that the key shows the khmer letter.
+16. Change the device from Windows to Mobile by clicking the "Device" button.
+17. Press some keys on the OSK.
+18. Verified that the key is showing the khmer letter.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the search bar (in the taskbar).
+2. Verify that the ‘Control Panel’ appears in the menu list.
+3. Click the Control Panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman Developer version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully.
+
+
+
+---
+
+**TEST_362**
+
+Remove redundant Name and RTL fields from .kps LexicalModel_TEST_NEW_PROJECT
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `362`
+- Product: `Developer`
+- Source files: `362.JSON`, `362.html`
+
+
+
+**Description**
+
+TC - fix(developer): remove redundant Name and RTL fields from .kps LexicalModel_TEST_NEW_PROJECT #13640
+
+
+Setup
+
+1. Download Keyman Developer build from https://keyman.com/windows/ Site to the Desktop.
+2. Install KeymanDeveloper build.
+3. Install the Keyman build.
+
+
+
+
+Action
+
+1. Launch the KeymanDeveloper.
+2. Open an LDML keyboard project from the GitHub\lexical-models\release folder path.
+3. Create a new LDML keyboard project by clicking the project menu --> new project.
+4. Build the entire project on the packaging.
+5. Verify that the project build folder has files(inside the build folder)
+6. Compile the changes by clicking the keyboard menu --> Compile keyboard.
+7. Open the .kps file in Notepad from the source folder.
+8. Verify that the name does not appear in the *.kps file
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the search bar (in the taskbar).
+2. Verify that the ‘Control Panel’ appears in the menu list.
+3. Click the Control Panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman Developer version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully.
+
+
+
+---
+
diff --git a/docs/tests/acceptance/gestures.md b/docs/tests/acceptance/gestures.md
new file mode 100644
index 0000000000..8882113e12
--- /dev/null
+++ b/docs/tests/acceptance/gestures.md
@@ -0,0 +1,826 @@
+# Gestures Acceptance Tests
+
+**TEST_287**
+
+Test case for 10_KEY_ROTA,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `287`
+- Product: `Gestures`
+- Source files: `287.JSON`, `287.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC188
+
+
+Setup
+
+1. Android Mobile is ready to test.
+2. Install Keyman latest Stable build from Keyman.com site.
+3. Install Chrome browser.
+4. KeymanWeb Test Home link is available for testing.
+
+
+
+
+Action
+
+1. Click the “Test unminified Keymanweb” link button.
+2. Verify that ‘KeymanWeb Sample Page - Unminified Source’ page opens.
+3. Click the text input screen.
+4. Click the globe key.
+5. Select English - Classic 10-key using from Keyboard picker menu.
+6. Verify that all of the key numbers 1-9 aside from 7 have three or more lower case letters as key hints.
+7. Tap the 8 key, then wait for a second.
+8. Tap the 8 key twice in quick succession, then wait for a second.
+9. Verify the output ‘8a’ in the text input screen.
+10. Tap the 8 key continuously for at least 2 seconds.
+11. Verify that it can rotate through : 8a8, 8aa, 8ab, 8ac, 8aA, 8aB, 8aC, then back to 8a8
+12. Stop tapping when the new character is a capital letter.
+13. Verify that the key hints are now capitalized
+14. Double-tap the 9 key once.
+15. Verify that “D” is emitted as the result.
+16. Repeatedly tap 9 for at least five seconds.
+17. Verify that if a lowercase letter is the result, the key hints is lowercase.
+18. Verify that if an uppercase letter is the result, the key hints is uppercase.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_288**
+
+Test case for 10_KEY_DIACRITICS,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `288`
+- Product: `Gestures`
+- Source files: `288.JSON`, `288.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC189
+
+
+Setup
+
+1. Android Mobile is ready to test.
+2. Install Keyman latest Stable build from Keyman.com site.
+3. Install Chrome browser.
+4. KeymanWeb Test Home link is available for testing.
+
+
+
+
+Action
+
+1. Click the “Test unminified Keymanweb” link button.
+2. Verify that ‘KeymanWeb Sample Page - Unminified Source’ page opens.
+3. Click the text input screen.
+4. Click the globe key.
+5. Select English - Diacritic 10-key Rota using from Keyboard picker menu.
+6. Verify that English - Diacritic 10-key Rota OSK appeared on the screen.
+7. Tap the ◌̀ key. (The key between backspace [above] and enter [below] representing a diacritic.
+8. Double-tap the 8 key.
+9. Verify à letter appear on the screen.
+10. Triple-tap the ◌̀ key.
+11. Verify that a circumflex diacritic appeared over the à.
+12. Triple-tap the 9 key.
+13. Verify that the total result àê appeared on the screen.
+14. Deselect the text-area element.
+15. 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.)
+16. Double-tap the 8 key.
+17. Verify that àềa appeared on the screen.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_289**
+
+Test case for APP_10_KEY_DIACRITICS,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `289`
+- Product: `Gestures`
+- Source files: `289.JSON`, `289.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC190
+
+
+Setup
+
+1. Android Mobile is ready to test.
+2. Install Keyman latest Stable build from Keyman.com site.
+3. Download this KMP : https://jahorton.github.io/diacritic_rota.kmp
+4. Install it for use within the Keyman app.
+5. KeymanWeb Test Home link is available for testing.
+
+
+
+
+Action
+
+1. Tap the 7 key twice.
+2. Verify that 77 is output on the screen.
+3. Tap the ◌̀ key.
+4. Double-tap the 8 key.
+5. Verify that the total result 77à appeared on the screen.
+6. Triple-tap the ◌̀ key.
+7. Verify that a circumflex diacritic appeared over the à
+8. Triple-tap the 9 key.
+9. Verify that the total result 77àê appeared on the screen.
+10. Tap the ◌̀ key.
+11. Verify that a diacritic appeared over the ê.
+12. Open the Keyman In-App Settings menu.
+13. Close the in-app Settings menu.
+14. Double-tap the 8 key.
+15. Verify the output 77àềa appeared on the screen.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_290**
+
+Test case for BASIC_SIMPLE_SHIFT,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `290`
+- Product: `Gestures`
+- Source files: `290.JSON`, `290.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC191
+
+
+Setup
+
+1. Android Mobile is ready to test.
+2. Install Keyman latest Stable build from Keyman.com site.
+3. Install Chrome browser.
+4. KeymanWeb Test Home link is available for testing.
+
+
+
+
+Action
+
+1. Click “Test unminified Keymanweb” link button.
+2. Verify that ‘KeymanWeb Sample Page - Unminified Source’ page opens.
+3. Click the text input screen.
+4. Click the globe key.
+5. Select Norwegian - EuroLatin(SIL) using the Keyboard picker menu.
+6. Verify that the Norwegian - EuroLatin(SIL) OSK appeared on the screen.
+7. Tap the Spacebar.
+8. Verify that the keyboard is on the default (lowercase) layer after this.
+9. Tap the Shift key.
+10. Verify that the keyboard stays on the Shift layer.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_291**
+
+Test case of BASIC_MODIPRESS,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `291`
+- Product: `Gestures`
+- Source files: `291.JSON`, `291.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC192
+
+
+Setup
+
+1. Android Mobile is ready to test.
+2. Install Keyman latest Stable build from Keyman.com site.
+3. Install Chrome browser.
+4. KeymanWeb Test Home link is available for testing.
+
+
+
+
+Action
+
+1. Click the “Test unminified Keymanweb” link button.
+2. Verify that ‘KeymanWeb Sample Page - Unminified Source’ page opens.
+3. Click the text input screen.
+4. Click the globe key.
+5. Select Norwegian - EuroLatin(SIL) using the Keyboard picker menu.
+6. Verify that the Norwegian - EuroLatin(SIL) OSK appeared on the screen.
+7. Tap the Spacebar.
+8. Tap and hold the Shift key.
+9. Verify that the keyboard changed to the Shift layer.
+10. Tap the A key.
+11. Verify that it produces letter A on the Screen.
+12. Release the Shift key.
+13. Verify that the Keyboard changed to the default layer.
+14. Repeat Steps from 8 to 13 quickly.
+15. Holding Shift just long enough to tap the Shift layers A key
+16. Release it quickly.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+**TEST_292**
+
+Test case for BASIC_MODIPRESS_HOLD,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `292`
+- Product: `Gestures`
+- Source files: `292.JSON`, `292.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC193
+
+
+Setup
+
+1. Android Mobile is ready to test.
+2. Install Keyman latest Stable build from Keyman.com site.
+3. Install Chrome browser.
+4. KeymanWeb Test Home link is available for testing.
+
+
+
+
+Action
+
+1. Click the “Test unminified Keymanweb” link button.
+2. Verify that ‘KeymanWeb Sample Page - Unminified Source’ page opens.
+3. Click the text input screen.
+4. Click the globe key.
+5. Select Norwegian - EuroLatin(SIL) using the Keyboard picker menu.
+6. Verify that the Norwegian - EuroLatin(SIL) OSK appeared on the screen.
+7. Tap the Spacebar.
+8. Tap and hold the Shift key.
+9. Verify that the keyboard changed to the Shift layer.
+10. Wait at least one second.
+11. Release the Shift key.
+12. Verify that the keyboard changed to the default layer as a result of Step 11.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_293**
+
+Test case for NUMERIC_FROM_SHIFT,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `293`
+- Product: `Gestures`
+- Source files: `293.JSON`, `293.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC194
+
+
+Setup
+
+1. Android Mobile is ready to test.
+2. Install Keyman latest Stable build from Keyman.com site.
+3. Install Chrome browser.
+4. KeymanWeb Test Home link is available for testing.
+
+
+
+
+Action
+
+1. Click the “Test unminified Keymanweb” link button.
+2. Verify that ‘KeymanWeb Sample Page - Unminified Source’ page opens.
+3. Click the text input screen.
+4. Click the globe key.
+5. Select Norwegian - EuroLatin(SIL) using the Keyboard picker menu.
+6. Verify that the Norwegian - EuroLatin(SIL) OSK appeared on the screen.
+7. Tap the Spacebar.
+8. Verify that the keyboard is on the default (lowercase) layers after this.
+9. Tap the Shift key.
+10. Verify Keyboard is in the Shift layer.
+11. Tap and hold the numeric key (123) underneath the Shift key.
+12. Verify that the keyboard changed to the numeric layer - numbers in the top row, mathematical symbols elsewhere.
+13. Long press the % key.
+14. Select ‱ subkey.
+15. Verified that ‱ is emitted as text.
+16. Release the numeric key.
+17. Verify that the keyboard changed back to the Shift layer.
+18. Tap the numeric key, releasing it immediately.
+19. Repeat from 13 to 15, long pressing the % key.
+20. Select the ‱ subkey.
+21. Verify that the keyboard automatically changed back to the default (lowercase)layer.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_294**
+
+Test case for DELAYED_SUBKEY,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `294`
+- Product: `Gestures`
+- Source files: `294.JSON`, `294.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC195
+
+
+Setup
+
+1. Android Mobile is ready to test.
+2. Install Keyman latest Stable build from Keyman.com site.
+3. Install Chrome browser.
+4. KeymanWeb Test Home link is available for testing.
+
+
+
+
+Action
+
+1. Click the “Test unminified Keymanweb” link button.
+2. Verify that ‘KeymanWeb Sample Page - Unminified Source’ page opens.
+3. Click the text input screen.
+4. Click the globe key.
+5. Select Norwegian - EuroLatin(SIL) using the Keyboard picker menu.
+6. Verify that the Norwegian - EuroLatin(SIL) OSK appeared on the screen.
+7. Tap the Spacebar.
+8. Tap the Shift key.
+9. Verify that the Shift layer is active.
+10. Tap and hold the numeric (123) key underneath the Shift key.
+11. Verify that the keyboard changed to the numeric layer - numbers in the top row, mathematical symbols elsewhere.
+12. Long press the % key.
+13. Release the numeric key.
+14. Verify that the keyboard changed remained on the numeric layer, with the subkey menu still displayed.
+15. Select the ‱ subkey.
+16. Verify that ‱ is emitted as text and that the layer has changed back to the Shift layer.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_295**
+
+Test case for DOUBLETAP_CAPS,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `295`
+- Product: `Gestures`
+- Source files: `295.JSON`, `295.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC196
+
+
+Setup
+
+1. Android Mobile is ready to test.
+2. Install Keyman latest Stable build from Keyman.com site.
+3. Install Chrome browser.
+4. KeymanWeb Test Home link is available for testing.
+
+
+
+
+Action
+
+1. Click the “Test unminified Keymanweb” link button.
+2. Verify that ‘KeymanWeb Sample Page - Unminified Source’ page opens.
+3. Click the text input screen.
+4. Click the globe key.
+5. Select Norwegian - EuroLatin(SIL) using the Keyboard picker menu.
+6. Verify that the Norwegian - EuroLatin(SIL) OSK appeared on the screen.
+7. Type “All”.
+8. Double-tap the Shift key.
+9. Type “CAPS”.
+10. Tap the Shift key.
+11. Type “Well” without touching the Shift key at any point.
+12. Verify the final result, in total : All CAPS word Well
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_297**
+
+Test case for ALTERNATING_SHIFT_AND_KEY,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `297`
+- Product: `Gestures`
+- Source files: `297.JSON`, `297.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC198
+
+
+Setup
+
+1. Android Mobile is ready to test.
+2. Install Keyman latest Stable build from Keyman.com site.
+3. Install Chrome browser.
+4. KeymanWeb Test Home link is available for testing.
+
+
+
+
+Action
+
+1. Click the “Test unminified Keymanweb” link button.
+2. Verify that ‘KeymanWeb Sample Page - Unminified Source’ page opens.
+3. Click the text input screen.
+4. Click the globe key.
+5. Select “English - Gesture Prototyping” using the Keyboard picker menu.
+6. Verify that the English - Gesture Prototyping OSK appeared on the screen.
+7. Tap and hold the SHIFT key.
+8. Tap the H key and release it.
+9. Release the SHIFT key.
+10. Verify that an H is output on the text screen.
+11. Verify that the layer returns to default after step 7.
+12. Repeat steps 7-10 five times.
+13. Repeat steps 7-9 quickly for at least 10 seconds.
+14. Tap the numeric (123) key.
+15. Verify that the layer switches properly to keys with numbers in the top row and symbols in the middle two rows.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_300**
+
+Test case for FLICK_LOCKING,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `300`
+- Product: `Gestures`
+- Source files: `300.JSON`, `300.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC201
+
+
+Setup
+
+1. Android Mobile is ready to test.
+2. Install Keyman latest Stable build from Keyman.com site.
+3. Install Chrome browser.
+4. KeymanWeb Test Home link is available for testing.
+
+
+
+
+Action
+
+1. Click the “Test unminified Keymanweb” link button.
+2. Verify that ‘KeymanWeb Sample Page - Unminified Source’ page opens.
+3. Click the text input screen.
+4. Click the globe key.
+5. Select “English - Gesture Prototyping” using the Keyboard picker menu.
+6. Verify that the English - Gesture Prototyping OSK appeared on the screen.
+7. Tap and hold the ‘u’ key.
+8. Drag it to a straight up position.
+9. Verify that the û key is in the preview area.
+10. Verify that the animation is not “jumpy”.
+11. Return your finger to its original position.
+12. Verify that the ‘u’ key should like back into place.
+13. Drag your finger in an up-and-right motion.
+14. Verify that you should also see a preview for ú as you do so.
+15. Verify that the animation is not “jumpy”.
+16. Lift your finger and end the gesture, while the ú is visible and in the center.
+17. Verify that a ú is output.
+18. Tap and hold the a key.
+19. Drag it to a straight up position.
+20. Verify that the â key is in the preview area.
+21. Verify that the animation is not “jumpy”.
+22. Return your finger to its original position.
+23. Verify that the ‘a’ key should like back into place.
+24. Drag your finger in an up-and-right motion.
+25. Verify that a preview for ú appeared.
+26. Verify that the animation is not “jumpy”.
+27. Lift your finger and end the gesture, while the ú is visible and in the center.
+28. Verify that a á is output.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_302**
+
+Test case for FLICK_DURING_MODIPRESS,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `302`
+- Product: `Gestures`
+- Source files: `302.JSON`, `302.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC203
+
+
+Setup
+
+1. Android Mobile is ready to test.
+2. Install Keyman latest Stable build from Keyman.com site.
+3. Install Chrome browser.
+4. KeymanWeb Test Home link is available for testing.
+
+
+
+
+Action
+
+1. Click the “Test unminified Keymanweb” link button.
+2. Verify that ‘KeymanWeb Sample Page - Unminified Source’ page opens.
+3. Click the text input screen.
+4. Click the globe key.
+5. Select “English - Gesture Prototyping” using the Keyboard picker menu.
+6. Verify that the English - Gesture Prototyping OSK appeared on the screen.
+7. Tap and hold the SHIFT key.
+8. Tap and hold the U key.
+9. Drag it purely to a straight up position.
+10. Verify that the Û key in the preview area.
+11. Verify that the animation is not “jumpy”.
+12. Release the SHIFT key.
+13. Verify that the Shift layer (all uppercase) remains visible.
+14. Verify that the flick animation is still active.
+15. Return the finger to its original position.
+16. Verify that the ‘U’ key slid back into place.
+17. Drag the finger in an up-and-right motion.
+18. Verify that a preview for Ú . appeared
+19. Verify that the animation is not “jumpy”.
+20. Tap on the Q key, while Ú the is visible and in the center.
+21. Verify that the keyboard returns to the default (lowercase) layer.
+22. Verify that it shows either Ú or Úq as the output.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
diff --git a/docs/tests/acceptance/ios.md b/docs/tests/acceptance/ios.md
new file mode 100644
index 0000000000..5f1b69859c
--- /dev/null
+++ b/docs/tests/acceptance/ios.md
@@ -0,0 +1,998 @@
+# iOS Acceptance Tests
+
+**TEST_150**
+
+Test Case for “Get_Started” menu
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `150`
+- Product: `IOS`
+- Source files: `150.JSON`, `150.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC92
+
+
+Setup
+
+1. Install latest Keyman(.ios) build in iPhone / iPad device or Simulator.
+2. Ensure the device or emulator is enabled with internet connection.
+
+
+
+
+Action
+
+1. Click the Keyman icon from the screen.
+2. Verify that the Keyman application opens.
+3. Verify the “Get Started” menu appears along with the application.
+4. Click the “Add a keyboard for your languages” option from the Get Started menu.
+5. Verify that the ‘Install Keyboard or Dictionary’ menu opens.
+6. Click the ‘Setup Keyman as system wide keyboard > Enable keyman’’ option from the Get Started menu.
+7. Verify that it pulls up the keyman settings menu within iOS settings.
+8. Click the ‘More Info’ option from the Get Started menu.
+9. Verify that the “Keyman for iPhone and iPad 17.0 Help’ topic opens.
+10. Enable “Don’t show again” toggle switch.
+11. Click the “Done” option which appears at the top right corner of the menu.
+12. Close the Keyman application.
+13. Verify that the Keyman application is closed.
+14. Click the Keyman icon.
+15. Verify that the “Get Started” menu does not appear after the Keyman application opens.
+
+
+
+
+Cleanup
+
+1. Long press the Keyman icon from the display.
+2. Verify that the “Remove App” option appears on the screen.
+3. Click the “Remove App” option.
+4. Verify that a warning message appears “Remove Keyman? on the screen with ‘Delete App’ option.
+5. Click the ‘Delete App’ option.
+6. Verify that another warning message “Delete Keyman? - Delete this app will also delete its data” appears on the Screen with ‘Delete’ and ‘Cancel’ button.
+7. Click the Delete button.
+8. Verify that the Keyman Uninstallation completed successfully.
+
+
+**TEST_153**
+
+Test case for adding a new keyboard via Get Started menu,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `153`
+- Product: `IOS`
+- Source files: `153.JSON`, `153.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC95
+
+
+Setup
+
+1. Install latest Keyman(.ios) build in iPhone / iPad device or Simulator.
+2. Ensure the device or emulator is enabled with internet connection.
+
+
+
+
+Action
+
+1. Click on the Keyman icon from the display.
+2. Verify that the Keyman application opens.
+3. Verify that the 'Get Started’ menu opens.
+4. Click the ‘Add keyboard for your language’ option from the Get Started menu dialog.
+5. Verify that the Keyboard Search menu opens.
+6. Enter ‘US Basic’ in the Search field.
+7. Verify that the US Basic keyboard link opens.
+8. Click the US Basic link button.
+9. Verify that the US basic Keyboard menu opens.
+10. Click the Install Keyboard button.
+11. Verify that the US Basic Keyboard installed Successfully.
+12. Verify that the US Basic Keyboard appears as the active keyboard in the text input screen.
+
+
+
+
+Cleanup
+
+1. Long press the Keyman icon from the display.
+2. Verify that the “Remove App” option appears on the screen.
+3. Click the “Remove App” option.
+4. Verify that a warning message appears “Remove Keyman? on the screen with ‘Delete App’ option.
+5. Click the ‘Delete App’ option.
+6. Verify that another warning message “Delete Keyman? - Delete this app will also delete its data” appears on the Screen with ‘Delete’ and ‘Cancel’ button.
+7. Click the Delete button.
+8. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_155**
+
+Test case for Switch_Keyboard,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `155`
+- Product: `IOS`
+- Source files: `155.JSON`, `155.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC97
+
+
+Setup
+
+1. Install latest Keyman(.ios) build in iPhone / iPad device or Simulator.
+2. Ensure the device or emulator is enabled with internet connection.
+3. Install US Basic Keyboard from Keyman.com Site.
+
+
+
+
+Action
+
+1. Click on the Keyman icon from the display.
+2. Verify that the Keyman application opens.
+3. Verify that “EuroLatin (SIL)” keyboard as the default keyboard.
+4. Click the globe key.
+5. Verify that the Keyboard picker menu.
+6. Click on “English (US Basic)” keyboard.
+7. Verify that the Keyboard should be changed to US Basic keyboard in the input text screen.
+8. Click the globe key.
+9. Verify the keyboard picker menu.
+10. Click the “EuroLatin (SIL)” keyboard.
+11. Verify that the keyboard switches back to “EuroLatin (SIL)” keyboard as the active keyboard in the input text screen.
+
+
+
+
+Cleanup
+
+1. Long press the Keyman icon from the display.
+2. Verify that the “Remove App” option appears on the screen.
+3. Click the “Remove App” option.
+4. Verify that a warning message appears “Remove Keyman? on the screen with ‘Delete App’ option.
+5. Click the ‘Delete App’ option.
+6. Verify that another warning message “Delete Keyman? - Delete this app will also delete its data” appears on the Screen with ‘Delete’ and ‘Cancel’ button.
+7. Click the Delete button.
+8. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_158**
+
+Test case for appearing Text Size in the Input text Screen,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `158`
+- Product: `IOS`
+- Source files: `158.JSON`, `158.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC100
+
+
+Setup
+
+1. Install latest Keyman(.ios) build in iPhone / iPad device or Simulator.
+2. Ensure the device or emulator is enabled with internet connection.
+
+
+
+
+Action
+
+1. Click on the Keyman icon from the display.
+2. Verify that the Keyman application opens.
+3. Type “Keyman” on the Input text Screen.
+4. Click the “Text Size” option from the Keyman menu list.
+5. Verify that the Text Size option menu appears at the bottom of the Screen.
+6. Set it to the Maximum Size “72”
+7. Verify that the word “Keyman” appeared to be in big size in the Input text screen.
+8. Set the Text Size to the minimum “16”
+9. Verify that the word “Keyman” appeared to be in Small size in the Input text screen.
+
+
+
+
+Cleanup
+
+1. Long press the Keyman icon from the display.
+2. Verify that the “Remove App” option appears on the screen.
+3. Click the “Remove App” option.
+4. Verify that a warning message appears “Remove Keyman? on the screen with the ‘Delete App’ option.
+5. Click the ‘Delete App’ option.
+6. Verify that another warning message “Delete Keyman? - Delete this app will also delete its data” appears on the Screen with ‘Delete’ and ‘Cancel’ button.
+7. Click the Delete button.
+8. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_160**
+
+Test case for Info Help topic,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `160`
+- Product: `IOS`
+- Source files: `160.JSON`, `160.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC102
+
+
+Setup
+
+• Install latest Keyman(.ios) build in iPhone / iPad device or Simulator.
+• Ensure the device or emulator is enabled with internet connection.
+
+
+
+
+Action
+
+1. Click on the Keyman icon from the display.
+2. Verify that the Keyman application opens.
+3. Verify that the Get Started menu dialog opens along with the Keyman app.
+4. Click More Info option from the Get Started menu dialog.
+5. Verify that the “Keyman for iPhone and iPad 17.0 Help’ topic opens.
+6. Click the Done button.
+7. Verify that the “Keyman for..” help topic closes.
+8. Click the Close (X) button which appears at the bottom of the help topic.
+9. Verify that the “Keyman for..” help topic closes.
+10. Click the Keyman list menu (three dots which appear at the top right corner of the screen).
+11. Verify that the Info option appears in the Keyman list menu.
+12. Click the Info option.
+13. Verify that the “Keyman for iPhone and iPad 17.0 Help’ topic opens.
+14. Click the Done button.
+15. Verify that the “Keyman for ..” helpt topic closes.
+16. Click the Close (X) button which appears at the bottom of the help topic.
+17. Verify that the “Keyman for.. “ help topic closes.
+
+
+
+
+Cleanup
+
+1. Long press the Keyman icon from the display.
+2. Verify that the “Remove App” option appears on the screen.
+3. Click the “Remove App” option.
+4. Verify that a warning message appears “Remove Keyman? on the screen with the ‘Delete App’ option.
+5. Click the ‘Delete App’ option.
+6. Verify that another warning message “Delete Keyman? - Delete this app will also delete its data” appears on the Screen with ‘Delete’ and ‘Cancel’ button.
+7. Click the Delete button.
+8. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_163**
+
+Test case for US Basic Keyboard,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `163`
+- Product: `IOS`
+- Source files: `163.JSON`, `163.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC105
+
+
+Setup
+
+1. Install latest Keyman(.ios) build in iPhone / iPad device or Simulator.
+2. Ensure the device or emulator is enabled with internet connection.
+
+
+
+
+Action
+
+1. Click on the Keyman icon from the display.
+2. Verify that the Keyman application opens.
+3. Click the Settings option from the Keyboard list menu.
+4. Verify the Keyman Settings page opens.
+5. Click the Installed Languages option.
+6. Verify that the Install Languages menu opens.
+7. Click the (+) plus button which appears at the top right corner of the screen.
+8. Type ‘US basic’ in the Keyboard Search bar.
+9. Verify that the US Basic Keyboard link appears on the keyboard list.
+10. Click the US Basic Keyboard link button.
+11. Verify that the Install Keyboard button appears on the screen.
+12. Click the Install Keyboard button.
+13. Verify that the ‘English’ has been selected in the available languages list menu.
+14. Click the Install button.
+15. Click the Done button.
+16. Verify that the ‘English - US Basic’ keyboard successfully installed and appeared as an active keyboard in the Keyman app.
+17. Type ‘US basic’ in the Keyboard Search bar.
+18. Verify that the US Basic Keyboard link appears on the keyboard list.
+19. Click the US Basic Keyboard link button.
+20. Verify that the Install Keyboard button appears on the screen.
+21. Click the Install Keyboard button.
+22. Click ‘Tagalog’ from the available languages list menu.
+23. Click the Install button.
+24. Click the Done button.
+25. Verify that the ‘Tagalog - US Basic’ keyboard successfully installed in the Keyman app.
+26. Set ‘English - US Basic’ keyboard as the active in-app keyboard.
+27. Verify that predictive text suggestions appear.
+28. Click the globe key.
+29. Click the ‘Tagalog - US Basic’ keyboard.
+30. Verify that predictive text suggestions do not appear.
+31. Click the number Key.
+32. Verify the number keys and special key appear on the number layer.
+33. Click the Special key.
+34. Verify that the currency and symbol layer appear on the keyboard.
+35. Select the currency layer, then press the £ key.
+36. Verify that the keyboard outputs correctly and returns to the default layer.
+37. Go to the symbol layer and press the © key.
+38. Verify that the keyboard outputs correctly and remains on the symbol layer.
+39. Revert to the default layer and ensure basic key inputs work.
+40. Long-press e on the default layer and select a subkey.
+41. Verify that the selected key produces the correct output.
+42. Click the Setting option from the Keyboard list menu.
+43. Verify that the Keyman Settings menu opens.
+44. Click the Installed Languages option.
+45. Verify that the Installed Languages menu opens.
+46. Click the ‘English’ keyboard option.
+47. Verify that the US Basic English keyboard appears under the EuroLatin (SIL) keyboard.
+48. Click the US Basic English keyboard option.
+49. Verify that the US Basic English keyboard menu opens.
+50. Click the Keyboard Help option.
+51. Verify that the US Basic English Keyboard help topic opens.
+52. Click the Installed Languages option.
+53. Verify that the Installed Languages menu opens.
+54. Click the ‘Tagalog’ Keyboard option.
+55. Verify that the Tagalog Settings menu opens.
+56. Click the US Basic Keyboard option.
+57. Verify that the Tagalog Settings / US Basic menu opens.
+58. Click the Keyboard Help option.
+59. Verify that the US Basic keyboard help topic opens.
+60. scan the QR code with a phone
+61. Verify that it links to the current version of that keyboard's public download page on keyman.com.
+62. Click the Settings button from the Keyman list menu.
+63. Click the Installed Languages option.
+64. Click the English (2 keyboards installed) Keyboard option.
+65. Verify that the English Settings menu opens.
+66. Click the US Basic keyboard option.
+67. Verify that the US Basic menu opens.
+68. Click the Uninstall Keyboard option.
+69. Verify that “would you like to uninstall this keyboard?” warning message appears with Cancel and Uninstall buttons.
+70. Click the Uninstall button.
+71. Verify that the US Basic - English Keyboard was successfully uninstalled from the Installed languages menu.
+
+
+
+
+Cleanup
+
+1. Long press the Keyman icon from the display.
+2. Verify that the “Remove App” option appears on the screen.
+3. Click the “Remove App” option.
+4. Verify that a warning message appears “Remove Keyman? on the screen with the ‘Delete App’ option.
+5. Click the ‘Delete App’ option.
+6. Verify that another warning message “Delete Keyman? - Delete this app will also delete its data” appears on the Screen with ‘Delete’ and ‘Cancel’ button.
+7. Click the Delete button.
+8. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_165**
+
+Test case for Long Press on all layers in the On Screen Keyboard,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `165`
+- Product: `IOS`
+- Source files: `165.JSON`, `165.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC107
+
+
+Setup
+
+1. Install latest Keyman(.ios) build in iPhone / iPad device or Simulator.
+2. Ensure the device or emulator is enabled with internet connection.
+
+
+
+
+Action
+
+1. Click on the Keyman icon from the display.
+2. Verify that the Keyman application opens.
+3. Verify that EuroLatin (SIL) keyboard appeared as the active keyboard.
+4. Verify the Shift layer is enabled.
+5. Long press A Base key from the keyboard.
+6. Verify that the Sub Key menu appears at the top of the Base key A.
+7. Click one of the sub key letters.
+8. Verify that the Sub Key letter appears in the input text screen.
+9. Click the Shift Key.
+10. Verify the Shift layer is disabled.
+11. Long press ‘a’ Base key from the keyboard.
+12. Verify that the Sub Key menu appears at the top of the Base Key a.
+13. Click one of the sub key letters.
+14. Verify that the Sub Key letter appears in the input text screen.
+15. Click the Num key.
+16. Long press 1 Base key.
+17. Verify that the Sub key menu appears at the top of the Base key 1.
+18. Click one of the sub key numbers.
+19. Verify that the Sub key number appears in the input text screen.
+
+
+
+
+Cleanup
+
+1. Long press the Keyman icon from the display.
+2. Verify that the “Remove App” option appears on the screen.
+3. Click the “Remove App” option.
+4. Verify that a warning message appears “Remove Keyman? on the screen with the ‘Delete App’ option.
+5. Click the ‘Delete App’ option.
+6. Verify that another warning message “Delete Keyman? - Delete this app will also delete its data” appears on the Screen with ‘Delete’ and ‘Cancel’ button.
+7. Click the Delete button.
+8. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_168**
+
+Test case for for changing UI language into Amharic in the Keyman In-App,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `168`
+- Product: `IOS`
+- Source files: `168.JSON`, `168.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC110
+
+
+Setup
+
+1. Install latest Keyman(.ios) build in iPhone / iPad device or Simulator.
+2. Ensure the device or emulator is enabled with internet connection.
+
+
+
+
+Action
+
+1. Click the Settings icon from the iOS device / emulator.
+2. Verify that the Settings menu opens.
+3. Click the General option.
+4. Verify the General menu opens.
+5. Click the Language & Religion option.
+6. Click the Add language blue link button.
+7. Type “Amharic” in the Search bar.
+8. Verify the Amharic language appears on the Screen.
+9. Click the Amharic language.
+10. Verify that the ‘Prefer Amharic’ option appears on the Screen.
+11. Click the Prefer Amharic option.
+12. Verify the Amharic language has been updated on the device.
+13. Click on the Keyman icon from the display.
+14. Verify that the Keyman application opens.
+15. Click the Settings option from the Keyman list menu.
+16. Verify the UI language of the Keyman Settings menu has been changed to Amharic language.
+17. Verify that the UI of the Keyman menu list should appear in Amharic.
+
+
+
+
+Cleanup
+
+1. Long press the Keyman icon from the display.
+2. Verify that the “Remove App” option appears on the screen.
+3. Click the “Remove App” option.
+4. Verify that a warning message appears “Remove Keyman? on the screen with the ‘Delete App’ option.
+5. Click the ‘Delete App’ option.
+6. Verify that another warning message “Delete Keyman? - Delete this app will also delete its data” appears on the Screen with ‘Delete’ and ‘Cancel’ button.
+7. Click the Delete button.
+8. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_170**
+
+Test case for bug(iOS): predictive-text consistency after backspaces #10127,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `170`
+- Product: `IOS`
+- Source files: `170.JSON`, `170.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC215
+
+
+Setup
+
+1. Install Keyman's latest Stable build from the Keyman.com site.
+2. Install sil_euro_latin keyboard.
+
+
+
+
+Action
+
+1. Open Keyman In-App.
+2. Type ‘somwwhat’.
+3. Press the Backspace key until ‘somw’.
+4. Verify the Predictions should be displayed on the suggestion banner.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Taskbar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully
+
+
+
+---
+
+**TEST_349**
+
+Slide dismissal of keyboard-height adjuster will properly resize the keyboard_TEST_REPRO_13443
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `349`
+- Product: `IOS`
+- Source files: `349.JSON`, `349.html`
+
+
+
+**Description**
+
+TC - fix(ios): slide dismissal of keyboard-height adjuster will properly resize the keyboard_TEST_REPRO_13443 #13631
+
+
+Setup
+
+1. Install the latest Keyman (.dmg)build on the iPad device/simulator.
+2. Accept all the iOS permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Dismiss the "Get Started" dialog.
+3. Open Keyman Settings -> Adjust Keyboard Height.
+4. Verify that the "Adjust Keyboard" page appears.
+5. Change the keyboard's height sufficiently to be noticed when you exit the settings.
+6. Swipe down on the sheet so that "Adjust Keyboard" is dismissed.
+7. Verify that the "Adjust Keyboard" returns to the main(text-editing view)
+8. Verify that the keyboard appears automatically, with no need to tap in the text area.
+9. Verify that the keyboard size change and matches the adjustment from step 5.
+
+
+
+
+Cleanup
+
+1. Long-press the Keyman icon from the display.
+2. Verify that the “Remove App” option appears on the screen.
+3. Click the “Remove App” option.
+4. Verify that a warning message appears “Remove Keyman? on the screen with the ‘Delete App’ option.
+5. Click the ‘Delete App’ option.
+6. Verify that another warning message “Delete Keyman? - Delete this app will also delete its data” appears on the Screen with ‘Delete’ and ‘Cancel’ buttons.
+7. Click the Delete button.
+8. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_351**
+
+Do not show notification for downloaded keyboard when showing its installer_TEST_REPRO_12590_SINGLE
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `351`
+- Product: `IOS`
+- Source files: `351.JSON`, `351.html`
+
+
+
+**Description**
+
+TC - fix(ios): do not show notification for downloaded keyboard when showing its installer_TEST_REPRO_12590_SINGLE #13687
+
+
+Setup
+
+1. Install the latest Keyman (.dmg)build on the iPad device/simulator.
+2. Accept all the iOS permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Dismiss the "Get Started" dialog.
+3. Navigate to the "Installed Languages" page by clicking the three dots --> settings --> Installed Languages
+4. Click on the “+” icon at the top right.
+5. Search "ekwtamil99uni"
+6. Click on the "Thamizha Tamil99" keyboard.
+7. Verify that the keyboard information page appears.
+8. Click on the “Install keyboard” button.
+9. The screen closes and moves back to the “Installed Languages” page for a few seconds.
+10. Verify that the package-installer page appears with no effects of the issue.
+
+
+
+
+Cleanup
+
+1. Long-press the Keyman icon from the display.
+2. Verify that the “Remove App” option appears on the screen.
+3. Click the “Remove App” option.
+4. Verify that a warning message appears “Remove Keyman? on the screen with the ‘Delete App’ option.
+5. Click the ‘Delete App’ option.
+6. Verify that another warning message “Delete Keyman? - Delete this app will also delete its data” appears on the Screen with ‘Delete’ and Cancel’ buttons.
+7. Click the Delete button.
+8. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_353**
+
+Do not show notification for downloaded keyboard when showing its installer_TEST_REPRO_UPDATES_AVAILABLE
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `353`
+- Product: `IOS`
+- Source files: `353.JSON`, `353.html`
+
+
+
+**Description**
+
+TC - fix(ios): do not show notification for downloaded keyboard when showing its installer_TEST_REPRO_UPDATES_AVAILABLE #13687
+
+
+Setup
+
+1. Install the older Keyman version( 18 stable version *.dmg) on the iPhone or iPad device/simulator.
+2. Accept all the iOS permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+8. Go to jahorton.github.io page.
+9. Download the khmer_angkor.kmp older version package.
+10. Install khmer_angkor.kmp the package which was downloaded earlier step.
+
+
+
+
+Action
+
+1. Install the latest Keyman 19 version.
+2. Launch the Keyman app.
+3. Dismiss the "Get Started" dialog.
+4. Navigate to the "Installed Languages" page by clicking the three dots --> settings --> Installed Languages
+5. Return to the main screen and close Keyman from the back end.
+6. Reopen the Keyman app.
+7. Dismiss the "Get Started" dialog.
+8. Navigate to the "Installed Languages" page by clicking the three dots --> settings --> Installed Languages
+9. Click on the “+” icon at the top right.
+10. Search "ekwtamil99uni"
+11. Verified that the “Update Available” appears
+
+
+
+
+Cleanup
+
+1. Long-press the Keyman icon from the display.
+2. Verify that the “Remove App” option appears on the screen.
+3. Click the “Remove App” option.
+4. Verify that a warning message appears “Remove Keyman? on the screen with ‘Delete App’ option.
+5. Click the ‘Delete App’ option.
+6. Verify that another warning message “Delete Keyman? - Delete this app will also delete its data” appears on the Screen with ‘Delete’ and Cancel’ button.
+7. Click the Delete button.
+8. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_356**
+
+Allow swipe-dismissal of Settings to be cancelled_TEST_BUTTON_DISMISSAL
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `356`
+- Product: `IOS`
+- Source files: `356.JSON`, `356.html`
+
+
+
+**Description**
+
+TC - fix(ios): allow swipe-dismissal of Settings to be cancelled_TEST_BUTTON_DISMISSAL #13686
+
+
+Setup
+
+1. Install the latest Keyman version(*.dmg) on the iPhone or iPad device/simulator.
+2. Accept all the iOS permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Dismiss the "Get Started" dialog.
+3. Open Keyman Settings by clicking the three dots --> Settings
+4. Tap on the Adjust Keyboard Height.
+5. Verify that the "Adjust Keyboard" page appears
+6. Change the height of the keyboard to 50% height of the screen.
+7. Verify that the keyboard template changed.
+8. Click the "Back" button on the "Adjust Keyboard"
+9. Click the "Done" on the "Keyman settings" page
+10. Verify that the keyboard appears automatically, with no need to tap in the editor page.
+11. Confirm that the keyboard height is changed to 50% height of the screen.
+
+
+
+
+Cleanup
+
+1. Long-press the Keyman icon from the display.
+2. Verify that the “Remove App” option appears on the screen.
+3. Click the “Remove App” option.
+4. Verify that a warning message appears “Remove Keyman? on the screen with the ‘Delete App’ option.
+5. Click the ‘Delete App’ option.
+6. Verify that another warning message “Delete Keyman? - Delete this app will also delete its data” appears on the Screen with ‘Delete’ and Cancel’ button.
+7. Click the Delete button.
+8. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_358**
+
+Prevent re-display of keyboard when re-entering app to its menus_TEST_REPRO_13629
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `358`
+- Product: `IOS`
+- Source files: `358.JSON`, `358.html`
+
+
+
+**Description**
+
+fix(ios): prevent re-display of keyboard when re-entering app to its menus_TEST_REPRO_13629 #13630
+
+
+Setup
+
+1. Install the latest Keyman version(*.dmg) in the iPhone or iPad device/simulator.
+2. Accept all the iOS permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Open the "settings" menu by clicking the "three dots"
+3. Select the "System Keyboard Settings" option.
+4. Verify that the "Keyman" page appeared on the iPhone.
+5. At the top-left corner of the device: use the "< Keyman" system option to return directly from the system's Settings app to the Keyman app.
+6. Verify that the page redirects to the Keyman app's "Keyman" page.
+7. Verify that the keyboard did not appear on the "Keyman" page.
+
+
+
+
+Cleanup
+
+1. Long-press the Keyman icon from the display.
+2. Verify that the “Remove App” option appears on the screen.
+3. Click the “Remove App” option.
+4. Verify that a warning message appears “Remove Keyman? on the screen with the ‘Delete App’ option.
+5. Click the ‘Delete App’ option.
+6. Verify that another warning message “Delete Keyman? - Delete this app will also delete its data” appears on the Screen with ‘Delete’ and Cancel’ button.
+7. Click the Delete button.
+8. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_360**
+
+Prevent re-display of keyboard when re-entering app to its menus_TEST_REPRO_EST_REPRO_6387
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `360`
+- Product: `IOS`
+- Source files: `360.JSON`, `360.html`
+
+
+
+**Description**
+
+fix(ios): prevent re-display of keyboard when re-entering app to its menus_TEST_REPRO_EST_REPRO_6387 #13630
+
+
+Setup
+
+1. Install the latest Keyman version(*.dmg) on the iPhone or iPad device/simulator.
+2. Accept all the iOS permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Minimize the Keyman app using the "swipe gestures" (it stays under the recent).
+3. Launch your test device's Safari and visit https://jahorton.github.io.
+4. Download the sil_ipa.kmp option near the top.
+5. Go to the File app and then double-tap on the "sil_ipa.kmp" file.
+6. Verified that the Package installer appeared, and then the Keyboard did not appear on that.
+
+
+
+
+Cleanup
+
+1. Long-press the Keyman icon from the display.
+2. Verify that the “Remove App” option appears on the screen.
+3. Click the “Remove App” option.
+4. Verify that a warning message appears “Remove Keyman? on the screen with the ‘Delete App’ option.
+5. Click the ‘Delete App’ option.
+6. Verify that another warning message “Delete Keyman? - Delete this app will also delete its data” appears on the Screen with ‘Delete’ and Cancel’ button.
+7. Click the Delete button.
+8. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
diff --git a/docs/tests/acceptance/linux.md b/docs/tests/acceptance/linux.md
new file mode 100644
index 0000000000..dfd5381ed9
--- /dev/null
+++ b/docs/tests/acceptance/linux.md
@@ -0,0 +1,1207 @@
+# Linux Acceptance Tests
+
+**TEST_63**
+
+Test case for installing Keyman and onboard.
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `63`
+- Product: `Linux`
+- Source files: `63.JSON`, `63.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC35
+
+
+Setup
+
+Install the latest updates on the system:
+1. Open Terminal Window.
+2. Run "sudo apt update"
+3. Run "sudo apt --autoremove remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0"
+4. Run "rm -rf ~/.local/share/keyman/"
+5. Run "sudo rm -rf /usr/local/share/keyman/"
+6. Run "sudo add-apt-repository ppa:keymanapp/keyman-alpha"
+7. Run "sudo apt update"
+(for pre-beta tests, replace keyman-alpha with keyman-beta)
+8. Reboot
+
+
+
+
+Action
+
+1. Click the terminal icon on the Desktop.
+2. Verify the terminal window opens.
+3. Run "sudo apt update"
+4. Verify the system is up to date.
+5. Run "sudo apt install keyman onboard-keyman"
+6. Verify that this works without showing any error.
+
+
+
+
+Cleanup
+
+1. Open a Terminal window.
+2. Type “sudo apt --autoremove remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0”.
+3. Run the command below to remove leftover artifacts.
+4. rm -rf ~/.local/share/keyman/
+5. sudo rm -rf /usr/local/share/keyman/
+
+
+
+---
+
+**TEST_66**
+
+Test case for the installed keyboard appears in the keyboard dropdown
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `66`
+- Product: `Linux`
+- Source files: `66.JSON`, `66.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC38
+
+
+Setup
+
+1. Run to install the latest Keyman in the system.
+2. Install Khmer Angkor Keyboard.
+
+
+
+
+Action
+
+1. Open a terminal window.
+2. Run the “km-config”
+3. Verify the Keyman Configuration dialog opens.
+4. Verify the Khmer Angkor keyboard appears in the Configuration window.
+5. Verify that the language tag for the current keyboard appears in the keyboard.
+6. Verify the Keyboard language dropdown list appears in the taskbar (with the language name (Khmer) )
+7. Click the launcher icon on the Desktop.
+8. Type ‘Settings’ in the Search box.
+9. Verify that the Settings icon appears in the Desktop.
+10. Click Settings.
+11. Verify the Region & Language dialog opens.
+12. Verify the keyboard appears in the “Input Sources” list with the language name (eg., Khmer Angkor)
+
+
+
+
+Cleanup
+
+1. Open a Terminal window.
+2. Type “sudo apt --autoremove remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0”.
+3. Run the command below to remove leftover artifacts.
+4. rm -rf ~/.local/share/keyman/
+5. sudo rm -rf /usr/local/share/keyman/
+
+
+
+---
+
+**TEST_68**
+
+Test case for adding a keyboard for an additional language (Eurolatin (SIL)),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `68`
+- Product: `Linux`
+- Source files: `68.JSON`, `68.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC40
+
+
+Setup
+
+1. Run to install the latest Keyman in the system.
+
+
+
+
+Action
+
+1. Click the launcher icon on the desktop.
+2. Type “Keyman Configuration” in the search bar.
+3. Verify the “Keyman Configuration” dialog appears on the screen.
+4. Click the Download button.
+5. Type “Icelandic” in the Search box.
+6. Click the “EuroLatin (SIL) (Icelandic language)” keyboard from the menu list.
+7. Click “Install Keyboard”
+8. Verify that the Readme file appears in the install window.
+9. Click the “Install” button.
+10. Verify that the Welcome file appears after installation.
+11. Verify that the new keyboard, Eurolatin (SIL) appears in the “Keyman Configuration” dialog.
+12. Verify the new Keyboard appears on the top right of the screen.
+
+
+
+
+Cleanup
+
+1. Open a Terminal window.
+2. Type “sudo apt --autoremove remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0”.
+3. Run the command below to remove leftover artifacts.
+4. rm -rf ~/.local/share/keyman/
+5. sudo rm -rf /usr/local/share/keyman/
+
+
+
+---
+
+**TEST_71**
+
+Test case for UI_About keyboard,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `71`
+- Product: `Linux`
+- Source files: `71.JSON`, `71.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC43
+
+
+Setup
+
+1. Install the latest Keyman in the system.
+2. Khmer Angkor Keyboard should be installed before following the steps.
+
+
+
+
+Action
+
+1. Open Terminal Window.
+2. Type a “km-config” command
+3. Press the “Enter” key.
+4. Verify that the Keyman Configuration dialog opens.
+5. Verify that the installed “Khmer Angkor” keyboard appears on the list.
+6. Select Khmer Angkor keyboard.
+7. Click the About button.
+8. Verify package and keyboard information are displayed.
+9. Verify that a QR Code link is displayed under Keyboard Information.
+
+
+
+
+Cleanup
+
+1. Open a Terminal window.
+2. Type “sudo apt --autoremove remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0”.
+3. Run the command below to remove leftover artifacts.
+4. rm -rf ~/.local/share/keyman/
+5. sudo rm -rf /usr/local/share/keyman/
+
+
+
+---
+
+**TEST_73**
+
+Test case for UI_Options from the Configuration dialog,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `73`
+- Product: `Linux`
+- Source files: `73.JSON`, `73.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC45
+
+
+Setup
+
+1. Run to install the latest Keyman in the system.
+2. EuroLatin (SIL) Keyboard should be installed and ready for testing.
+3. Tamil99 Keyboard should be installed and ready for test.
+
+
+
+
+Action
+
+1. Type ‘Keyman’ from launcher.
+2. Verify that the Keyman Configuration dialog box opens.
+3. Verify that the installed keyboards appear in the Keyman Configuration dialog.
+4. Select EuroLatin (SIL) Keyboard.
+5. Verify that the Options button is enabled.
+6. Click the Options button.
+7. Verify that the Options help page opens.
+8. Click the Close button.
+9. Verify that the Options help page closes.
+10. Select Tamil99 keyboard.
+11. Verify that the Options button is disabled.
+
+
+
+
+Cleanup
+
+1. Open Terminal window.
+2. Run
+3. Run to remove left-over artifacts
+4. Run
+
+
+
+---
+
+**TEST_76**
+
+Test case for km-package-install using Command line tools,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `76`
+- Product: `Linux`
+- Source files: `76.JSON`, `76.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC48
+
+
+Setup
+
+1. Install the latest Keyman in the system.
+
+
+
+
+Action
+
+1. Open Terminal Window
+2. Run "km-package-install"
+3. Verify that you get an error message.
+4. Run "km-package-install -p sil_korda_jamo"
+5. Verify that this adds the “Korean KORDA Jamo (SIL)” keyboard to the keyboard dropdown.
+6. Run "sudo km-package-install -s -f ~/.cache/keyman/hieroglyphic.kmp"
+7. Verify that this adds the “Hieroglyphic” keyboard for ancient Egyptian to the keyboard dropdown.
+8. Type km-package-install -p gff_amh
+9. Press the TAB key.
+10. Verify that this completes the command to "km-package-install -p gff_amharic"
+11. Run "man km-package-install"
+12. Verify it shows the manual page explaining the parameters.
+13. Open Chrome browser.
+14. Type “https://help.keyman.com/products/linux/15.0/reference/km-package-install “ in the Search box.
+15. Verify that the same information is in the manual page.
+
+
+
+
+Cleanup
+
+1. Open a Terminal window.
+2. Type “sudo apt --autoremove remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0”.
+3. Run the command below to remove leftover artifacts.
+4. rm -rf ~/.local/share/keyman/
+5. sudo rm -rf /usr/local/share/keyman/
+
+
+
+---
+
+**TEST_78**
+
+Test case for Keyman KVK2LDML file using Command line tools,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `78`
+- Product: `Linux`
+- Source files: `78.JSON`, `78.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC50
+
+
+Setup
+
+1. Run to install the latest Keyman in the system.
+
+
+
+
+Action
+
+1. Open a Terminal window.
+2. Run "km-kvk2ldml"
+3. Verify that an error message appears in the terminal window.
+4. Run "km-kvk2ldml -o /tmp/test.ldml ~/.local/share/keyman/khmer_angkor/khmer_angkor.kvk"
+5. Verify that the test.ldml file is created in the /tmp folder.
+6. Run "km-kvk2ldml -p ~/.local/share/keyman/khmer_angkor/khmer_angkor.kvk"
+7. Verify that this prints information about the keyboard.
+8. Run "km-kvk2ldml -k -p ~/.local/share/keyman/khmer_angkor/khmer_angkor.kvk"
+9. Verify that, in addition to the information about the keyboard, it prints the keys contained in the keyboard.
+10. Run "man km-kvk2ldml"
+11. Verify it shows the manual page explaining the parameters.
+12. Open Chrome browser.
+13. Type https://help.keyman.com/products/linux/15.0/reference/km-kvk2ldml in the search bar.
+14. Verify that the same information appears in the manual page too.
+(Note: Replace 15.0 with the Keyman version you're testing)
+
+
+
+
+Cleanup
+
+1. Open a Terminal window.
+2. Type “sudo apt --autoremove remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0”.
+3. Run the command below to remove leftover artifacts.
+4. rm -rf ~/.local/share/keyman/
+5. sudo rm -rf /usr/local/share/keyman/
+
+
+
+---
+
+**TEST_81**
+
+Test case for verifying specific keyboards,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `81`
+- Product: `Linux`
+- Source files: `81.JSON`, `81.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC53
+
+
+Setup
+
+1. Install the latest Keyman in the system.
+2. Install IPA (SIL) keyboard.
+3. Install the Korean KORDA Jamo (SIL) keyboard.
+4. Install Khmer Angkor keyboard.
+
+
+
+
+Action
+
+1. Click LibreOffice Writer.
+2. Verify that the LibreOffice Writer opens.
+3. Click the Keyman icon from the taskbar.
+4. Verify that the IPA (SIL) keyboard appears in the Keyman menu.
+5. Select IPA (SIL) keyboard.
+6. Type n > in the document.
+7. Verify that it shows ŋ in the document.
+8. Type ‘gedit’ from the launcher.
+9. Verify that the text editor opens.
+10. Type n > in the document.
+11. Verify that it shows ŋ in the document.
+12. Open LibreOffice document.
+13. Click the Keyman icon from the taskbar.
+14. Verify that the “Korean KORDA Jamo (SIL)” keyboard.
+15. Type hangeul.
+16. Verify that the result is “한글”
+17. Type ‘gedit’ from the launcher.
+18. Verify that the text editor opens.
+19. Type hangeul in the document.
+20. Verify that it shows “한글” in the document.
+21. Open LibreOffice document.
+22. Click the Keyman icon from the taskbar.
+23. Verify that the “Khmer Angkor” keyboard appears.
+24. Type xEjmr.
+25. Verify that it shows the result “ខ្មែរ”
+26. Type ‘gedit’ from the launcher.
+27. Verify that the text editor opens.
+28. Type xEjmr in the document.
+29. Verify that it shows “ខ្មែរ” in the document.
+30. Type ‘gedit’ from the launcher.
+31. Verify that the text editor opens.
+32. Click the Keyman icon from the taskbar.
+33. Verify that the “IPA (SIL)r” keyboard appears.
+34. Type
+an
+m
+35. Click after n
+36. Type >
+37. Verify that the output shows
+aŋ
+m
+
+
+
+
+Cleanup
+
+1. Open a Terminal window.
+2. Type “sudo apt --autoremove remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0”.
+3. Run the command below to remove leftover artifacts.
+4. rm -rf ~/.local/share/keyman/
+5. sudo rm -rf /usr/local/share/keyman/
+
+
+**TEST_83**
+
+Test case for update an existing installation,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `83`
+- Product: `Linux`
+- Source files: `83.JSON`, `83.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC55
+
+
+Setup
+
+1. Install the latest Keyman in the system.
+2. Install Khmer Angkor Keyboard.
+3. Install IPA (SIL) Keyboard.
+
+
+
+
+Action
+
+1. Open Terminal Window.
+2. Run "sudo apt --autoremove remove keyman"
+3. Run "sudo rm /etc/apt/sources.list.d/keymanapp-ubuntu-keyman*"
+4. Run "sudo add-apt-repository ppa:keymanapp/keyman"
+5. Run "sudo apt update"
+6. Run "sudo apt install keyman"
+7. Verify that this has installed the latest stable version.
+8. Click the Keyman icon, which appears in the taskbar.
+9. Verify that the Keyman keyboards still show up in the keyboards dropdown.
+10. Select Khmer Angkor Keyboard.
+11. Verify that the Khmer Angkor Keyboard icon appears in the taskbar instead of the Keyman icon.
+12. Open Text editor.
+13. Type xEjmr.
+14. Verify that the output results “ខ្មែរ” in the text editor.
+
+
+
+
+Cleanup
+
+1. Open a Terminal window.
+2. Type “sudo apt --autoremove remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0”.
+3. Run the command below to remove leftover artifacts.
+4. rm -rf ~/.local/share/keyman/
+5. sudo rm -rf /usr/local/share/keyman/
+
+
+
+---
+
+**TEST_86**
+
+Test case for bug(linux): backspace doesn't work in "Download Keyman keyboards" dialog #7971,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `86`
+- Product: `Linux`
+- Source files: `86.JSON`, `86.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC214
+
+
+Setup
+
+1. Install Keyman's latest Stable build from the Keyman.com site.
+2. Install Vietnamese_telex keyboard.
+
+
+
+
+Action
+
+1. Open the Keyman Configuration dialog box.
+2. Switch to Vietnamese_telex keyboard.
+3. Click on the Keyboard Search bar.
+4. Type ‘gox tieesn Vieejt’
+5. Verify it outputs gõ tiếng Việt
+
+
+
+
+Cleanup
+
+1. Open a Terminal window.
+2. Type “sudo apt --autoremove remove keyman ibus-keyman python3-keyman-config libkmnkbp0-0”.
+3. Run the command below to remove leftover artifacts.
+4. rm -rf ~/.local/share/keyman/
+5. sudo rm -rf /usr/local/share/keyman/
+
+
+
+---
+
+**TEST_88**
+
+KMX_PROCESSOR_NON_COMPLIANT_TEST_FRAME_KEY_RESET_MARKERS_GROUP_LINUX: Chrome Browser
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `88`
+- Product: `Linux`
+- Source files: `88.JSON`, `88.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC228
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Chrome browser.
+
+
+
+
+Action
+
+1. Click on the Chrome browser icon from Linux Desktop.
+2. Verify that the Chrome browser opens.
+3. Navigate to the "https://www.editpad.org/" page.
+4. Click in the edit box.
+5. Press `
+6. Verify it produces `
+7. Press the "right arrow"
+8. Type e
+9. Verify it produces `e
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Linux.
+2. Uninstall Chrome browser.
+
+
+
+---
+
+**TEST_90**
+
+KMX_PROCESSOR_NON_COMPLIANT_TEST_SCROLLLOCK_KEY_NO_RESET_GROUP_LINUX: Chrome Browser
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `90`
+- Product: `Linux`
+- Source files: `90.JSON`, `90.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC230
+
+
+Setup
+
+1. Install Keyman build.
+2. Install TextEdit app.
+
+
+
+
+Action
+
+1. Click on the Chrome browser icon from Linux Desktop.
+2. Verify that the Chrome browser opens.
+3. Navigate to the "https://www.editpad.org/" page.
+4. Click in the edit box.
+5. Press `
+6. Verify it produces `
+7. Press the "scroll lock" key
+8. Type e
+9. Verify it produces è
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Linux.
+2. Uninstall Chrome browser.
+
+
+
+---
+
+**TEST_91**
+
+KMX_PROCESSOR_COMPLIANT_TEST_CONTROL_1_GROUP_LINUX: gedit
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `91`
+- Product: `Linux`
+- Source files: `91.JSON`, `91.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC240
+
+
+Setup
+
+1. Install Keyman build.
+
+
+
+
+Action
+
+1. Click on the “gedit” App icon from Linux Desktop.
+2. Verify that the “gedit” Application opens.
+3. Type `
+4. Verify it produces e.
+5. Verify it produces è
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Linux
+
+
+
+---
+
+**TEST_93**
+
+KMX_PROCESSOR_COMPLIANT_TEST_FRAME_KEY_RESET_NOMARKERS_GROUP_LINUX: gedit
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `93`
+- Product: `Linux`
+- Source files: `93.JSON`, `93.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC242
+
+
+Setup
+
+1. Install Keyman build.
+
+
+
+
+Action
+
+1. Click on the “gedit” App icon from Linux Desktop.
+2. Verify that the “gedit” Application opens.
+3. Press 1 \ \
+4. Verify it produces 1 \ \
+5. Press the "right arrow"
+6. Type 2
+7. Verify it produces 1/2
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Linux
+
+
+
+---
+
+**TEST_94**
+
+KMX_PROCESSOR_COMPLIANT_TEST_SCROLLLOCK_KEY_NO_RESET_GROUP_LINUX: gedit
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `94`
+- Product: `Linux`
+- Source files: `94.JSON`, `94.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC243
+
+
+Setup
+
+1. Install Keyman build.
+
+
+
+
+Action
+
+1. Click on the “gedit” App icon from Linux Desktop.
+2. Verify that the “gedit” Application opens.
+3. Press `
+4. Verify it produces `
+5. Press the "Scroll Lock"
+6. Type e
+7. Verify it produces è
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Linux
+
+
+
+---
+
+**TEST_96**
+
+LDML_PROCESSOR_NON_COMPLIANT_TEST_FRAME_KEY_RESET_MARKERS_GROUP_LINUX: Chrome Browser
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `96`
+- Product: `Linux`
+- Source files: `96.JSON`, `96.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC255
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Chrome browser.
+
+
+
+
+Action
+
+1. Click on the Chrome browser icon from Linux Desktop.
+2. Verify that the Chrome browser opens.
+3. Navigate to the "www.google.com" page.
+4. Click in the search box.
+5. Type ^
+6. Verify it produces ^.
+7. Press the “right arrow”(->)
+8. Verify it produces e
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Linux.
+2. Uninstall Chrome browser.
+
+
+
+---
+
+**TEST_97**
+
+LDML_PROCESSOR_NON_COMPLIANT_TEST_FRAME_KEY_RESET_NO_MARKERS_GROUP_LINUX: Chrome Browser
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `97`
+- Product: `Linux`
+- Source files: `97.JSON`, `97.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC256
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Chrome browser.
+
+
+
+
+Action
+
+1. Click on the Chrome browser icon from Linux Desktop.
+2. Verify that the Chrome browser opens.
+3. Navigate to the "www.google.com" page.
+4. Click in the search box.
+5. Press a
+6. Verify it produces a
+7. Press the "right arrow"(->)
+8. Press the SHIFT + 8
+9. Verify it produces a*
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Linux.
+2. Uninstall Chrome browser.
+
+
+
+---
+
+**TEST_98**
+
+LDML_PROCESSOR_NON_COMPLIANT_TEST_FRAME_SCROLL_LOCK_NO_RESET_GROUP_LINUX: Chrome Browser
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `98`
+- Product: `Linux`
+- Source files: `98.JSON`, `98.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC257
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Chrome browser.
+
+
+
+
+Action
+
+1. Click on the Chrome browser icon from Linux Desktop.
+2. Verify that the Chrome browser opens.
+3. Navigate to the "www.google.com" page.
+4. Click in the search box.
+5. Press ^
+6. Verify it produces ^
+7. Press the "Scroll Lock"
+8. Press the e
+9. Verify it produces ê
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Linux.
+2. Uninstall Chrome browser.
+
+
+
+---
+
+**TEST_100**
+
+LDML_PROCESSOR_COMPLIANT_TEST_CONTROL_1_LINUX: gedit
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `100`
+- Product: `Linux`
+- Source files: `100.JSON`, `100.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC269
+
+
+Setup
+
+1. Install Keyman build.
+2. Install gedit app.
+
+
+
+
+Action
+
+1. Click on the gedit App icon from Linux Desktop.
+2. Verify that the gedit Application opens.
+3. Press ^
+4. Verify it produces ^
+5. Type e
+6. Verify it produces ê
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Linux
+2. Uninstall the gedit app.
+
+
+
+---
+
+**TEST_101**
+
+LDML_PROCESSOR_COMPLIANT_TEST_FRAME_KEY_RESET_MARKERS_LINUX: gedit
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `101`
+- Product: `Linux`
+- Source files: `101.JSON`, `101.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC270
+
+
+Setup
+
+1. Install Keyman build.
+2. Install gedit app.
+
+
+
+
+Action
+
+1. Click on the gedit App icon from Linux Desktop.
+2. Verify that the gedit Application opens.
+3. Press ^
+4. Verify it produces ^
+5. Press the "right arrow(->)"
+6. Type e
+7. Verify it produces e
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Linux.
+2. Uninstall the gedit app.
+
+
+
+---
+
+**TEST_103**
+
+LDML_PROCESSOR_COMPLIANT_TEST_FRAME_SCROLL_LOCK_NO_RESET_LINUX: gedit
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `103`
+- Product: `Linux`
+- Source files: `103.JSON`, `103.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC272
+
+
+Setup
+
+1. Install Keyman build.
+2. Install gedit app.
+
+
+
+
+Action
+
+1. Click on the gedit App icon from Linux Desktop.
+2. Verify that the gedit Application opens.
+3. Press ^
+4. Verify it produces ^
+5. Press the "Scroll Lock" key
+6. Type e
+7. Verify it produces ê
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Linux.
+2. Uninstall the gedit app.
+
+
+
+---
+
+**TEST_104**
+
+LDML_PROCESSOR_COMPLIANT_TEST_MODIFIER_TAP_NO_RESET_GROUP_LINUX: gedit
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `104`
+- Product: `Linux`
+- Source files: `104.JSON`, `104.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC273
+
+
+Setup
+
+1. Install Keyman build.
+2. Install gedit app.
+
+
+
+
+Action
+
+1. Click on the gedit App icon from Linux Desktop.
+2. Verify that the gedit Application opens.
+3. Press ^
+4. Verify it produces ^
+5. Press and Release CTRL key.
+6. Type e
+7. Verify it produces ê
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Linux
+2. Uninstall the gedit app.
+
+
+
+---
+
diff --git a/docs/tests/acceptance/mac.md b/docs/tests/acceptance/mac.md
new file mode 100644
index 0000000000..6262f62111
--- /dev/null
+++ b/docs/tests/acceptance/mac.md
@@ -0,0 +1,1629 @@
+# macOS Acceptance Tests
+
+**TEST_173**
+
+Test case for Chrome_Google_Docs with Amharic,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `173`
+- Product: `MAC`
+- Source files: `173.JSON`, `173.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC113
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Amharic keyboard.
+3. Install Chrome browser.
+
+
+
+
+Action
+
+1. Click on the Chrome browser icon from macOS Desktop.
+2. Verify that the Chrome browser opens.
+3. Open Google document.
+4. Type t a
+5. Verify it produces ታ.
+6. Type t, left-arrow, a
+7. Verify it produces አት
+8. Type t t, left-arrow, a
+9. Verify it produces ትአት
+10. Type t t
+11. Mouse-clicking between the two ትት characters.
+12. Type a
+13. Verify it produces ትአት
+14. Verify in each of three cases, the insertion point should end up before the final ት character.
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+2. Uninstall the Amharic keyboard.
+3. Uninstall the Chrome browser.
+
+
+
+---
+
+**TEST_175**
+
+Test case for ATOM editor with Amharic,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `175`
+- Product: `MAC`
+- Source files: `175.JSON`, `175.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC115
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Amharic keyboard.
+3. Install Atom Editor.
+
+
+
+
+Action
+
+1. Click on the Atom Editor icon from the macOS Desktop.
+2. Verify the Atom Editor opens.
+3. Type t a
+4. Verify it produces ታ.
+5. Type t, left-arrow, a
+6. Verify it produces አት
+7. Type t t, left-arrow, a
+8. Verify it produces ትአት
+9. Type t t
+10. Mouse-clicking between the two ትት characters.
+11. Type a
+12. Verify it produces ትአት
+13. Verify in each of three cases, the insertion point should end up before the final ት character.
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+2. Uninstall the Amharic keyboard.
+3. Uninstall Atom Editor.
+
+
+
+---
+
+**TEST_178**
+
+Test case for Safari_Google_Docs with Amharic,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `178`
+- Product: `MAC`
+- Source files: `178.JSON`, `178.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC118
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Amharic keyboard.
+3. Install Safari browser.
+
+
+
+
+Action
+
+1. Click on the Safari browser icon from macOS Desktop.
+2. Verify that the Safari browser opens.
+3. Open Google document.
+4. Type t a
+5. Verify it produces ታ.
+6. Type t, left-arrow, a
+7. Verify it produces አት
+8. Type t t, left-arrow, a
+9. Verify it produces ታት
+10. Type t t
+11. Mouse-clicking between the two ታ characters.
+12. Type a
+13. Verify it produces ታት
+14. Verify in each of three cases, the insertion point should end up before the final ት character.
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+2. Uninstall the Amharic keyboard.
+3. Uninstall Safari browser.
+
+
+
+---
+
+**TEST_180**
+
+Test case for Firefox_URL_Bar with Amharic,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `180`
+- Product: `MAC`
+- Source files: `180.JSON`, `180.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC120
+
+
+Setup
+
+1. Install Keyman build on the device.
+2. Install Amharic keyboard.
+3. Install Firefox browser.
+
+
+
+
+Action
+
+1. Click on the Firefox browser icon from macOS Desktop.
+2. Verify that the Firefox browser opens.
+3. Click on the URL bar.
+4. Type t a
+5. Verify it produces ታ.
+6. Type t, left-arrow, a
+7. Verify it produces አት
+8. Type t t, left-arrow, a
+9. Verify it produces ትአት
+10. Type t t
+11. Mouse-clicking between the two ትት characters.
+12. Type a
+13. Verify it produces ትአት
+14. Verify in each of three cases, the insertion point should end up before the final ት character.
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+2. Uninstall the Amharic keyboard.
+3. Uninstall the Firefox browser.
+
+
+
+---
+
+**TEST_183**
+
+Test case for Firefox_Word_Online with Amharic,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `183`
+- Product: `MAC`
+- Source files: `183.JSON`, `183.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC123
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Amharic keyboard.
+3. Install Firefox browser.
+
+
+
+
+Action
+
+1. Click on the Firefox browser icon from macOS Desktop.
+2. Verify that the Firefox browser opens.
+3. Open the ‘Word online’ document.
+4. Type t a
+5. Verify it produces ታ.
+6. Type t, left-arrow, a
+7. Verify it produces አት
+8. Type t t, left-arrow, a
+9. Verify it produces ትአት
+10. Type t t
+11. Mouse-clicking between the two ትት characters.
+12. Type a
+13. Verify it produces ትአት
+14. Verify in each of three cases, the insertion point should end up before the final ት character.
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+2. Uninstall the Amharic keyboard.
+3. Uninstall the Firefox browser.
+
+
+
+---
+
+**TEST_185**
+
+Test case for Notes_App with Amharic,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `185`
+- Product: `MAC`
+- Source files: `185.JSON`, `185.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC125
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Amharic keyboard.
+3. Install Notes App.
+
+
+
+
+Action
+
+1. Click on the Notes App icon from macOS Desktop.
+2. Verify that the Notes Application opens.
+3. Type t a
+4. Verify it produces ታ.
+5. Type t, left-arrow, a
+6. Verify it produces አት
+7. Type t t, left-arrow, a
+8. Verify it produces ታት
+9. Type t t
+10. Mouse-clicking between the two ታ characters.
+11. Type a
+12. Verify it produces ታት
+13. Verify in each of three cases, the insertion point should end up before the final ት character.
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+2. Uninstall the Amharic keyboard.
+3. Uninstall Notes App.
+
+
+
+---
+
+**TEST_188**
+
+Test case for LibreOffice Writer with Amharic,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `188`
+- Product: `MAC`
+- Source files: `188.JSON`, `188.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC128
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Amharic keyboard.
+3. Install LibreOffice 7.0 app.
+
+
+
+
+Action
+
+1. Click on the LibreOffice Writer icon from the macOS Desktop.
+2. Verify that the LibreOffice Writer Application opens.
+3. Type t a
+4. Verify it produces ታ.
+5. Type t, left-arrow, a
+6. Verify it produces አት
+7. Type t t, left-arrow, a
+8. Verify it produces ትአት
+9. Type t t
+10. Mouse-clicking between the two ትት characters.
+11. Type a
+12. Verify it produces ትአት
+13. Verify in each of three cases, the insertion point should end up before the final ት character.
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+2. Uninstall the Amharic keyboard.
+3. Uninstall LibreOffice 7.0 app.
+
+
+
+---
+
+**TEST_190**
+
+Test case for Chrome_URL_Bar with Shortcuts,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `190`
+- Product: `MAC`
+- Source files: `190.JSON`, `190.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC130
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Chrome browser.
+
+
+
+
+Action
+
+1. Click on the Chrome browser icon.
+2. Verify that the Chrome browser opens.
+3. Press Command + F (⌘+F) keys from magic keyboard.
+4. Verify that the Find or Control dialog box opens.
+5. Press Command + O (⌘-O) keys from magic keyboard.
+6. Verify that the File opens.
+7. Type ‘testing’ in the URL bar.
+8. Press Command + A (⌘-A) keys from magic keyboard.
+9. Verify that the text ‘testing’ has been selected.
+10. Press Command + X (⌘-X) keys from magic keyboard.
+11. Verify that the text ‘testing’ has been cut from the URL.
+12. Press Command + V (⌘-V) keys from magic keyboard.
+13. Verify that the text ‘testing’ has been pasted in the URL.
+14. Press Command + C (⌘-C) keys from magic keyboard.
+15. Verify that the text ‘testing’ has been copied from the URL.
+16. Press Command + V (⌘-V) keys from magic keyboard.
+17. Verify that the text ‘testing’ has been pasted in the URL.
+18. Press Command + A (⌘-A) keys from magic keyboard.
+19. Verify that the text ‘testing’ has been selected.
+20. Type t
+21. Verify it replaces selected characters with ት
+22. Type a t
+23. Press Command + A (⌘-A) keys
+24. Verify that the text ‘testing’ has been selected.
+25. Type a
+26. Verify it produces አ
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+2. Uninstall Chrome browser.
+
+
+
+---
+
+**TEST_193**
+
+Test case for Chrome_Word_Online with Shortcuts,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `193`
+- Product: `MAC`
+- Source files: `193.JSON`, `193.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC133
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Chrome browser.
+
+
+
+
+Action
+
+1. Click on the Chrome browser icon from macOS Desktop.
+2. Verify that the Chrome browser opens.
+3. Open ‘Word online’ document.
+4. Press Command + F (⌘+F) keys from magic keyboard.
+5. Verify that the Find or Control dialog box opens.
+6. Press Command + O (⌘-O) keys from magic keyboard.
+7. Verify that the File opens.
+8. Type ‘testing’ in the URL bar.
+9. Press Command + A (⌘-A) keys from magic keyboard.
+10. Verify that the text ‘testing’ has been selected.
+11. Press Command + X (⌘-X) keys from magic keyboard.
+12. Verify that the text ‘testing’ has been cut from the URL.
+13. Press Command + V (⌘-V) keys from magic keyboard.
+14. Verify that the text ‘testing’ has been pasted in the URL.
+15. Press Command + C (⌘-C) keys from magic keyboard.
+16. Verify that the text ‘testing’ has been copied from the URL.
+17. Press Command + V (⌘-V) keys from magic keyboard.
+18. Verify that the text ‘testing’ has been pasted in the URL.
+19. Press Command + A (⌘-A) keys from magic keyboard.
+20. Verify that the text ‘testing’ has been selected.
+21. Type t
+22. Verify it replaces selected characters with ት
+23. Type a t
+24. Press Command + A (⌘-A) keys
+25. Verify that the text ‘testing’ has been selected.
+26. Type a
+27. Verify it produces አ
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+2. Uninstall Chrome browser.
+
+
+
+---
+
+**TEST_195**
+
+Test case for Safari_URL_Bar with Shortcuts,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `195`
+- Product: `MAC`
+- Source files: `195.JSON`, `195.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC135
+
+
+Setup
+
+1. Install Keyman build.
+
+
+
+
+Action
+
+1. Click on the Safari browser icon from macOS Desktop.
+2. Verify that the Safari browser opens.
+3. Click on the URL bar.
+4. Press Command + F (⌘+F) keys from magic keyboard.
+5. Verify that the Find or Control dialog box opens.
+6. Press Command + O (⌘-O) keys from magic keyboard.
+7. Verify that the File opens.
+8. Type ‘testing’ in the URL bar.
+9. Press Command + A (⌘-A) keys from magic keyboard.
+10. Verify that the text ‘testing’ has been selected.
+11. Press Command + X (⌘-X) keys from magic keyboard.
+12. Verify that the text ‘testing’ has been cut from the URL.
+13. Press Command + V (⌘-V) keys from magic keyboard.
+14. Verify that the text ‘testing’ has been pasted in the URL.
+15. Press Command + C (⌘-C) keys from magic keyboard.
+16. Verify that the text ‘testing’ has been copied from the URL.
+17. Press Command + V (⌘-V) keys from magic keyboard.
+18. Verify that the text ‘testing’ has been pasted in the URL.
+19. Press Command + A (⌘-A) keys from magic keyboard.
+20. Verify that the text ‘testing’ has been selected.
+21. Type t
+22. Verify it replaces selected characters with ት
+23. Type a t
+24. Press Command + A (⌘-A) keys from magic keyboard.
+25. Verify that the text ‘testing’ has been selected.
+26. Type a
+27. Verify it produces አ
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+
+
+
+---
+
+**TEST_198**
+
+Test case for Safari_World_Online with Shortcuts,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `198`
+- Product: `MAC`
+- Source files: `198.JSON`, `198.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC138
+
+
+Setup
+
+1. Install Keyman build.
+
+
+
+
+Action
+
+1. Click on the Safari browser icon from macOS Desktop.
+2. Verify that the Safari browser opens.
+3. Open ‘Word online’ document.
+4. Press Command + F (⌘+F) keys from magic keyboard.
+5. Verify that the Find or Control dialog box opens.
+6. Press Command + O (⌘-O) keys from magic keyboard.
+7. Verify that the File opens.
+8. Type ‘testing’ in the URL bar.
+9. Press Command + A (⌘-A) keys
+10. Verify that the text ‘testing’ has been selected.
+11. Press Command + X (⌘-X) keys from magic keyboard.
+12. Verify that the text ‘testing’ has been cut from the URL.
+13. Press Command + V (⌘-V) keys from magic keyboard.
+14. Verify that the text ‘testing’ has been pasted in the URL.
+15. Press Command + C (⌘-C) keys from magic keyboard.
+16. Verify that the text ‘testing’ has been copied from the URL.
+17. Press Command + V (⌘-V) keys from magic keyboard.
+18. Verify that the text ‘testing’ has been pasted in the URL.
+19. Press Command + A (⌘-A) keys from magic keyboard.
+20. Verify that the text ‘testing’ has been selected.
+21. Type t
+22. Verify it replaces selected characters with ት
+23. Type a t
+24. Press Command + A (⌘-A) keys
+25. Verify that the text ‘testing’ has been selected.
+26. Type a
+27. Verify it produces አ
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+
+
+
+---
+
+**TEST_200**
+
+Test case for Firefox_FB_Search_Control with Shortcuts,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `200`
+- Product: `MAC`
+- Source files: `200.JSON`, `200.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC140
+
+
+Setup
+
+1. Install Keyman build.
+
+
+
+
+Action
+
+1. Click on the Firefox browser icon from macOS Desktop.
+2. Verify that the Firefox browser opens.
+3. Type ‘www.facebook.com’ on the URL search bar.
+4. Press Enter key.
+5. Verify that the Facebook page opens.
+6. Verify the ‘Search Facebook’ bar appears on the page.
+7. Press Command + F (⌘+F) keys from magic keyboard.
+8. Verify that the Find or Control dialog box opens.
+9. Press Command + O (⌘-O) keys from magic keyboard.
+10. Verify that the File opens.
+11. Type ‘testing’ in the URL bar.
+12. Press Command + A (⌘-A) keys from magic keyboard.
+13. Verify that the text ‘testing’ has been selected.
+14. Press Command + X (⌘-X) keys from magic keyboard.
+15. Verify that the text ‘testing’ has been cut from the URL.
+16. Press Command + V (⌘-V) keys from magic keyboard.
+17. Verify that the text ‘testing’ has been pasted in the URL.
+18. Press Command + C (⌘-C) keys from magic keyboard.
+19. Verify that the text ‘testing’ has been copied from the URL.
+20. Press Command + V (⌘-V) keys from magic keyboard.
+21. Verify that the text ‘testing’ has been pasted in the URL.
+22. Press Command + A (⌘-A) keys from magic keyboard.
+23. Verify that the text ‘testing’ has been selected.
+24. Type t
+25. Verify it replaces selected characters with ት
+26. Type a t
+27. Press Command + A (⌘-A) keys
+28. Verify that the text ‘testing’ has been selected.
+29. Type a
+30. Verify it produces አ
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+
+
+
+---
+
+**TEST_203**
+
+Test case for Messages_App with Shortcuts,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `203`
+- Product: `MAC`
+- Source files: `203.JSON`, `203.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC143
+
+
+Setup
+
+1. Install Keyman build.
+
+
+
+
+Action
+
+1. Click on the Message App icon from macOS Desktop.
+2. Verify that the Message Application opens.
+3. Click the To: line
+4. Press Command + F (⌘+F) keys from magic keyboard.
+5. Verify that the Find or Control dialog box opens.
+6. Press Command + O (⌘-O) keys from magic keyboard.
+7. Verify that the File opens.
+8. Type ‘testing’ in the URL bar.
+9. Press Command + A (⌘-A) keys from magic keyboard.
+10. Verify that the text ‘testing’ has been selected.
+11. Press Command + X (⌘-X) keys from magic keyboard.
+12. Verify that the text ‘testing’ has been cut from the URL.
+13. Press Command + V (⌘-V) keys from magic keyboard.
+14. Verify that the text ‘testing’ has been pasted in the URL.
+15. Press Command + C (⌘-C) keys from magic keyboard.
+16. Verify that the text ‘testing’ has been copied from the URL.
+17. Press Command + V (⌘-V) keys from magic keyboard.
+18. Verify that the text ‘testing’ has been pasted in the URL.
+19. Press Command + A (⌘-A) keys from magic keyboard.
+20. Verify that the text ‘testing’ has been selected.
+21. Type t
+22. Verify it replaces selected characters with ት
+23. Type a t
+24. Press Command + A (⌘-A) keys
+25. Verify that the text ‘testing’ has been selected.
+26. Type a
+27. Verify it produces አ
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+
+
+
+---
+
+**TEST_205**
+
+Test case for TextEdit_App with Shortcuts,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `205`
+- Product: `MAC`
+- Source files: `205.JSON`, `205.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC145
+
+
+Setup
+
+1. Install Keyman build.
+
+
+
+
+Action
+
+1. Click on the TextEdit App icon from macOS Desktop.
+2. Verify that the TextEdit Application opens.
+3. Press Command + F (⌘+F) keys from magic keyboard.
+4. Verify that the Find or Control dialog box opens.
+5. Press Command + O (⌘-O) keys from magic keyboard.
+6. Verify that the File opens.
+7. Type ‘testing’ in the URL bar.
+8. Press Command + A (⌘-A) keys from magic keyboard.
+9. Verify that the text ‘testing’ has been selected.
+10. Press Command + X (⌘-X) keys from magic keyboard.
+11. Verify that the text ‘testing’ has been cut from the URL.
+12. Press Command + V (⌘-V) keys from magic keyboard.
+13. Verify that the text ‘testing’ has been pasted in the URL.
+14. Press Command + C (⌘-C) keys from magic keyboard.
+15. Verify that the text ‘testing’ has been copied from the URL.
+16. Press Command + V (⌘-V) keys from magic keyboard.
+17. Verify that the text ‘testing’ has been pasted in the URL.
+18. Press Command + A (⌘-A) keys from magic keyboard.
+19. Verify that the text ‘testing’ has been selected.
+20. Type t
+21. Verify it replaces selected characters with ት
+22. Type a t
+23. Press Command + A (⌘-A) keys
+24. Verify that the text ‘testing’ has been selected.
+25. Type a
+26. Verify it produces አ
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+
+
+**TEST_208**
+
+Test case for MAIL app with Shortcuts,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `208`
+- Product: `MAC`
+- Source files: `208.JSON`, `208.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC148
+
+
+Setup
+
+1. Install Keyman build.
+
+
+
+
+Action
+
+1. Click on the MAIL icon from macOS Desktop.
+2. Verify that the Mail > message body opens.
+3. Press Command + F (⌘+F) keys from magic keyboard.
+4. Verify that the Find or Control dialog box opens.
+5. Press Command + O (⌘-O) keys from magic keyboard.
+6. Verify that the File opens.
+7. Type ‘testing’ in the URL bar.
+8. Press Command + A (⌘-A) keys from magic keyboard.
+9. Verify that the text ‘testing’ has been selected.
+10. Press Command + X (⌘-X) keys from magic keyboard.
+11. Verify that the text ‘testing’ has been cut from the URL.
+12. Press Command + V (⌘-V) keys from magic keyboard.
+13. Verify that the text ‘testing’ has been pasted in the URL.
+14. Press Command + C (⌘-C) keys from magic keyboard.
+15. Verify that the text ‘testing’ has been copied from the URL.
+16. Press Command + V (⌘-V) keys from magic keyboard.
+17. Verify that the text ‘testing’ has been pasted in the URL.
+18. Press Command + A (⌘-A) keys from magic keyboard.
+19. Verify that the text ‘testing’ has been selected.
+20. Type t
+21. Verify it replaces selected characters with ት
+22. Type a t
+23. Press Command + A (⌘-A) keys
+24. Verify that the text ‘testing’ has been selected.
+25. Type a
+26. Verify it produces አ
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+
+
+
+---
+
+**TEST_210**
+
+KMX_PROCESSOR_NON_COMPLIANT_TEST_CONTROL_1_GROUP_MAC: Chrome Browser
+
+Status: `Deprecated`
+
+
+Metadata
+
+- Source ID: `210`
+- Product: `MAC`
+- Source files: `210.JSON`, `210.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC222
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Chrome browser.
+
+
+
+
+Action
+
+1. Click on the Chrome browser icon from macOS Desktop.
+2. Verify that the Chrome browser opens.
+3. Navigate to the "www.google.com" page.
+4. Click in the search box.
+5. Type `
+6. Verify it produces e.
+7. Verify it produces è
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+2. Uninstall Chrome browser.
+
+
+
+---
+
+**TEST_213**
+
+KMX_PROCESSOR_NON_COMPLIANT_TEST_FRAME_KEY_RESET_NOMARKERS_GROUP_MAC: Chrome Browser
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `213`
+- Product: `MAC`
+- Source files: `213.JSON`, `213.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC225
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Chrome browser.
+
+
+
+
+Action
+
+1. Click on the Chrome browser icon from macOS Desktop.
+2. Verify that the Chrome browser opens.
+3. Navigate to the "www.google.com" page.
+4. Click in the search box.
+5. Press 1 / /
+6. Verify it produces 1 / /
+7. Press the "right arrow"
+8. Type 2
+9. Verify it produces 1//2
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+2. Uninstall Chrome browser.
+
+
+
+---
+
+**TEST_215**
+
+KMX_PROCESSOR_COMPLIANT_TEST_CONTROL_1_GROUP_MAC: TextEdit
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `215`
+- Product: `MAC`
+- Source files: `215.JSON`, `215.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC235
+
+
+Setup
+
+1. Install Keyman build.
+
+
+
+
+Action
+
+1. Click on the TextEdit App icon from MAC.
+2. Verify that the TextEdit Application opens.
+3. Type `
+4. Verify it produces e.
+5. Verify it produces è
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the MAC
+
+
+
+---
+
+**TEST_218**
+
+KMX_PROCESSOR_COMPLIANT_TEST_SCROLLLOCK_KEY_NO_RESET_GROUP_MAC: TextEdit
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `218`
+- Product: `MAC`
+- Source files: `218.JSON`, `218.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC238
+
+
+Setup
+
+1. Install Keyman build.
+
+
+
+
+Action
+
+1. Click on the TextEdit App icon from MAC.
+2. Verify that the TextEdit Application opens.
+3. Press `
+4. Verify it produces `
+5. Press the "fn"
+6. Type e
+7. Verify it produces è
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the MAC
+SUITE_KMX_PROCESSOR_COMPLIANT_GROUP_LINUX:
+
+
+
+---
+
+**TEST_220**
+
+LDML_PROCESSOR_NON_COMPLIANT_TEST_FRAME_KEY_RESET_MARKERS_GROUP_MAC: Chrome Browser
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `220`
+- Product: `MAC`
+- Source files: `220.JSON`, `220.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC250
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Chrome browser.
+
+
+
+
+Action
+
+1. Click on the Chrome browser icon from macOS Desktop.
+2. Verify that the Chrome browser opens.
+3. Navigate to the "www.google.com" page.
+4. Click in the search box.
+5. Type ^
+6. Verify it produces ^.
+7. Press the “right arrow”(->)
+8. Verify it produces e
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+2. Uninstall Chrome browser.
+
+
+
+---
+
+**TEST_223**
+
+LDML_PROCESSOR_NON_COMPLIANT_TEST_MODIFIER_TAP_NO_RESET_GROUP_MAC: Chrome Browser
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `223`
+- Product: `MAC`
+- Source files: `223.JSON`, `223.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC253
+
+
+Setup
+
+1. Install Keyman build.
+2. Install Chrome browser.
+
+
+
+
+Action
+
+1. Click on the Chrome browser icon from macOS Desktop.
+2. Verify that the Chrome browser opens.
+3. Navigate to the "www.google.com" page.
+4. Click in the search box.
+5. Press ^
+6. Verify it produces ^
+7. Press and release the CTRL
+8. Press the e
+9. Verify it produces ê
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the device.
+2. Uninstall Chrome browser.
+
+
+
+---
+
+**TEST_226**
+
+LDML_PROCESSOR_COMPLIANT_TEST_FRAME_KEY_RESET_NO_MARKERS_MAC: TextEdit
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `226`
+- Product: `MAC`
+- Source files: `226.JSON`, `226.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC266
+
+
+Setup
+
+1. Install Keyman build.
+2. Install TextEdit app.
+
+
+
+
+Action
+
+1. Click on the TextEdit App icon from macOS Desktop.
+2. Verify that the TextEdit Application opens.
+3. Press a
+4. Verify it produces a
+5. Press the "right arrow"(->)
+6. Press the SHIFT + 8
+7. Verify it produces “Star”
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the macOS
+2. Uninstall the TextEdit app.
+
+
+
+---
+
+**TEST_228**
+
+LDML_PROCESSOR_COMPLIANT_TEST_MODIFIER_TAP_NO_RESET_GROUP_MAC: TextEdit
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `228`
+- Product: `MAC`
+- Source files: `228.JSON`, `228.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC268
+
+
+Setup
+
+1. Install Keyman build.
+2. Install TextEdit app.
+
+
+
+
+Action
+
+1. Click on the TextEdit App icon from macOS Desktop.
+2. Verify that the TextEdit Application opens.
+3. Press ^
+4. Verify it produces ^
+5. Press and Release CTRL key.
+6. Type e
+7. Verify it produces ê
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the macOS
+2. Uninstall the TextEdit app.
+
+
+
+---
+
+**TEST_231**
+
+feat(mac): both option keys generate right alt if no left alt mapping #12458(TEST_RALT_KEYBOARD_WITH_OPTION_KEY_COMBOS)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `231`
+- Product: `MAC`
+- Source files: `231.JSON`, `231.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC286
+
+
+Setup
+
+1. Download the MacOS installer build from "state.keyman.com"
+2. Install Keyman build on the Sonoma or the latest macOS.
+
+
+
+
+Action
+
+1. Click the Keyman icon from the taskbar.
+2. Verify the Keyman menu opens.
+3. Select the "Configuration"
+4. Verify the "Keyman Configuration" dialog appears.
+5. Installed the "Armenian Mnemonic" keyboard by clicking the "Download Keyboard" button.
+6. Verify the "Armenian Mnemonic" keyboard appears on the "Keyman Configuration" dialog.
+7. Switch to the "Armenian Mnemonic" keyboard.
+8. Press the ALT + 9 on the left side.
+9. Verify this generates the subscript character '₉'
+10. Press the ALT + SHIFT + 9 on the left side.
+11. Verify that this generates the superscript character '⁹'
+12. Press the ALT + SHIFT + 9 on the right side.
+13. Verify that this generates the same superscript character '⁹'
+
+
+
+
+Cleanup
+
+1. Uninstall the Keyman build on the macOS.
+
+
+
+---
+
+**TEST_233**
+
+change(mac): remove 'Always show OSK' option #12355 (TEST_ALWAYS_SHOW_OPTION_IS_GONE)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `233`
+- Product: `MAC`
+- Source files: `233.JSON`, `233.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC288
+
+
+Setup
+
+1. Download the MacOS installer build from "state.keyman.com"
+2. Install Keyman build on the Sonoma or the latest macOS.
+
+
+
+
+Action
+
+1. Click the Keyman icon from the taskbar.
+2. Verify the Keyman menu opens.
+3. Select the "Configuration"
+4. Verify the "Keyman Configuration" dialog appears.
+5. Installed the "Khmer Angkor" keyboard by clicking the "Download Keyboard" button.
+6. Verify the "Khmer Angkor" keyboard appears on the "Keyman Configuration" dialog.
+7. Click on the "Options" tab.
+8. Verify the "Always show on-screen keyboard" checkbox is gone.
+
+
+
+
+Cleanup
+
+1. Uninstall the Keyman build on the macOS.
+
+
+
+---
+
+**TEST_236**
+
+change(mac): remove 'Always show OSK' option #12355(TEST_OSK_REMAINS_HIDDEN_WITH_KEYMAN_INACTIVE)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `236`
+- Product: `MAC`
+- Source files: `236.JSON`, `236.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC291
+
+
+Setup
+
+1. Download the MacOS installer build from "state.keyman.com"
+2. Install Keyman build on the Sonoma or the latest macOS.
+
+
+
+
+Action
+
+1. Click the Keyman icon from the taskbar.
+2. Verify the Keyman menu opens.
+3. Select the "On-Screen Keyboard"
+4. Verify the OSK appears.
+5. Change the keyboard from Keyman to Apple(U.S. Keyboard)
+6. Verify that the OSK appears.
+7. Open the "Text Editor" application.
+8. Type some text in the "Text Editor" application.
+9. Verify the text reflect it.
+10. Switch the application from "Text Editor" to "Stickes."
+11. Click on the app's menu and items.
+12. Verify the OSK does not flash when it is not inactive state.
+
+
+
+
+Cleanup
+
+1. Uninstall the Keyman build on the macOS.
+
+
+
+---
+
+**TEST_238**
+
+change(mac): remove 'Always show OSK' option #12355 (TEST_OSK_REMEMBERS_SIZE_AND_LOCATION_AFTER_RESTART)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `238`
+- Product: `MAC`
+- Source files: `238.JSON`, `238.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC293
+
+
+Setup
+
+1. Download the MacOS installer build from "state.keyman.com"
+2. Install Keyman build on the Sonoma or the latest macOS.
+
+
+
+
+Action
+
+1. Click the Keyman icon from the taskbar.
+2. Verify the Keyman menu opens.
+3. Select the "On-Screen Keyboard"
+4. Verify the OSK appears.
+5. Change the OSK size and move the OSK to 2nd monitor screen.
+6. Verify the OSK appears in a bigger size.
+7. Restart the machine.
+8. Login as a user.
+9. Switch to the keyman keyboard.
+10. Verify the OSK keyboard is change.
+11. Verify the OSK appears in the same bigger size and the OSK position appears in the same place earlier too.
+
+
+
+
+Cleanup
+
+1. Uninstall the Keyman build on the macOS.
+
+
+
+---
+
+**TEST_341**
+
+Handle PackageInfo section in kmp.inf file
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `341`
+- Product: `MAC`
+- Source files: `341.JSON`, `341.html`
+
+
+
+**Description**
+
+TC - fix(mac): handle PackageInfo section in kmp.inf file #13876
+
+
+Setup
+
+1. Download the MacOS installer build from "state.keyman.com"(Alpha version) or keyman.com (stable version)
+2. Install Keyman build on the Sonoma or the latest macOS.
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Open the Configuration dialog by clicking Keyman icon --> Configuration.
+3. Click the "Download Keyboard" button to open the "Keyman: Download Keyboard" dialog
+4. Verify that the "Keyman: Download Keyboard" dialog appears.
+5. Search for the “Sanskrit Unicode” keyboard in the search box.
+6. Verify that the “Sanskrit Unicode” results appeared.
+7. Install the “Sanskrit Unicode” keyboard.
+8. Verify that the “Download complete” pop-up window
+9. Click the "Done" button on the pop-up window.
+10. Verify that the "Package Information" dialog appears.
+11. Press “x” to exit "Package Information."
+12. Open the "Notes" app.
+13. Open a blank note.
+14. Select the “Sanskrit Unicode” keyboard by clicking the Keyman icon --> Sanskrit Unicode
+15. Enter some text in the note app using the "Sanskrit Unicode" keyboard.
+16. Verify that the "Sanskrit Unicode" keyboard appears in the configuration dialog.
+17. Verify that the "Sanskrit Unicode" letter appears in the note app.
+18. Close the keyman's configuration dialog.
+
+
+
+
+Cleanup
+
+1. Uninstall the Keyman build on macOS.
+
+
+
+---
+
diff --git a/docs/tests/acceptance/web.md b/docs/tests/acceptance/web.md
new file mode 100644
index 0000000000..e8ca5f6b7d
--- /dev/null
+++ b/docs/tests/acceptance/web.md
@@ -0,0 +1,3671 @@
+# Web Acceptance Tests
+
+**TEST_261**
+
+Test case for Baseline_Add_Sil_Ipa
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `261`
+- Product: `Web`
+- Source files: `261.JSON`, `261.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC162
+
+
+Setup
+
+1. Install Firefox in windows.
+2. Install Chrome in windows.
+3. Install Safari in macOS.
+4. Install Chrome in macOS.
+5. Install Firefox in macOS.
+6. Install Firefox in Linux OS.
+
+
+
+
+Action
+
+1. Open Firefox browser in Windows OS.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/433344:id/index.html' in the Search bar.
+3.Verify that the testing index page opens.
+4. Click 'View Keymanweb use samples' link button.
+5. Verify KeymanWeb Samples page opens.
+6. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Type ‘n >’ in the text input screen.
+9. Verify it produces ‘ŋ’
+10. Open Chrome browser in Windows OS.
+11. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/433344:id/index.html' in the Search bar.
+12.Verify that the testing index page opens.
+13. Click 'View Keymanweb use samples' link button.
+14. Verify KeymanWeb Samples page opens.
+15. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+16. Verify the corresponding KeymaWeb Sample page opens.
+17. Type ‘n >’ in the text input screen.
+18. Verify it produces ‘ŋ’
+19. Open Safari browser in macOS.
+20. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/433344:id/index.html' in the Search bar.
+21.Verify that the testing index page opens.
+22. Click 'View Keymanweb use samples' link button.
+23. Verify KeymanWeb Samples page opens.
+24. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+25. Verify the corresponding KeymaWeb Sample page opens.
+26. Type ‘n >’ in the text input screen.
+27. Verify it produces ‘ŋ’
+28. Open Chrome browser in macOS.
+29. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/433344:id/index.html' in the Search bar.
+30.Verify that the testing index page opens.
+31. Click 'View Keymanweb use samples' link button.
+32. Verify KeymanWeb Samples page opens.
+33. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+34. Verify the corresponding KeymaWeb Sample page opens.
+35. Type ‘n >’ in the text input screen.
+36. Verify it produces ‘ŋ’
+37. Open Firefox in macOS.
+38. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/433344:id/index.html' in the Search bar.
+39.Verify that the testing index page opens.
+40. Click 'View Keymanweb use samples' link button.
+41. Verify KeymanWeb Samples page opens.
+42. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+43. Verify the corresponding KeymaWeb Sample page opens.
+44. Type ‘n >’ in the text input screen.
+45. Verify it produces ‘ŋ’
+46. Open Firefox in Linux OS.
+47. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/433344:id/index.html' in the Search bar.
+48.Verify that the testing index page opens.
+49. Click 'View Keymanweb use samples' link button.
+50. Verify KeymanWeb Samples page opens.
+51. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+52. Verify the corresponding KeymaWeb Sample page opens.
+53. Type ‘n >’ in the text input screen.
+54. Verify it produces ‘ŋ’
+
+
+
+
+Cleanup
+
+1. Uninstall Firefox browser in Windows.
+2. Uninstall Chrome in Windows.
+3. Uninstall Safari in macOS.
+4. Uninstall Chrome in macOS.
+5. Uninstall Firefox in macOS.
+6. Uninstall Firefox in Linux OS.
+
+
+
+---
+
+**TEST_262**
+
+Test case for Baseline_Add_KM
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `262`
+- Product: `Web`
+- Source files: `262.JSON`, `262.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC163
+
+
+Setup
+
+1. Install Firefox in windows.
+2. Install Chrome in windows.
+3. Install Safari in macOS.
+4. Install Chrome in macOS.
+5. Install Firefox in macOS.
+6. Install Firefox in Linux OS.
+
+
+
+
+Action
+
+1. Open Firefox browser in Windows OS.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/433344:id/index.html' in the Search bar.
+3.Verify that the testing index page opens.
+4. Click 'View Keymanweb use samples' link button.
+5. Verify KeymanWeb Samples page opens.
+6. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Click ‘Add a keyboard by BCP-47 language code’ dropdown list.
+9. Select km keyboard.
+10. Verify that the Khmer Angkor keyboard is added and displayed on the Screen.
+11. Open Chrome browser in Windows OS.
+12. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+13.Verify that the testing index page opens.
+14. Click 'View Keymanweb use samples' link button.
+15. Verify KeymanWeb Samples page opens.
+16. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+17. Verify the corresponding KeymaWeb Sample page opens.
+18. Click ‘Add a keyboard by BCP-47 language code’ dropdown list.
+19. Select km keyboard.
+20. Verify that the Khmer Angkor keyboard is added and displayed on the Screen.
+21. Open Safari browser in macOS.
+22. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+23.Verify that the testing index page opens.
+24. Click 'View Keymanweb use samples' link button.
+25. Verify KeymanWeb Samples page opens.
+26. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+27. Verify the corresponding KeymaWeb Sample page opens.
+28. Click ‘Add a keyboard by BCP-47 language code’ dropdown list.
+29. Select km keyboard.
+30. Verify that the Khmer Angkor keyboard is added and displayed on the Screen.
+31. Open Chrome browser in macOS.
+32. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+33.Verify that the testing index page opens.
+34. Click 'View Keymanweb use samples' link button.
+35. Verify KeymanWeb Samples page opens.
+36. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+37. Verify the corresponding KeymaWeb Sample page opens.
+38. Click ‘Add a keyboard by BCP-47 language code’ dropdown list.
+39. Select km keyboard.
+40. Verify that the Khmer Angkor keyboard is added and displayed on the Screen.
+41. Open Firefox browser in macOS.
+42. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+43.Verify that the testing index page opens.
+44. Click 'View Keymanweb use samples' link button.
+45. Verify KeymanWeb Samples page opens.
+46. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+47. Verify the corresponding KeymaWeb Sample page opens.
+48. Click ‘Add a keyboard by BCP-47 language code’ dropdown list.
+49. Select km keyboard.
+50. Verify that the Khmer Angkor keyboard is added and displayed on the Screen.
+51. Open Firefox browser in Linux OS.
+52. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+53.Verify that the testing index page opens.
+54. Click 'View Keymanweb use samples' link button.
+55. Verify KeymanWeb Samples page opens.
+56. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+57. Verify the corresponding KeymaWeb Sample page opens.
+58. Click ‘Add a keyboard by BCP-47 language code’ dropdown list.
+59. Select km keyboard.
+60. Verify that the Khmer Angkor keyboard is added and displayed on the Screen.
+
+
+
+
+Cleanup
+
+1. Uninstall Firefox browser in Windows.
+2. Uninstall Chrome in Windows.
+3. Uninstall Safari in macOS.
+4. Uninstall Chrome in macOS.
+5. Uninstall Firefox in macOS.
+6. Uninstall Firefox in Linux OS.
+
+
+
+---
+
+**TEST_263**
+
+Test case for Baseline_Add_Khmer_Angkor
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `263`
+- Product: `Web`
+- Source files: `263.JSON`, `263.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC164
+
+
+Setup
+
+1. Install Firefox in windows.
+2. Install Chrome in windows.
+3. Install Safari in macOS.
+4. Install Chrome in macOS.
+5. Install Firefox in macOS.
+6. Install Firefox in Linux OS.
+
+
+
+
+Action
+
+1. Open Firefox browser in Windows OS.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3.Verify that the testing index page opens.
+4. Click 'View Keymanweb use samples' link button.
+5. Verify KeymanWeb Samples page opens.
+6. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Click ‘Add a keyboard by keyboard name’ dropdown list.
+9. Select khmer_angkor keyboard.
+10. Click the Add button.
+11. Verified that the Khmer_Angkor keyboard appears on the screen.
+12. Type Ctrl+Alt+B in the text input screen.
+13. It produces ឞ in the screen.
+14. Delete the character again.
+15. Type ‘ s u j r k’ using the (US) keyboard.
+16. It produces ស្រុក in the text input screen.
+17. Hit the Backspace key.
+18. It shows ស្រុ on the screen.
+19. Hit the Backspace key.
+20. It shows ស្រ in the screen.
+21. Hit the Backspace key.
+22. It shows ស on the screen.
+23. Hit the Backspace key.
+24. Verify it deletes the remaining letter on the screen.
+25. Open Chrome browser in Windows OS.
+22. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+23.Verify that the testing index page opens.
+24. Click 'View Keymanweb use samples' link button.
+25. Verify KeymanWeb Samples page opens.
+26. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+27. Verify the corresponding KeymaWeb Sample page opens.
+24. Click ‘Add a keyboard by keyboard name’ dropdown list.
+25. Select khmer_angkor keyboard.
+26. Click the Add button.
+27. Verified that the Khmer_Angkor keyboard appears on the screen.
+28. Type Ctrl+Alt+B in the text input screen.
+29. It produces ឞ in the screen.
+30. Delete the character again.
+31. Type ‘ s u j r k’ using the (US) keyboard.
+32. It produces ស្រុក in the text input screen.
+33. Hit the Backspace key.
+34. It shows ស្រុ on the screen.
+35. Hit the Backspace key.
+36. It shows ស្រ in the screen.
+37. Hit the Backspace key.
+38. It shows ស on the screen.
+39. Hit the Backspace key.
+40. Verify it deletes the remaining letter on the screen.
+41. Open Safari browser in macOS
+42. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+43.Verify that the testing index page opens.
+44. Click 'View Keymanweb use samples' link button.
+45. Verify KeymanWeb Samples page opens.
+46. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+47. Verify the corresponding KeymaWeb Sample page opens.
+48. Click ‘Add a keyboard by keyboard name’ dropdown list.
+49. Select khmer_angkor keyboard.
+50. Click the Add button.
+51. Verified that the Khmer_Angkor keyboard appears on the screen.
+52. Type Ctrl+Alt+B in the text input screen.
+53. It produces ឞ in the screen.
+54. Delete the character again.
+55. Type ‘ s u j r k’ using the (US) keyboard.
+56. It produces ស្រុក in the text input screen.
+57. Hit the Backspace key.
+58. It shows ស្រុ on the screen.
+59. Hit the Backspace key.
+60. It shows ស្រ in the screen.
+61. Hit the Backspace key.
+62. It shows ស on the screen.
+63. Hit the Backspace key.
+64. Verify it deletes the remaining letter on the screen.
+61. Open Chrome browser in macOS.
+62. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+63.Verify that the testing index page opens.
+64. Click 'View Keymanweb use samples' link button.
+65. Verify KeymanWeb Samples page opens.
+66. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+67. Verify the corresponding KeymaWeb Sample page opens.
+68. Click ‘Add a keyboard by keyboard name’ dropdown list.
+69. Select khmer_angkor keyboard.
+70. Click the Add button.
+71. Verified that the Khmer_Angkor keyboard appears on the screen.
+72. Type Ctrl+Alt+B in the text input screen.
+73. It produces ឞ in the screen.
+74. Delete the character again.
+75. Type ‘ s u j r k’ using the (US) keyboard.
+76. It produces ស្រុក in the text input screen.
+77. Hit the Backspace key.
+78. It shows ស្រុ on the screen.
+79. Hit the Backspace key.
+80. It shows ស្រ in the screen.
+81. Hit the Backspace key.
+82. It shows ស on the screen.
+83. Hit the Backspace key.
+84. Verify it deletes the remaining letter on the screen.
+85. Open Firefox browser in macOS.
+86. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+87.Verify that the testing index page opens.
+88. Click 'View Keymanweb use samples' link button.
+89. Verify KeymanWeb Samples page opens.
+90. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+91. Verify the corresponding KeymaWeb Sample page opens.
+92. Click ‘Add a keyboard by keyboard name’ dropdown list.
+93. Select khmer_angkor keyboard.
+94. Click the Add button.
+95. Verified that the Khmer_Angkor keyboard appears on the screen.
+96. Type Ctrl+Alt+B in the text input screen.
+97. It produces ឞ in the screen.
+98. Delete the character again.
+99. Type ‘ s u j r k’ using the (US) keyboard.
+100. It produces ស្រុក in the text input screen.
+101. Hit the Backspace key.
+102. It shows ស្រុ on the screen.
+103. Hit the Backspace key.
+104. It shows ស្រ in the screen.
+105. Hit the Backspace key.
+106. It shows ស on the screen.
+107. Hit the Backspace key.
+108. Verify it deletes the remaining letter on the screen.
+101. Open Firefox browser in Linux OS.
+102. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+103.Verify that the testing index page opens.
+104. Click 'View Keymanweb use samples' link button.
+105. Verify KeymanWeb Samples page opens.
+106. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+107. Verify the corresponding KeymaWeb Sample page opens.
+108. Click ‘Add a keyboard by keyboard name’ dropdown list.
+109. Select khmer_angkor keyboard.
+110. Click the Add button.
+111. Verified that the Khmer_Angkor keyboard appears on the screen.
+112. Type Ctrl+Alt+B in the text input screen.
+113. It produces ឞ in the screen.
+114. Delete the character again.
+115. Type ‘ s u j r k’ using the (US) keyboard.
+116. It produces ស្រុក in the text input screen.
+117. Hit the Backspace key.
+118. It shows ស្រុ on the screen.
+119. Hit the Backspace key.
+120. It shows ស្រ in the screen.
+121. Hit the Backspace key.
+122. It shows ស on the screen.
+123. Hit the Backspace key.
+124. Verify it deletes the remaining letter on the screen.
+
+
+
+
+Cleanup
+
+1. Uninstall Firefox browser in Windows.
+2. Uninstall Chrome in Windows.
+3. Uninstall Safari in macOS.
+4. Uninstall Chrome in macOS.
+5. Uninstall Firefox in macOS.
+6. Uninstall Firefox in Linux OS.
+
+
+
+---
+
+**TEST_264**
+
+Test case for Baseline_Add_Spanish
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `264`
+- Product: `Web`
+- Source files: `264.JSON`, `264.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC165
+
+
+Setup
+
+1. Install Firefox in windows.
+2. Install Chrome in windows.
+3. Install Safari in macOS.
+4. Install Chrome in macOS.
+5. Install Firefox in macOS.
+6. Install Firefox in Linux OS.
+
+
+
+
+Action
+
+1. Open Firefox browser in Windows OS.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3.Verify that the testing index page opens.
+4. Click 'View Keymanweb use samples' link button.
+5. Verify KeymanWeb Samples page opens.
+6. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Click ‘Add a keyboard by language name(s) section’ dropdown list.
+9. Select ‘spanish’.
+10. Click the Add button.
+11. Verify that a Spanish keyboard is added to the list.
+12. Open Chrome browser in Windows OS.
+13. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+14.Verify that the testing index page opens.
+15. Click 'View Keymanweb use samples' link button.
+16. Verify KeymanWeb Samples page opens.
+17. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+18. Verify the corresponding KeymaWeb Sample page opens.
+19. Click ‘Add a keyboard by language name(s) section’ dropdown list.
+20. Select ‘spanish’.
+21. Click the Add button.
+22. Verify that a Spanish keyboard is added to the list.
+23. Open Safari browser in macOS.
+24. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+25.Verify that the testing index page opens.
+26. Click 'View Keymanweb use samples' link button.
+27. Verify KeymanWeb Samples page opens.
+28. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+29. Verify the corresponding KeymaWeb Sample page opens.
+30. Click ‘Add a keyboard by language name(s) section’ dropdown list.
+31. Select ‘spanish’.
+32. Click the Add button.
+33. Verify that a Spanish keyboard is added to the list.
+34. Open Chrome browser in macOS.
+35. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+36.Verify that the testing index page opens.
+37. Click 'View Keymanweb use samples' link button.
+38. Verify KeymanWeb Samples page opens.
+39. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+40. Verify the corresponding KeymaWeb Sample page opens.
+41. Click ‘Add a keyboard by language name(s) section’ dropdown list.
+42. Select ‘spanish’.
+43. Click the Add button.
+44. Verify that a Spanish keyboard is added to the list.
+45. Open Firefox browser in macOS.
+46. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+47.Verify that the testing index page opens.
+48. Click 'View Keymanweb use samples' link button.
+49. Verify KeymanWeb Samples page opens.
+50. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+51. Verify the corresponding KeymaWeb Sample page opens.
+52. Click ‘Add a keyboard by language name(s) section’ dropdown list.
+53. Select ‘spanish’.
+54. Click the Add button.
+55. Verify that a Spanish keyboard is added to the list.
+56. Open Firefox browser in Linux OS.
+57. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+58.Verify that the testing index page opens.
+59. Click 'View Keymanweb use samples' link button.
+60. Verify KeymanWeb Samples page opens.
+61. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+62. Verify the corresponding KeymaWeb Sample page opens.
+63. Click ‘Add a keyboard by language name(s) section’ dropdown list.
+64. Select ‘spanish’.
+65. Click the Add button.
+66. Verify that a Spanish keyboard is added to the list.
+
+
+
+
+Cleanup
+
+1. Uninstall Firefox browser in Windows.
+2. Uninstall Chrome in Windows.
+3. Uninstall Safari in macOS.
+4. Uninstall Chrome in macOS.
+5. Uninstall Firefox in macOS.
+6. Uninstall Firefox in Linux OS.
+
+
+
+---
+
+**TEST_265**
+
+Test case for Basline_Swedish
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `265`
+- Product: `Web`
+- Source files: `265.JSON`, `265.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC166
+
+
+Setup
+
+1. Install Firefox in windows.
+2. Install Chrome in windows.
+3. Install Safari in macOS.
+4. Install Chrome in macOS.
+5. Install Firefox in macOS.
+6. Install Firefox in Linux OS.
+
+
+
+
+Action
+
+1. Open Firefox browser in Windows OS.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3.Verify that the testing index page opens.
+4. Click 'View Keymanweb use samples' link button.
+5. Verify KeymanWeb Samples page opens.
+6. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Type ‘ e in the text input screen.
+9. It produces é on the screen.
+10. Type o \ e on the screen.
+11. It produces œ on the screen.
+12. Open Chrome browser in Windows OS.
+13. Enter ‘web/samples/minified.html’ in the Search bar.
+14. Verify that the minified page opens in Firefox.
+15. Type ‘ e in the text input screen.
+16. It produces é on the screen.
+17. Type o \ e on the screen.
+18. It produces œ on the screen.
+
+
+
+
+Cleanup
+
+1. Uninstall Firefox browser in Windows.
+2. Uninstall Chrome in Windows.
+3. Uninstall Safari in macOS.
+4. Uninstall Chrome in macOS.
+5. Uninstall Firefox in macOS.
+6. Uninstall Firefox in Linux OS.
+
+
+
+---
+
+**TEST_266**
+
+Test case for Text Selection_Tests (Windows)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `266`
+- Product: `Web`
+- Source files: `266.JSON`, `266.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC167
+
+
+Setup
+
+1. Install Firefox in windows.
+2. Install Chrome in windows.
+3. Install web_context_tests keyboard.
+4. Run on both INPUT and TEXTAREA elements.
+5. Press Ctrl+F5 to reload the page between tests.
+
+
+
+
+Action
+
+1. Open Firefox browser in Windows OS.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3. Verify that the testing index page opens.
+4. Click 'View Keymaweb website-oriented manual test pages' link button.
+5. Verify KeymanWeb Samples page opens.
+6. Click 'Test unminified Keymanweb' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Select 'web_context_test' keyboard.
+9. Type a b c x in the TextArea.
+10. Select bc.
+11. Type q.
+12. Verify that the output shows ‘aqx’.
+13. Press Ctrl+F5 keys.
+14. Verify that the page reloads the page.
+15. Type a b c x.
+16. Select bc.
+17. Type p.
+18. Verify that the output shows ‘aqx’.
+19. Type a b c d.
+20. Press Ctrl+F5 keys.
+21. Verify that the page reloads the page.
+22. Type a b c d.
+23. Verify that the output shows !.
+24. Press Ctrl+F5 keys.
+25. Type a b c x.
+26. Select the x character.
+27. Type d.
+28. Verify that the final letter should be changed and the output should be abcd.
+29. Press Ctrl+F5 keys.
+30. Type a b c x.
+31. Select the x character.
+32. Press Backspace key to delete the character.
+33. Type d.
+34. Verify that the final letter should be !.
+35. Press Ctrl+F5 keys.
+36. Type a b c x.
+37. Select the x character.
+38. Type y.
+39. Press Backspace key.
+40. Type d.
+41. Verify that the final letter should be !.
+42. Press Ctrl+F5 keys.
+43. Type x a b c x.
+44. Select the abc characters.
+45. Type d.
+46. Verify that the final letter should be xdx.
+47. Open Chrome browser in Windows OS.
+48.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+49. Verify that the testing index page opens.
+50. Click 'View Keymaweb website-oriented manual test pages' link button.
+51. Verify KeymanWeb Samples page opens.
+52. Click 'Test unminified Keymanweb' link button.
+53. Verify the corresponding KeymaWeb Sample page opens.
+54. Select 'web_context_test' keyboard.
+55. Type a b c x in the TextArea.
+56. Select bc.
+57. Type q.
+58. Verify that the output shows ‘aqx’.
+59. Press Ctrl+F5 keys.
+60. Verify that the page reloads the page.
+61. Type a b c x.
+62. Select bc.
+63. Type p.
+64. Verify that the output shows ‘aqx’.
+65. Type a b c d.
+66. Press Ctrl+F5 keys.
+67. Verify that the page reloads the page.
+68. Type a b c d.
+69. Verify that the output shows !.
+70. Press Ctrl+F5 keys.
+71. Type a b c x.
+72. Select the x character.
+73. Type d.
+74. Verify that the final letter should be changed and the output should be abcd.
+75. Press Ctrl+F5 keys.
+76. Type a b c x.
+77. Select the x character.
+78. Press Backspace key to delete the character.
+79. Type d.
+80. Verify that the final letter should be !.
+81. Press Ctrl+F5 keys.
+82. Type a b c x.
+83. Select the x character.
+84. Type y.
+85. Press Backspace key.
+86. Type d.
+87. Verify that the final letter should be !.
+88. Press Ctrl+F5 keys.
+89. Type x a b c x.
+90. Select the abc characters.
+91. Type d.
+92. Verify that the final letter should be xdx.
+
+
+
+
+Cleanup
+
+1. Uninstall Firefox browser.
+2. Uninstall Chrome browser.
+3. Uninstall web_context_tests keyboard.
+
+
+**TEST_267**
+
+Test case for Text Selection_Tests (macOS)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `267`
+- Product: `Web`
+- Source files: `267.JSON`, `267.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC168
+
+
+Setup
+
+1. Install Safari in macOS
+2. Install Chrome in macOS
+3. Install Firefox in macOS
+4. Install web_context_tests keyboard.
+5. Run on both INPUT and TEXTAREA elements.
+6. Press Ctrl+F5 to reload the page between tests.
+
+
+
+
+Action
+
+1. Open Safari browser in macOS.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3. Verify that the testing index page opens.
+4. Click 'View Keymaweb website-oriented manual test pages' link button.
+5. Verify KeymanWeb Samples page opens.
+6. Click 'Test unminified Keymanweb' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Select 'web_context_test' keyboard.
+9. Type a b c x in the TextArea.
+10. Select bc.
+11. Type q.
+12. Verify that the output shows ‘aqx’.
+13. Press Ctrl+F5 keys.
+14. Verify that the page reloads the page.
+15. Type a b c x.
+16. Select bc.
+17. Type p.
+18. Verify that the output shows ‘aqx’.
+19. Type a b c d.
+20. Press Ctrl+F5 keys.
+21. Verify that the page reloads the page.
+22. Type a b c d.
+23. Verify that the output shows !.
+24. Press Ctrl+F5 keys.
+25. Type a b c x.
+26. Select the x character.
+27. Type d.
+28. Verify that the final letter should be changed and the output should be abcd.
+29. Press Ctrl+F5 keys.
+30. Type a b c x.
+31. Select the x character.
+32. Press Backspace key to delete the character.
+33. Type d.
+34. Verify that the final letter should be !.
+35. Press Ctrl+F5 keys.
+36. Type a b c x.
+37. Select the x character.
+38. Type y.
+39. Press Backspace key.
+40. Type d.
+41. Verify that the final letter should be !.
+42. Press Ctrl+F5 keys.
+43. Type x a b c x.
+44. Select the abc characters.
+45. Type d.
+46. Verify that the final letter should be xdx.
+47. Open Chrome browser in macOS.
+48. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+49. Verify that the testing index page opens.
+50. Click 'View Keymaweb website-oriented manual test pages' link button.
+51. Verify KeymanWeb Samples page opens.
+52. Click 'Test unminified Keymanweb' link button.
+53. Verify the corresponding KeymaWeb Sample page opens.
+54. Select 'web_context_test' keyboard.
+55. Type a b c x in the TextArea.
+56. Select bc.
+57. Type q.
+58. Verify that the output shows ‘aqx’.
+59. Press Ctrl+F5 keys.
+60. Verify that the page reloads the page.
+61. Type a b c x.
+62. Select bc.
+63. Type p.
+64. Verify that the output shows ‘aqx’.
+65. Type a b c d.
+66. Press Ctrl+F5 keys.
+67. Verify that the page reloads the page.
+68. Type a b c d.
+69. Verify that the output shows !.
+70. Press Ctrl+F5 keys.
+71. Type a b c x.
+72. Select the x character.
+73. Type d.
+74. Verify that the final letter should be changed and the output should be abcd.
+75. Press Ctrl+F5 keys.
+76. Type a b c x.
+77. Select the x character.
+78. Press Backspace key to delete the character.
+79. Type d.
+80. Verify that the final letter should be !.
+81. Press Ctrl+F5 keys.
+82. Type a b c x.
+83. Select the x character.
+84. Type y.
+85. Press Backspace key.
+86. Type d.
+87. Verify that the final letter should be !.
+88. Press Ctrl+F5 keys.
+89. Type x a b c x.
+90. Select the abc characters.
+91. Type d.
+92. Verify that the final letter should be xdx.
+93. Open Firefox browser in macOS.
+94. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+95. Verify that the testing index page opens.
+96. Click 'View Keymaweb website-oriented manual test pages' link button.
+97. Verify KeymanWeb Samples page opens.
+98. Click 'Test unminified Keymanweb' link button.
+99. Verify the corresponding KeymaWeb Sample page opens.
+100. Select 'web_context_test' keyboard.
+101. Type a b c x in the TextArea.
+102. Select bc.
+103. Type q.
+104. Verify that the output shows ‘aqx’.
+105. Press Ctrl+F5 keys.
+106. Verify that the page reloads the page.
+107. Type a b c x.
+108. Select bc.
+109. Type p.
+110. Verify that the output shows ‘aqx’.
+111. Type a b c d.
+112. Press Ctrl+F5 keys.
+113. Verify that the page reloads the page.
+114. Type a b c d.
+115. Verify that the output shows !.
+116. Press Ctrl+F5 keys.
+117. Type a b c x.
+118. Select the x character.
+119. Type d.
+120. Verify that the final letter should be changed and the output should be abcd.
+121. Press Ctrl+F5 keys.
+122. Type a b c x.
+123. Select the x character.
+124. Press Backspace key to delete the character.
+125. Type d.
+126. Verify that the final letter should be !.
+127. Press Ctrl+F5 keys.
+128. Type a b c x.
+129. Select the x character.
+130. Type y.
+131. Press Backspace key.
+132. Type d.
+133. Verify that the final letter should be !.
+134. Press Ctrl+F5 keys.
+135. Type x a b c x.
+136. Select the abc characters.
+137. Type d.
+138. Verify that the final letter should be xdx.
+
+
+
+
+Cleanup
+
+1. Uninstall Safari browser.
+2. Uninstall Chrome browser.
+3. Uninstall Firefox browser.
+4. Uninstall web_context_tests keyboard.
+
+
+
+---
+
+**TEST_268**
+
+Test case for Text Selection_Tests (LinuxOS)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `268`
+- Product: `Web`
+- Source files: `268.JSON`, `268.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC169
+
+
+Setup
+
+1. Install Firefox in Linux OS.
+2. Install web_context_tests keyboard.
+
+
+
+
+Action
+
+1. Open Firefox browser in Linux OS.
+2.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3. Verify that the testing index page opens.
+4. Click 'View Keymaweb website-oriented manual test pages' link button.
+5. Verify KeymanWeb Samples page opens.
+6. Click 'Test unminified Keymanweb' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Select 'web_context_test' keyboard.
+9. Type a b c x in the TextArea.
+10. Select bc.
+11. Type q.
+12. Verify that the output shows ‘aqx’.
+13. Press Ctrl+F5 keys.
+14. Verify that the page reloads the page.
+15. Type a b c x.
+16. Select bc.
+17. Type p.
+18. Verify that the output shows ‘aqx’.
+19. Type a b c d.
+20. Press Ctrl+F5 keys.
+21. Verify that the page reloads the page.
+22. Type a b c d.
+23. Verify that the output shows !.
+24. Press Ctrl+F5 keys.
+25. Type a b c x.
+26. Select the x character.
+27. Type d.
+28. Verify that the final letter should be changed and the output should be abcd.
+29. Press Ctrl+F5 keys.
+30. Type a b c x.
+31. Select the x character.
+32. Press Backspace key to delete the character.
+33. Type d.
+34. Verify that the final letter should be !.
+35. Press Ctrl+F5 keys.
+36. Type a b c x.
+37. Select the x character.
+38. Type y.
+39. Press Backspace key.
+40. Type d.
+41. Verify that the final letter should be !.
+42. Press Ctrl+F5 keys.
+43. Type x a b c x.
+44. Select the abc characters.
+45. Type d.
+46. Verify that the final letter should be xdx.
+
+
+
+
+Cleanup
+
+1. Uninstall Firefox browser.
+2. Uninstall web_context_tests keyboard.
+
+
+
+---
+
+**TEST_269**
+
+Test case for Element Attachment Tests
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `269`
+- Product: `Web`
+- Source files: `269.JSON`, `269.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC170
+
+
+Setup
+
+1. Install Firefox in windows.
+2. Install Chrome in windows.
+3. Install Safari in macOS.
+4. Install Chrome in macOS.
+5. Install Firefox in macOS.
+6. Install Firefox in Linux OS.
+
+
+
+
+Action
+
+1. Open Firefox browser in Windows.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3. Verify that the testing index page opens.
+4. Click 'Tests the new Attachment/Enablement API functionality' link button.
+5. Verify KeymanWeb Samples - Attachment API Testing page opens.
+6. Verify there are 2 radio buttons namely auto and manual appear one by one on the page.
+7. Enable ‘auto’ attachment mode radio button.
+8. Verify that it automatically attaches to each dynamically-added control.
+9. Enable ‘’manual’ attachment mode radio button.
+10. Verify that manual attachment mode results in a page with no KMW-activated controls.
+11. Verify that the KeymanWeb is properly attached to and detaches from each relevant type of control with the page’s API-interface controls.
+10. Open Chrome browser in Windows.
+11. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+12. Verify that the testing index page opens.
+13. Click 'Tests the new Attachment/Enablement API functionality' link button.
+14. Verify KeymanWeb Samples - Attachment API Testing page opens.
+15. Verify there are 2 radio buttons namely auto and manual appear one by one on the page.
+16. Enable ‘auto’ attachment mode radio button.
+17. Verify that it automatically attaches to each dynamically-added control.
+18. Enable ‘’manual’ attachment mode radio button.
+19. Verify that manual attachment mode results in a page with no KMW-activated controls.
+20. Verify that the KeymanWeb is properly attached to and detaches from each relevant type of control with the page’s API-interface controls.
+21. Open Safari in macOS.
+22. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+23. Verify that the testing index page opens.
+24. Click 'Tests the new Attachment/Enablement API functionality' link button.
+25. Verify KeymanWeb Samples - Attachment API Testing page opens.
+26. Verify there are 2 radio buttons namely auto and manual appear one by one on the page.
+27. Enable ‘auto’ attachment mode radio button.
+28. Verify that it automatically attaches to each dynamically-added control.
+29. Enable ‘’manual’ attachment mode radio button.
+30. Verify that manual attachment mode results in a page with no KMW-activated controls.
+31. Verify that the KeymanWeb is properly attached to and detaches from each relevant type of control with the page’s API-interface controls.
+32. Open Chrome browser in macOS.
+33. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+34 Verify that the testing index page opens.
+35. Click 'Tests the new Attachment/Enablement API functionality' link button.
+36. Verify KeymanWeb Samples - Attachment API Testing page opens.
+37. Verify there are 2 radio buttons namely auto and manual appear one by one on the page.
+38. Enable ‘auto’ attachment mode radio button.
+39. Verify that it automatically attaches to each dynamically-added control.
+40. Enable ‘’manual’ attachment mode radio button.
+41. Verify that manual attachment mode results in a page with no KMW-activated controls.
+42. Verify that the KeymanWeb is properly attached to and detaches from each relevant type of control with the page’s API-interface controls.
+43. Open Firefox browser in macOS.
+44. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+45. Verify that the testing index page opens.
+46. Click 'Tests the new Attachment/Enablement API functionality' link button.
+47. Verify KeymanWeb Samples - Attachment API Testing page opens.
+48. Verify there are 2 radio buttons namely auto and manual appear one by one on the page.
+49. Enable ‘auto’ attachment mode radio button.
+50. Verify that it automatically attaches to each dynamically-added control.
+51. Enable ‘’manual’ attachment mode radio button.
+52. Verify that manual attachment mode results in a page with no KMW-activated controls.
+53. Verify that the KeymanWeb is properly attached to and detaches from each relevant type of control with the page’s API-interface controls.
+54. Open Firefox browser in Linux OS.
+55. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+56. Verify that the testing index page opens.
+57. Click 'Tests the new Attachment/Enablement API functionality' link button.
+58. Verify KeymanWeb Samples - Attachment API Testing page opens.
+59. Verify there are 2 radio buttons namely auto and manual appear one by one on the page.
+60. Enable ‘auto’ attachment mode radio button.
+61. Verify that it automatically attaches to each dynamically-added control.
+62. Enable ‘’manual’ attachment mode radio button.
+63. Verify that manual attachment mode results in a page with no KMW-activated controls.
+64. Verify that the KeymanWeb is properly attached to and detaches from each relevant type of control with the page’s API-interface controls.
+Clean Steps:
+1. Uninstall Firefox browser in Windows.
+2. Uninstall Chrome in Windows.
+3. Uninstall Safari in macOS.
+4. Uninstall Chrome in macOS.
+5. Uninstall Firefox in macOS.
+6. Uninstall Firefox in Linux OS.
+
+
+
+
+Cleanup
+
+No steps recorded.
+
+
+
+---
+
+**TEST_270**
+
+Test case for Normal_Use
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `270`
+- Product: `Web`
+- Source files: `270.JSON`, `270.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC171
+
+
+Setup
+
+1. Install Firefox in windows.
+2. Install Chrome in windows.
+3. Install Safari in macOS.
+4. Install Chrome in macOS.
+5. Install Firefox in macOS.
+6. Install Firefox in Linux OS.
+
+
+
+
+Action
+
+1. Open Firefox in windows OS.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3. Verify that the testing index page opens.
+4. Click 'Tests the new Attachment/Enablement API functionality' link button.
+5. Verify KeymanWeb Samples - Attachment API Testing page opens.
+6. Click the “Create Inputs” button one time.
+7. Click / touch the new page element.
+8. Verify the On Screen Keyboard should display.
+7. Type “K” using OSK.
+8. Type “L” using OSK.
+9. Verify that the OSK keys should produce their expected output.
+11. Click / touch a blank area of the page.
+12. Verify that the OSK should automatically hide.
+13. Open Chrome in windows OS.
+14.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+15. Verify that the testing index page opens.
+16. Click 'Tests the new Attachment/Enablement API functionality' link button.
+17. Verify KeymanWeb Samples - Attachment API Testing page opens.
+18. Click the “Create Inputs” button one time.
+19. Click / touch the new page element.
+20. Verify the On Screen Keyboard should display.
+21. Type “K” using OSK.
+22. Type “L” using OSK.
+23. Verify that the OSK keys should produce their expected output.
+24. Click / touch a blank area of the page.
+25. Verify that the OSK should automatically hide.
+26. Open Safari browser macOS.
+27. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+28. Verify that the testing index page opens.
+29. Click 'Tests the new Attachment/Enablement API functionality' link button.
+30. Verify KeymanWeb Samples - Attachment API Testing page opens.
+31. Click the “Create Inputs” button one time.
+32. Click / touch the new page element.
+33. Verify the On Screen Keyboard should display.
+34. Type “K” using OSK.
+35. Type “L” using OSK.
+36. Verify that the OSK keys should produce their expected output.
+37. Click / touch a blank area of the page.
+38. Verify that the OSK should automatically hide.
+39. Open Chrome browser in macOS.
+40. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+41. Verify that the testing index page opens.
+42. Click 'Tests the new Attachment/Enablement API functionality' link button.
+43. Verify KeymanWeb Samples - Attachment API Testing page opens.
+44. Click the “Create Inputs” button one time.
+45. Click / touch the new page element.
+46. Verify the On Screen Keyboard should display.
+47. Type “K” using OSK.
+48. Type “L” using OSK.
+49. Verify that the OSK keys should produce their expected output.
+50. Click / touch a blank area of the page.
+51. Verify that the OSK should automatically hide.
+52. Open Firefox browser macOS.
+53. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+54. Verify that the testing index page opens.
+55. Click 'Tests the new Attachment/Enablement API functionality' link button.
+56. Verify KeymanWeb Samples - Attachment API Testing page opens.
+57. Click the “Create Inputs” button one time.
+58. Click / touch the new page element.
+59. Verify the On Screen Keyboard should display.
+60. Type “K” using OSK.
+61. Type “L” using OSK.
+62. Verify that the OSK keys should produce their expected output.
+63. Click / touch a blank area of the page.
+64. Verify that the OSK should automatically hide.
+65. Open Firefox browser in Linux OS.
+66. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+Verify that the testing index page opens.
+67. Click 'Tests the new Attachment/Enablement API functionality' link button.
+68. Verify KeymanWeb Samples - Attachment API Testing page opens.
+69. Click the “Create Inputs” button one time.
+70. Click / touch the new page element.
+71. Verify the On Screen Keyboard should display.
+72. Type “K” using OSK.
+73. Type “L” using OSK.
+74. Verify that the OSK keys should produce their expected output.
+75. Click / touch a blank area of the page.
+76. Verify that the OSK should automatically hide.
+
+
+
+
+Cleanup
+
+1. Uninstall Firefox browser in Windows.
+2. Uninstall Chrome in Windows.
+3. Uninstall Safari in macOS.
+4. Uninstall Chrome in macOS.
+5. Uninstall Firefox in macOS.
+6. Uninstall Firefox in Linux OS.
+
+
+
+---
+
+**TEST_271**
+
+Test case for Element_Hopping
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `271`
+- Product: `Web`
+- Source files: `271.JSON`, `271.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC172
+
+
+Setup
+
+1. Install Firefox in windows.
+2. Install Chrome in windows.
+3. Install Safari in macOS.
+4. Install Chrome in macOS.
+5. Install Firefox in macOS.
+6. Install Firefox in Linux OS.
+
+
+
+
+Action
+
+1. Open Firefox browser in Windows OS.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3.Verify that the testing index page opens.
+4.Click 'Tests the new Attachment/Enablement API functionality' link button.
+5. Verify KeymanWeb Samples - Attachment API Testing page opens.
+6. Click the ‘Create Inputs’ button one time.
+7. Click the ‘Create Textarea’ button one time.
+8. Click / touch the first of the new page elements.
+9. Verify that the OSK should display.
+10. Click / touch the other page element.
+11. Verify that the OSK should remain visible.
+12. Click / touch the first element again.
+13. Verify that the OSK should remain visible.
+14. Click / touch a blank area of the page.
+15. Verify that the OSK should automatically hide.
+16. Open Chrome browser in Windows OS.
+17. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+18. Verify that the testing index page opens.
+19. Click 'Tests the new Attachment/Enablement API functionality' link button.
+20. Verify KeymanWeb Samples - Attachment API Testing page opens.
+21. Click the ‘Create Inputs’ button one time.
+22. Click the ‘Create Textarea’ button one time.
+23. Click / touch the first of the new page elements.
+24. Verify that the OSK should display.
+25. Click / touch the other page element.
+26. Verify that the OSK should remain visible.
+27. Click / touch the first element again.
+28. Verify that the OSK should remain visible.
+29. Click / touch a blank area of the page.
+30. Verify that the OSK should automatically hide.
+31. Open Safari browser in macOS.
+32. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+33. Verify that the testing index page opens.
+34. Click 'Tests the new Attachment/Enablement API functionality' link button.
+35. Verify KeymanWeb Samples - Attachment API Testing page opens.
+36. Click the ‘Create Inputs’ button one time.
+37. Click the ‘Create Textarea’ button one time.
+38. Click / touch the first of the new page elements.
+39. Verify that the OSK should display.
+40. Click / touch the other page element.
+41. Verify that the OSK should remain visible.
+42. Click / touch the first element again.
+43. Verify that the OSK should remain visible.
+44. Click / touch a blank area of the page.
+45. Verify that the OSK should automatically hide.
+46. Open Chrome browser in macOS.
+47. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+48. Verify that the testing index page opens.
+49. Click 'Tests the new Attachment/Enablement API functionality' link button.
+50. Verify KeymanWeb Samples - Attachment API Testing page opens.
+51. Click the ‘Create Inputs’ button one time.
+52. Click the ‘Create Textarea’ button one time.
+53. Click / touch the first of the new page elements.
+54. Verify that the OSK should display.
+55. Click / touch the other page element.
+56. Verify that the OSK should remain visible.
+57. Click / touch the first element again.
+58. Verify that the OSK should remain visible.
+59. Click / touch a blank area of the page.
+60. Verify that the OSK should automatically hide.
+61. Open Firefox in macOS.
+62. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+63. Verify that the testing index page opens.
+64. Click 'Tests the new Attachment/Enablement API functionality' link button.
+65. Verify KeymanWeb Samples - Attachment API Testing page opens.
+66. Click the ‘Create Inputs’ button one time.
+67. Click the ‘Create Textarea’ button one time.
+68. Click / touch the first of the new page elements.
+69. Verify that the OSK should display.
+70. Click / touch the other page element.
+71. Verify that the OSK should remain visible.
+72. Click / touch the first element again.
+73. Verify that the OSK should remain visible.
+74. Click / touch a blank area of the page.
+75. Verify that the OSK should automatically hide.
+76. Open Firefox in Linux OS.
+77. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+78. Verify that the testing index page opens.
+79. Click 'Tests the new Attachment/Enablement API functionality' link button.
+80. Verify KeymanWeb Samples - Attachment API Testing page opens.
+81. Click the ‘Create Inputs’ button one time.
+82. Click the ‘Create Textarea’ button one time.
+83. Click / touch the first of the new page elements.
+84. Verify that the OSK should display.
+85. Click / touch the other page element.
+86. Verify that the OSK should remain visible.
+87. Click / touch the first element again.
+88. Verify that the OSK should remain visible.
+89. Click / touch a blank area of the page.
+90. Verify that the OSK should automatically hide.
+
+
+
+
+Cleanup
+
+1. Uninstall Firefox browser in Windows.
+2. Uninstall Chrome in Windows.
+3. Uninstall Safari in macOS.
+4. Uninstall Chrome in macOS.
+5. Uninstall Firefox in macOS.
+6. Uninstall Firefox in Linux OS.
+
+
+
+---
+
+**TEST_272**
+
+Test case for Specific_Keyboards
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `272`
+- Product: `Web`
+- Source files: `272.JSON`, `272.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC173
+
+
+Setup
+
+1. Install Firefox in windows.
+2. Install Chrome in windows.
+3. Install Safari in macOS.
+4. Install Chrome in macOS.
+5. Install Firefox in macOS.
+6. Install Firefox in Linux OS.
+
+
+
+
+Action
+
+1. Open Firefox browser in Windows OS.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+Verify that the testing index page opens.
+Click 'Tests the new Attachment/Enablement API functionality' link button.
+Verify KeymanWeb Samples - Attachment API Testing page opens.
+4. Click the ‘Create Inputs’ button three times.
+5. Click / touch Dynamic area #0.
+6. Click the element’s “Set to Dzongkha’ button.
+7. Change the keyboard to French.
+8. Click Dynamic area #1 ‘s ‘Set to Dzongkha button.
+9. Click Dynamic area #1.
+10. Verify the Dzongkha keyboard should be displayed.
+11. Click Dynamic area #2.
+12. Change the keyboard to Lao.
+13. Click Dynamic area#0.
+14. Verify that the French keyboard should be displayed.
+15. Click Dynamic area #2.
+16. Verify that the Lao keyboard should be displayed.
+17. Open Chrome browser in Windows OS.
+18.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+19. Verify that the testing index page opens.
+20. Click 'Tests the new Attachment/Enablement API functionality' link button.
+21. Verify KeymanWeb Samples - Attachment API Testing page opens.
+22. Click the ‘Create Inputs’ button three times.
+23. Click / touch Dynamic area #0.
+24. Click the element’s “Set to Dzongkha’ button.
+25. Change the keyboard to French.
+26. Click Dynamic area #1 ‘s ‘Set to Dzongkha button.
+27. Click Dynamic area #1.
+28. Verify the Dzongkha keyboard should be displayed.
+29. Click Dynamic area #2.
+30. Change the keyboard to Lao.
+31. Click Dynamic area#0.
+32. Verify that the French keyboard should be displayed.
+33. Click Dynamic area #2.
+34. Verify that the Lao keyboard should be displayed.
+35. Open Safari browser in macOS.
+36. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+37. Verify that the testing index page opens.
+38. Click 'Tests the new Attachment/Enablement API functionality' link button.
+39. Verify KeymanWeb Samples - Attachment API Testing page opens.
+40. Click the ‘Create Inputs’ button three times.
+41. Click / touch Dynamic area #0.
+42. Click the element’s “Set to Dzongkha’ button.
+43. Change the keyboard to French.
+44. Click Dynamic area #1 ‘s ‘Set to Dzongkha button.
+45. Click Dynamic area #1.
+46. Verify the Dzongkha keyboard should be displayed.
+47. Click Dynamic area #2.
+48. Change the keyboard to Lao.
+49. Click Dynamic area#0.
+50. Verify that the French keyboard should be displayed.
+51. Click Dynamic area #2.
+52. Verify that the Lao keyboard should be displayed.
+53. Open Safari browser in macOS.
+54. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+55. Verify that the testing index page opens.
+56. Click 'Tests the new Attachment/Enablement API functionality' link button.
+57. Verify KeymanWeb Samples - Attachment API Testing page opens.
+58. Click the ‘Create Inputs’ button three times.
+59. Click / touch Dynamic area #0.
+60. Click the element’s “Set to Dzongkha’ button.
+61. Change the keyboard to French.
+62. Click Dynamic area #1 ‘s ‘Set to Dzongkha button.
+63. Click Dynamic area #1.
+64. Verify the Dzongkha keyboard should be displayed.
+65. Click Dynamic area #2.
+66. Change the keyboard to Lao.
+67. Click Dynamic area#0.
+68. Verify that the French keyboard should be displayed.
+69. Click Dynamic area #2.
+70. Verify that the Lao keyboard should be displayed.
+71. Open Chrome browser in macOS.
+72. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+73. Verify that the testing index page opens.
+74. Click 'Tests the new Attachment/Enablement API functionality' link button.
+75. Verify KeymanWeb Samples - Attachment API Testing page opens.
+76. Click the ‘Create Inputs’ button three times.
+77. Click / touch Dynamic area #0.
+78. Click the element’s “Set to Dzongkha’ button.
+79. Change the keyboard to French.
+80. Click Dynamic area #1 ‘s ‘Set to Dzongkha button.
+81. Click Dynamic area #1.
+82. Verify the Dzongkha keyboard should be displayed.
+83. Click Dynamic area #2.
+84. Change the keyboard to Lao.
+85. Click Dynamic area#0.
+86. Verify that the French keyboard should be displayed.
+87. Click Dynamic area #2.
+88. Verify that the Lao keyboard should be displayed.
+89. Open Firefox browser in macOS.
+90.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+91. Verify that the testing index page opens.
+92. Click 'Tests the new Attachment/Enablement API functionality' link button.
+93. Verify KeymanWeb Samples - Attachment API Testing page opens.
+94. Click the ‘Create Inputs’ button three times.
+95. Click / touch Dynamic area #0.
+96. Click the element’s “Set to Dzongkha’ button.
+97. Change the keyboard to French.
+98. Click Dynamic area #1 ‘s ‘Set to Dzongkha button.
+99. Click Dynamic area #1.
+100. Verify the Dzongkha keyboard should be displayed.
+101. Click Dynamic area #2.
+102. Change the keyboard to Lao.
+103. Click Dynamic area#0.
+104. Verify that the French keyboard should be displayed.
+105. Click Dynamic area #2.
+106. Verify that the Lao keyboard should be displayed.
+107. Open Firefox browser in Linux OS.
+108. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+109. Verify that the testing index page opens.
+110. Click 'Tests the new Attachment/Enablement API functionality' link button.
+111. Verify KeymanWeb Samples - Attachment API Testing page opens.
+112. Click the ‘Create Inputs’ button three times.
+113. Click / touch Dynamic area #0.
+114. Click the element’s “Set to Dzongkha’ button.
+115. Change the keyboard to French.
+116. Click Dynamic area #1 ‘s ‘Set to Dzongkha button.
+117. Click Dynamic area #1.
+118. Verify the Dzongkha keyboard should be displayed.
+119. Click Dynamic area #2.
+120. Change the keyboard to Lao.
+121. Click Dynamic area#0.
+122. Verify that the French keyboard should be displayed.
+123. Click Dynamic area #2.
+124. Verify that the Lao keyboard should be displayed.
+
+
+
+
+Cleanup
+
+1. Uninstall Firefox browser in Windows.
+2. Uninstall Chrome in Windows.
+3. Uninstall Safari in macOS.
+4. Uninstall Chrome in macOS.
+5. Uninstall Firefox in macOS.
+6. Uninstall Firefox in Linux OS.
+
+
+
+---
+
+**TEST_273**
+
+Test case for Japanese_Typing
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `273`
+- Product: `Web`
+- Source files: `273.JSON`, `273.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC174
+
+
+Setup
+
+1. Install Firefox in windows.
+2. Install Chrome in windows.
+3. Install Safari in macOS.
+4. Install Chrome in macOS.
+5. Install Firefox in macOS.
+6. Install Firefox in Linux OS.
+7. Run on both INPUT and TEXTAREA elements.
+8. Press Ctrl+F5 to reload the page between tests.
+
+
+
+
+Action
+
+1. Open Firefox browser in Windows OS.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3. Verify that the testing index page opens.
+4. Click 'View Keymaweb website-oriented manual test pages' link button.
+5. Verify KeymanWeb Samples page opens.
+6. Click 'Test unminified Keymanweb' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Click the text box against the label name “Add a keyboard by keyboard name”.
+9. Type japanese.
+10. Click the Add button.
+11. Select the Japanese keyboard.
+12. Verify the OSK should change the shape notably.
+13. Type a.
+14. Verify a “picker” displaying a few options should display.
+15. Type 2.
+16. Verify the second option should replace the context.
+17. Open Chrome browser in Windows OS.
+18.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+19. Verify that the testing index page opens.
+20. Click 'View Keymaweb website-oriented manual test pages' link button.
+21. Verify KeymanWeb Samples page opens.
+22. Click 'Test unminified Keymanweb' link button.
+23. Verify the corresponding KeymaWeb Sample page opens.
+24. Click the text box against the label name “Add a keyboard by keyboard name”.
+25. Type japanese.
+26. Click the Add button.
+27. Select the Japanese keyboard.
+28. Verify the OSK should change the shape notably.
+29. Type a.
+30. Verify a “picker” displaying a few options should display.
+31. Type 2.
+32. Verify the second option should replace the context.
+33. Open Safari browser in macOS.
+34.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+35. Verify that the testing index page opens.
+36. Click 'View Keymaweb website-oriented manual test pages' link button.
+37. Verify KeymanWeb Samples page opens.
+38. Click 'Test unminified Keymanweb' link button.
+39. Verify the corresponding KeymaWeb Sample page opens.
+40. Click the text box against the label name “Add a keyboard by keyboard name”.
+41. Type japanese.
+42. Click the Add button.
+43. Select the Japanese keyboard.
+44. Verify the OSK should change the shape notably.
+45. Type a.
+46. Verify a “picker” displaying a few options should display.
+47. Type 2.
+48. Verify the second option should replace the context.
+49. Open Chrome browser in macOS.
+50. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+51. Verify that the testing index page opens.
+52. Click 'View Keymaweb website-oriented manual test pages' link button.
+53. Verify KeymanWeb Samples page opens.
+54. Click 'Test unminified Keymanweb' link button.
+55. Verify the corresponding KeymaWeb Sample page opens.
+56. Click the text box against the label name “Add a keyboard by keyboard name”.
+57. Type japanese.
+58. Click the Add button.
+59. Select the Japanese keyboard.
+60. Verify the OSK should change the shape notably.
+61. Type a.
+62. Verify a “picker” displaying a few options should display.
+63. Type 2.
+64. Verify the second option should replace the context.
+66. Open Firefox in macOS.
+67. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+68. Verify that the testing index page opens.
+69. Click 'View Keymaweb website-oriented manual test pages' link button.
+70. Verify KeymanWeb Samples page opens.
+71. Click 'Test unminified Keymanweb' link button.
+72. Verify the corresponding KeymaWeb Sample page opens.
+73. Click the text box against the label name “Add a keyboard by keyboard name”.
+74. Type japanese.
+75. Click the Add button.
+76. Select the Japanese keyboard.
+77. Verify the OSK should change the shape notably.
+78. Type a.
+79. Verify a “picker” displaying a few options should display.
+80. Type 2.
+81. Verify the second option should replace the context.
+82. Open Firefox in Linux OS.
+83.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+84. Verify that the testing index page opens.
+85. Click 'View Keymaweb website-oriented manual test pages' link button.
+86. Verify KeymanWeb Samples page opens.
+87. Click 'Test unminified Keymanweb' link button.
+88. Verify the corresponding KeymaWeb Sample page opens.
+89. Click the text box against the label name “Add a keyboard by keyboard name”.
+90. Type japanese.
+91. Click the Add button.
+92. Select the Japanese keyboard.
+93. Verify the OSK should change the shape notably.
+94. Type a.
+95. Verify a “picker” displaying a few options should display.
+96. Type 2.
+97. Verify the second option should replace the context.
+
+
+
+
+Cleanup
+
+1. Uninstall Firefox browser in Windows.
+2. Uninstall Chrome in Windows.
+3. Uninstall Safari in macOS.
+4. Uninstall Chrome in macOS.
+5. Uninstall Firefox in macOS.
+6. Uninstall Firefox in Linux OS.
+
+
+
+---
+
+**TEST_274**
+
+Test case for Japanese_Focus
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `274`
+- Product: `Web`
+- Source files: `274.JSON`, `274.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC175
+
+
+Setup
+
+1. Install Firefox in windows.
+2. Install Chrome in windows.
+3. Install Safari in macOS.
+4. Install Chrome in macOS.
+5. Install Firefox in macOS.
+6. Install Firefox in Linux OS.
+
+
+
+
+Action
+
+1. Open Firefox browser in Windows OS.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3.Verify that the testing index page opens.
+4. Click 'View Keymaweb website-oriented manual test pages' link button.
+5. Verify KeymanWeb Samples page opens.
+6.Click 'Test unminified Keymanweb' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Type 'japanese' under "Add a keyboard by keyboard name" text box.
+9. Click Add button.
+10. Select Japanese keyboard.
+11. Click the text box against the label name “Add a keyboard by keyboard name”.
+12. Type japanese.
+13. Click the Add button.
+14. Select the Japanese keyboard.
+15. Verify the OSK should change the shape notably.
+16. Type a.
+17. Verify a “picker” displaying a few options should display.
+18. Type 2.
+19. Verify the second option should replace the context.
+20. Select the page’s textarea element.
+21. Verify that the OSK’s title bar should appear on the screen.
+22. Click a blank area on the page.
+23. Verify that the OSK should automatically hide and the caret should disappear from the textarea.
+24. Select the page’s input field (the second editable control).
+25. Verify that the OSK should reappear under the newly-selected control.
+26. Select the page’s textarea element again.
+27. Verify that the OSK should remain visible.
+28. Verify the caret should move from the input control to the textarea control.
+29. Open Chrome browser in Windows OS.
+30. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+31. Verify that the testing index page opens.
+32. Click 'View Keymaweb website-oriented manual test pages' link button.
+33. Verify KeymanWeb Samples page opens.
+34. Click 'Test unminified Keymanweb' link button.
+35. Verify the corresponding KeymaWeb Sample page opens.
+36. Type 'japanese' under "Add a keyboard by keyboard name" text box.
+37. Click Add button.
+38. Select Japanese keyboard.
+39. Click the text box against the label name “Add a keyboard by keyboard name”.
+40. Type japanese.
+41. Click the Add button.
+42. Select the Japanese keyboard.
+43. Verify the OSK should change the shape notably.
+44. Type a.
+45. Verify a “picker” displaying a few options should display.
+46. Type 2.
+47. Verify the second option should replace the context.
+48. Select the page’s textarea element.
+49. Verify that the OSK’s title bar should appear on the screen.
+50. Click a blank area on the page.
+51. Verify that the OSK should automatically hide and the caret should disappear from the textarea.
+52. Select the page’s input field (the second editable control).
+53. Verify that the OSK should reappear under the newly-selected control.
+54. Select the page’s textarea element again.
+55. Verify that the OSK should remain visible.
+56. Verify the caret should move from the input control to the textarea control.
+57. Open Safari browser in macOS.
+58. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+59. Verify that the testing index page opens.
+60. Click 'View Keymaweb website-oriented manual test pages' link button.
+61. Verify KeymanWeb Samples page opens.
+62. Click 'Test unminified Keymanweb' link button.
+63. Verify the corresponding KeymaWeb Sample page opens.
+64. Type 'japanese' under "Add a keyboard by keyboard name" text box.
+65. Click Add button.
+66. Select Japanese keyboard.
+67. Click the text box against the label name “Add a keyboard by keyboard name”.
+68. Type japanese.
+69. Click the Add button.
+70. Select the Japanese keyboard.
+71. Verify the OSK should change the shape notably.
+72. Type a.
+73. Verify a “picker” displaying a few options should display.
+74. Type 2.
+75. Verify the second option should replace the context.
+76. Select the page’s textarea element.
+77. Verify that the OSK’s title bar should appear on the screen.
+78. Click a blank area on the page.
+79. Verify that the OSK should automatically hide and the caret should disappear from the textarea.
+80. Select the page’s input field (the second editable control).
+81. Verify that the OSK should reappear under the newly-selected control.
+82. Select the page’s textarea element again.
+83. Verify that the OSK should remain visible.
+84. Verify the caret should move from the input control to the textarea control.
+85. Open Chrome browser in macOS.
+86.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+87. Verify that the testing index page opens.
+88. Click 'View Keymaweb website-oriented manual test pages' link button.
+89. Verify KeymanWeb Samples page opens.
+90. Click 'Test unminified Keymanweb' link button.
+91. Verify the corresponding KeymaWeb Sample page opens.
+92. Type 'japanese' under "Add a keyboard by keyboard name" text box.
+93. Click Add button.
+94. Select Japanese keyboard.
+95. Click the text box against the label name “Add a keyboard by keyboard name”.
+96. Type japanese.
+97. Click the Add button.
+98. Select the Japanese keyboard.
+99. Verify the OSK should change the shape notably.
+100. Type a.
+101. Verify a “picker” displaying a few options should display.
+102. Type 2.
+103. Verify the second option should replace the context.
+104. Select the page’s textarea element.
+105. Verify that the OSK’s title bar should appear on the screen.
+106. Click a blank area on the page.
+107. Verify that the OSK should automatically hide and the caret should disappear from the textarea.
+108. Select the page’s input field (the second editable control).
+109. Verify that the OSK should reappear under the newly-selected control.
+110. Select the page’s textarea element again.
+111. Verify that the OSK should remain visible.
+112. Verify the caret should move from the input control to the textarea control.
+113. Open Firefox browser in macOS.
+114. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+115. Verify that the testing index page opens.
+116. Click 'View Keymaweb website-oriented manual test pages' link button.
+117. Verify KeymanWeb Samples page opens.
+118. Click 'Test unminified Keymanweb' link button.
+119. Verify the corresponding KeymaWeb Sample page opens.
+120. Type 'japanese' under "Add a keyboard by keyboard name" text box.
+121. Click Add button.
+122. Select Japanese keyboard.
+123. Click the text box against the label name “Add a keyboard by keyboard name”.
+124. Type japanese.
+125. Click the Add button.
+126. Select the Japanese keyboard.
+127. Verify the OSK should change the shape notably.
+128. Type a.
+129. Verify a “picker” displaying a few options should display.
+130. Type 2.
+131. Verify the second option should replace the context.
+132. Select the page’s textarea element.
+133. Verify that the OSK’s title bar should appear on the screen.
+134. Click a blank area on the page.
+135. Verify that the OSK should automatically hide and the caret should disappear from the textarea.
+136. Select the page’s input field (the second editable control).
+137. Verify that the OSK should reappear under the newly-selected control.
+138. Select the page’s textarea element again.
+139. Verify that the OSK should remain visible.
+140. Verify the caret should move from the input control to the textarea control.
+141. Open Firefox browser in Linux OS.
+142. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+143. Verify that the testing index page opens.
+144. Click 'View Keymaweb website-oriented manual test pages' link button.
+145. Verify KeymanWeb Samples page opens.
+146. Click 'Test unminified Keymanweb' link button.
+147. Verify the corresponding KeymaWeb Sample page opens.
+148. Type 'japanese' under "Add a keyboard by keyboard name" text box.
+149. Click Add button.
+150. Select Japanese keyboard.
+151. Click the text box against the label name “Add a keyboard by keyboard name”.
+152. Type japanese.
+153. Click the Add button.
+154. Select the Japanese keyboard.
+155. Verify the OSK should change the shape notably.
+156. Type a.
+157. Verify a “picker” displaying a few options should display.
+158. Type 2.
+159. Verify the second option should replace the context.
+160. Select the page’s textarea element.
+161. Verify that the OSK’s title bar should appear on the screen.
+162. Click a blank area on the page.
+163. Verify that the OSK should automatically hide and the caret should disappear from the textarea.
+164. Select the page’s input field (the second editable control).
+165. Verify that the OSK should reappear under the newly-selected control.
+166. Select the page’s textarea element again.
+167. Verify that the OSK should remain visible.
+168. Verify the caret should move from the input control to the textarea control.
+
+
+
+
+Cleanup
+
+1. Uninstall Firefox browser in Windows.
+2. Uninstall Chrome in Windows.
+3. Uninstall Safari in macOS.
+4. Uninstall Chrome in macOS.
+5. Uninstall Firefox in macOS.
+6. Uninstall Firefox in Linux OS.
+
+
+
+---
+
+**TEST_275**
+
+Test case for Baseline_Add_SIL_IPA (Touch / Hardware Platforms)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `275`
+- Product: `Web`
+- Source files: `275.JSON`, `275.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC176
+
+
+Setup
+
+1. Install Chrome browser in an Android Mobile (Touch)
+2. Install Chrome browser in an Android Mobile attached with Physical Keyboard. (Hardware)
+3. Install Safari browser in an iPhone Mobile (Touch)
+4. Install Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Install Safari browser in an iPad Tablet (Touch)
+6. Install Safari browser in an iPad Tablet attached with Physical Keyboard. (Hardware)
+
+
+
+
+Action
+
+1. Click the Chrome browser icon from the Android Mobile.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3. Verify that the testing index page opens.
+4. Click 'View Keymanweb use samples' link button.
+5. Verify KeymanWeb Samples page opens.
+6. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Click sil_ipa from the ‘Add a keyboard by keyboard name’ section.
+9. Click the Add button.
+10. Verify that the sil_ipa keyboard appears on the Screen.
+11. Long-press ‘n’ key, while keeping the finger down, move on the long-press options ‘ŋ‘ so it's highlighted, and release.
+12. Verify that the letter ‘ŋ’ appears on the text input screen.
+13. Click the Chrome browser icon from the Android Mobile with the physical keyboard.
+14. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+15. Verify that the testing index page opens.
+16. Click 'View Keymanweb use samples' link button.
+17. Verify KeymanWeb Samples page opens.
+18. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+19. Verify the corresponding KeymaWeb Sample page opens.
+20. Click sil_ipa from the ‘Add a keyboard by keyboard name’ section.
+21. Click the Add button.
+22. Verify that the sil_ipa keyboard appears on the Screen.
+23. Type n letter from physical keyboard.
+24. Type > symbol from physical keyboard.
+25. Verify that the letter ‘ŋ’ appears on the text input screen.
+26. Click the Safari browser in iPhone Mobile.
+27. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+28. Verify that the testing index page opens.
+29. Click 'View Keymanweb use samples' link button.
+30. Verify KeymanWeb Samples page opens.
+31. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+32. Verify the corresponding KeymaWeb Sample page opens.
+33. Click sil_ipa from the ‘Add a keyboard by keyboard name’ section.
+34. Click the Add button.
+35. Verify that the sil_ipa keyboard appears on the Screen.
+36. Long-press ‘n’ key, while keeping the finger down, move on the long-press options ‘ŋ‘ so it's highlighted, and release.
+37. Verify that the letter ‘ŋ’ appears on the text input screen.
+38. Click the Safari browser in iPhone Mobile with a physical keyboard.
+39. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+40. Verify that the testing index page opens.
+41. Click 'View Keymanweb use samples' link button.
+42. Verify KeymanWeb Samples page opens.
+43. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+44. Verify the corresponding KeymaWeb Sample page opens.
+45. Click sil_ipa from the ‘Add a keyboard by keyboard name’ section.
+46. Click the Add button.
+47. Verify that the sil_ipa keyboard appears on the Screen.
+48. Long-press ‘n’ key, while keeping the finger down, move on the long-press options ‘ŋ‘ so it's highlighted, and release.
+49. Verify that the letter ‘ŋ’ appears on the text input screen.
+50. Click the Safari browser in iPad Tablet.
+51. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+52.Verify that the testing index page opens.
+53. Click 'View Keymanweb use samples' link button.
+54. Verify KeymanWeb Samples page opens.
+55. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+56. Verify the corresponding KeymaWeb Sample page opens.
+57. Click sil_ipa from the ‘Add a keyboard by keyboard name’ section.
+58. Click the Add button.
+59. Verify that the sil_ipa keyboard appears on the Screen.
+60. Long-press ‘n’ key, while keeping the finger down, move on the long-press options ‘ŋ‘ so it's highlighted, and release.
+61. Verify that the letter ‘ŋ’ appears on the text input screen.
+62. Click the Safari browser in the iPad Tablet with a physical keyboard.
+63.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+64. Verify that the testing index page opens.
+65. Click 'View Keymanweb use samples' link button.
+66. Verify KeymanWeb Samples page opens.
+67. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+68. Verify the corresponding KeymaWeb Sample page opens.
+69. Click sil_ipa from the ‘Add a keyboard by keyboard name’ section.
+70. Click the Add button.
+71. Verify that the sil_ipa keyboard appears on the Screen.
+72. Long-press ‘n’ key, while keeping the finger down, move on the long-press options ‘ŋ‘ so it's highlighted, and release.
+73. Verify that the letter ‘ŋ’ appears on the text input screen.
+
+
+
+
+Cleanup
+
+1. Uninstall Chrome browser in an Android Mobile. (Touch)
+2. Uninstall Chrome browser in an Android Mobile attached with Physical Keyboard.(Hardware)
+3. Uninstall Safari browser in an iPhone Mobile.
+4. Uninstall Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Uninstall Safari browser in an iPad Tablet.
+6. Uninstall Safari browser in an iPad Tablet with Physical Keyboard.
+
+
+
+---
+
+**TEST_276**
+
+Test case for Baseline_Add_KM (Touch / Hardware Platforms),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `276`
+- Product: `Web`
+- Source files: `276.JSON`, `276.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC177
+
+
+Setup
+
+1. Install Chrome browser in an Android Mobile (Touch)
+2. Install Chrome browser in an Android Mobile attached with Physical Keyboard. (Hardware)
+3. Install Safari browser in an iPhone Mobile (Touch)
+4. Install Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Install Safari browser in an iPad Tablet (Touch)
+6. Install Safari browser in an iPad Tablet attached with Physical Keyboard. (Hardware)
+
+
+
+
+Action
+
+1. Click the Chrome browser icon from the Android Mobile.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3. Verify that the testing index page opens.
+4. Click 'View Keymanweb use samples' link button.
+5. Verify KeymanWeb Samples page opens.
+6. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Click km from the ‘Add a keyboard by BCP-47 language code’ section.
+9. Click the Add button.
+10. Verify that the khmer_angkor keyboard should be added and appear on the Screen.
+11. Click the Chrome browser in Android Mobile attached with a physical keyboard.
+12. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+13. Verify that the testing index page opens.
+14. Click 'View Keymanweb use samples' link button.
+15. Verify KeymanWeb Samples page opens.
+16. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+17. Verify the corresponding KeymaWeb Sample page opens.
+18. Click km from the ‘Add a keyboard by BCP-47 language code’ section.
+19. Click the Add button.
+20. Verify that the khmer_angkor keyboard should be added and appear on the Screen.
+21. Click Safari browser in an iPhone Mobile.
+22. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+23. Verify that the testing index page opens.
+24. Click 'View Keymanweb use samples' link button.
+25. Verify KeymanWeb Samples page opens.
+26. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+27. Verify the corresponding KeymaWeb Sample page opens.
+28. Click km from the ‘Add a keyboard by BCP-47 language code’ section.
+29. Click the Add button.
+30. Verify that the khmer_angkor keyboard should be added and appear on the Screen.
+31. Click Safari browser in an iPhone Mobile with a physical keyboard.
+32. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+33. Verify that the testing index page opens.
+34. Click 'View Keymanweb use samples' link button.
+35. Verify KeymanWeb Samples page opens.
+36. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+37. Verify the corresponding KeymaWeb Sample page opens.
+38. Click km from the ‘Add a keyboard by BCP-47 language code’ section.
+39. Click the Add button.
+40. Verify that the khmer_angkor keyboard should be added and appear on the Screen.
+41. Click Safari browser in an iPad Tablet.
+42. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+43. Verify that the testing index page opens.
+44. Click 'View Keymanweb use samples' link button.
+45. Verify KeymanWeb Samples page opens.
+46. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+47. Verify the corresponding KeymaWeb Sample page opens.
+48. Click km from the ‘Add a keyboard by BCP-47 language code’ section.
+49. Click the Add button.
+50. Verify that the khmer_angkor keyboard should be added and appear on the Screen.
+51. Click Safari browser in an iPad Tablet with a physical keyboard.
+52. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+53. Verify that the testing index page opens.
+54. Click 'View Keymanweb use samples' link button.
+55. Verify KeymanWeb Samples page opens.
+56. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+57. Verify the corresponding KeymaWeb Sample page opens.
+58. Click km from the ‘Add a keyboard by BCP-47 language code’ section.
+59. Click the Add button.
+60. Verify that the khmer_angkor keyboard should be added and appear on the Screen.
+
+
+
+
+Cleanup
+
+1. Uninstall Chrome browser in Android Mobile. (Touch)
+2. Uninstall Chrome browser in Android Mobile attached with Physical Keyboard.(Hardware)
+3. Uninstall Safari browser in an iPhone Mobile.
+4. Uninstall Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Uninstall Safari browser in an iPad Tablet.
+6. Uninstall Safari browser in an iPad Tablet with Physical Keyboard.
+
+
+
+---
+
+**TEST_277**
+
+Test case for Baseline_Add_Khmer_Angkor (Touch / Hardware Platforms)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `277`
+- Product: `Web`
+- Source files: `277.JSON`, `277.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC178
+
+
+Setup
+
+1. Install Chrome browser in an Android Mobile (Touch)
+2. Install Chrome browser in an Android Mobile attached with Physical Keyboard. (Hardware)
+3. Install Safari browser in an iPhone Mobile (Touch)
+4. Install Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Install Safari browser in an iPad Tablet (Touch)
+6. Install Safari browser in an iPad Tablet attached with Physical Keyboard. (Hardware)
+
+
+
+
+Action
+
+1. Click the Chrome browser icon from the Android Mobile.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3. Verify that the testing index page opens.
+4. Click 'View Keymanweb use samples' link button.
+5. Verify KeymanWeb Samples page opens.
+6. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Click khmer_angkor from the ‘Add a keyboard by keyboard name’ section.
+9. Click the Add button.
+10. Verify that the Khmer Angkor keyboard appears on the Screen.
+11. Type the following sequences on touch screen keyboard:
+12. ស
+13. ុ
+14. ្រ (subkey of រ)
+15. ក
+16. Verify that the output produces ស្រុក.
+17. Hit Backspace key. (as this is a reorder (keyboard) rule test)
+18. Verify that it shows ស្រុ
+19. Hit Backspace key.
+20. Verify that it shows ស្រ
+21. Hit Backspace key.
+22. Verify that it shows ស
+23. Hit Backspace key.
+24. Verify that it shows an empty text area.
+25. Click the Chrome browser icon from the Android mobile attached with a physical keyboard.
+26. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+27. Verify that the testing index page opens.
+28. Click 'View Keymanweb use samples' link button.
+29. Verify KeymanWeb Samples page opens.
+30. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+31. Verify the corresponding KeymaWeb Sample page opens.
+32. Click khmer_angkor from the ‘Add a keyboard by keyboard name’ section.
+33. Click the Add button.
+34. Verify that the Khmer Angkor keyboard appears on the Screen.
+35. Type the following (US) keys in the following sequences:
+36. Type s
+37. Type u
+38. Type j
+39. Type r
+40. Type k
+41. Verify that the output produces ស្រុក.
+42. Hit Backspace key. (as this is a reorder (keyboard) rule test)
+43. Verify that it shows ស្រុ
+44. Hit Backspace key.
+45. Verify that it shows ស្រ
+46. Hit Backspace key.
+47. Verify that it shows ស
+48. Hit Backspace key.
+49. Verify that it shows an empty text area.
+50. Click the Safari browser in an iPhone Mobile.
+51.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+52. Verify that the testing index page opens.
+53. Click 'View Keymanweb use samples' link button.
+54. Verify KeymanWeb Samples page opens.
+55. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+56. Verify the corresponding KeymaWeb Sample page opens.
+57. Click khmer_angkor from the ‘Add a keyboard by keyboard name’ section.
+58. Click the Add button.
+59. Verify that the Khmer Angkor keyboard appears on the Screen.
+60. Type the following sequences on touch screen keyboard:
+61. ស
+62. ុ
+63. ្រ (subkey of រ)
+64. ក
+65. Verify that the output produces ស្រុក.
+66. Hit Backspace key. (as this is a reorder (keyboard) rule test)
+67. Verify that it shows ស្រុ
+68. Hit Backspace key.
+69. Verify that it shows ស្រ
+70. Hit Backspace key.
+71. Verify that it shows ស
+72. Hit Backspace key.
+73. Verify that it shows an empty text area.
+74. Click the Safari browser in an iPhone Mobile attached to a physical keyboard.
+75. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+76. Verify that the testing index page opens.
+77. Click 'View Keymanweb use samples' link button.
+78. Verify KeymanWeb Samples page opens.
+79. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+80. Verify the corresponding KeymaWeb Sample page opens.
+81. Click khmer_angkor from the ‘Add a keyboard by keyboard name’ section.
+82. Click the Add button.
+83. Verify that the Khmer Angkor keyboard appears on the Screen.
+84. Type the following (US) keys in the following sequences:
+85. Type s
+86. Type u
+87. Type j
+88. Type r
+89. Type k
+90. Verify that the output produces ស្រុក.
+91. Hit Backspace key. (as this is a reorder (keyboard) rule test)
+92. Verify that it shows ស្រុ
+93. Hit Backspace key.
+94. Verify that it shows ស្រ
+95. Hit Backspace key.
+96. Verify that it shows ស
+97. Hit Backspace key.
+98. Verify that it shows an empty text area.
+99. Click Safari browser on an iPad device.
+100. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+101. Verify that the testing index page opens.
+102. Click 'View Keymanweb use samples' link button.
+103. Verify KeymanWeb Samples page opens.
+104. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+105. Verify the corresponding KeymaWeb Sample page opens.
+106. Click khmer_angkor from the ‘Add a keyboard by keyboard name’ section.
+107. Click the Add button.
+108. Verify that the Khmer Angkor keyboard appears on the Screen.
+109. Type the following sequences on touch screen keyboard:
+110. ស
+111. ុ
+112. ្រ (subkey of រ)
+113. ក
+114. Verify that the output produces ស្រុក.
+115. Hit Backspace key. (as this is a reorder (keyboard) rule test)
+116. Verify that it shows ស្រុ
+117. Hit Backspace key.
+118. Verify that it shows ស្រ
+119. Hit Backspace key.
+120. Verify that it shows ស
+121. Hit Backspace key.
+122. Verify that it shows an empty text area.
+123. Click Safari browser on an iPad device attached to a physical keyboard.
+124. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+125. Verify that the testing index page opens.
+126. Click 'View Keymanweb use samples' link button.
+127. Verify KeymanWeb Samples page opens.
+128. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+129. Verify the corresponding KeymanWeb Sample page opens.
+130. Click khmer_angkor from the ‘Add a keyboard by keyboard name’ section.
+131. Click the Add button.
+132. Verify that the Khmer Angkor keyboard appears on the Screen.
+133. Type the following (US) keys in the following sequences:
+134. Type s
+135. Type u
+136. Type j
+137. Type r
+138. Type k
+139. Verify that the output produces ស្រុក.
+140. Hit Backspace key. (as this is a reorder (keyboard) rule test)
+141. Verify that it shows ស្រុ
+142. Hit Backspace key.
+143. Verify that it shows ស្រ
+144. Hit Backspace key.
+145. Verify that it shows ស
+146. Hit Backspace key.
+147. Verify that it shows an empty text area.
+
+
+
+
+Cleanup
+
+1. Uninstall Chrome browser in Android Mobile. (Touch)
+2. Uninstall Chrome browser in Android Mobile attached with Physical Keyboard.(Hardware)
+3. Uninstall Safari browser in an iPhone Mobile.
+4. Uninstall Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Uninstall Safari browser in an iPad Tablet.
+6. Uninstall Safari browser in an iPad Tablet with Physical Keyboard.
+
+
+
+---
+
+**TEST_278**
+
+Test case for Baseline_Add_Spanish (Touch / Hardware Platforms),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `278`
+- Product: `Web`
+- Source files: `278.JSON`, `278.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC179
+
+
+Setup
+
+1. Install Chrome browser in an Android Mobile (Touch)
+2. Install Chrome browser in an Android Mobile attached with Physical Keyboard. (Hardware)
+3. Install Safari browser in an iPhone Mobile (Touch)
+4. Install Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Install Safari browser in an iPad Tablet (Touch)
+6. Install Safari browser in an iPad Tablet attached with Physical Keyboard. (Hardware)
+
+
+
+
+Action
+
+1. Click the Chrome browser icon from the Android Mobile.
+2. Click the Chrome browser icon from the Android Mobile.
+3. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+4. Verify that the testing index page opens.
+5. Click 'View Keymanweb use samples' link button.
+6. Verify KeymanWeb Samples page opens.
+7. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+8. Verify the corresponding KeymaWeb Sample page opens.
+9. Click spanish from the ‘Add a keyboard by language name(s)’ section.
+10. Click the Add button.
+11. Verify that the Spanish keyboard is added to the list.
+12. Click the Chrome browser in Android Mobile attached with a physical keyboard.
+13. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+14. Verify that the testing index page opens.
+15. Click 'View Keymanweb use samples' link button.
+16. Verify KeymanWeb Samples page opens.
+17. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+18. Verify the corresponding KeymaWeb Sample page opens.
+19. Click spanish from the ‘Add a keyboard by language name(s)’ section.
+20. Click the Add button.
+21. Verify that the Spanish keyboard is added to the list.
+22. Click Safari browser in an iPhone Mobile.
+23.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+24. Verify that the testing index page opens.
+25. Click 'View Keymanweb use samples' link button.
+26. Verify KeymanWeb Samples page opens.
+27. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+28. Verify the corresponding KeymaWeb Sample page opens.
+29. Click spanish from the ‘Add a keyboard by language name(s)’ section.
+30. Click the Add button.
+31. Verify that the Spanish keyboard is added to the list.
+32. Click Safari browser in an iPhone mobile attached with a physical keyboard.
+33. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+34. Verify that the testing index page opens.
+35. Click 'View Keymanweb use samples' link button.
+36. Verify KeymanWeb Samples page opens.
+37. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+38. Verify the corresponding KeymaWeb Sample page opens.
+39. Click spanish from the ‘Add a keyboard by language name(s)’ section.
+40. Click the Add button.
+41. Verify that the Spanish keyboard is added to the list.
+42. Click Safari browser in an iPad Tablet.
+43. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+44. Verify that the testing index page opens.
+45. Click 'View Keymanweb use samples' link button.
+46. Verify KeymanWeb Samples page opens.
+47. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+48. Verify the corresponding KeymaWeb Sample page opens.
+49. Click spanish from the ‘Add a keyboard by language name(s)’ section.
+50. Click the Add button.
+51. Verify that the Spanish keyboard is added to the list.
+52. Click Safari browser in an iPad Tablet attached with a physical keyboard.
+53. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+54. Verify that the testing index page opens.
+55. Click 'View Keymanweb use samples' link button.
+56. Verify KeymanWeb Samples page opens.
+57. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+58. Verify the corresponding KeymaWeb Sample page opens.
+59. Click spanish from the ‘Add a keyboard by language name(s)’ section.
+60. Click the Add button.
+61. Verify that the Spanish keyboard is added to the list.
+
+
+
+
+Cleanup
+
+1. Uninstall Chrome browser in Android Mobile. (Touch)
+2. Uninstall Chrome browser in Android Mobile attached with Physical Keyboard.(Hardware)
+3. Uninstall Safari browser in an iPhone Mobile.
+4. Uninstall Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Uninstall Safari browser in an iPad Tablet.
+6. Uninstall Safari browser in an iPad Tablet with Physical Keyboard.
+
+
+
+---
+
+**TEST_279**
+
+Test case for Baseline_Swedish (Touch / Hardware Platforms),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `279`
+- Product: `Web`
+- Source files: `279.JSON`, `279.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC180
+
+
+Setup
+
+1. Install Chrome browser in an Android Mobile (Touch)
+2. Install Chrome browser in an Android Mobile attached with Physical Keyboard. (Hardware)
+3. Install Safari browser in an iPhone Mobile (Touch)
+4. Install Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Install Safari browser in an iPad Tablet (Touch)
+6. Install Safari browser in an iPad Tablet attached with Physical Keyboard. (Hardware)
+
+
+
+
+Action
+
+1. Click the Chrome browser icon from the Android Mobile.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the
+Search bar.
+3. Verify that the testing index page opens.
+4. Click 'View Keymanweb use samples' link button.
+5. Verify KeymanWeb Samples page opens.
+6. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Switch to Swedish keyboard.
+9. Verify that the Swedish keyboard appears on the display screen.
+10. Long press . (period) on the OSK.
+11. Verify that there is a subkey ' appears over the basekey.
+12. Touch the subkey ' .
+13. Press letter e.
+14. Verify that the two characters should not combine. (‘ e)
+15. Long press p.
+16. Verify that it shows the subkey.
+17. Long press G.
+18. Verify that it shows the subkey.
+19. Click the Chrome browser icon from the Android Mobile attached with a physical keyboard.
+20. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+21. Verify that the testing index page opens.
+22. Click 'View Keymanweb use samples' link button.
+23. Verify KeymanWeb Samples page opens.
+24. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+25. Verify the corresponding KeymaWeb Sample page opens.
+26. Switch to Swedish keyboard.
+27. Type ‘
+28. Type e
+29. Verify that the output shows é in the text input screen.
+30. Type o
+31. Type \
+32. Type e
+33. Verify that the output shows œ in the text input screen.
+34. Click Safari browser in an iPhone mobile.
+35. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+36. Verify that the testing index page opens.
+37. Click 'View Keymanweb use samples' link button.
+38. Verify KeymanWeb Samples page opens.
+39. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+40. Verify the corresponding KeymaWeb Sample page opens.
+41. Switch to Swedish keyboard.
+42. Verify that the Swedish keyboard appears on the display screen.
+43. Long press . (period) on the OSK.
+44. Verify that there is a subkey ' appears over the basekey.
+45. Touch the subkey ' .
+46. Press letter e.
+47. Verify that the two characters should not combine. (‘ e)
+48. Long press p.
+49. Verify that it shows the subkey.
+50. Long press G.
+51. Verify that it shows the subkey.
+52. Click Safari browser in an iPhone mobile attached with a physical keyboard.
+53. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+54. Verify that the testing index page opens.
+55. Click 'View Keymanweb use samples' link button.
+56. Verify KeymanWeb Samples page opens.
+57. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+58. Verify the corresponding KeymaWeb Sample page opens.
+59. Switch to Swedish keyboard.
+60. Type ‘
+61. Type e
+62. Verify that the output shows é in the text input screen.
+63. Type o
+64. Type \
+65. Type e
+66. Verify that the output shows œ in the text input screen.
+67. Click Safari browser in an iPad Tablet.
+68. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+69. Verify that the testing index page opens.
+70. Click 'View Keymanweb use samples' link button.
+71. Verify KeymanWeb Samples page opens.
+72. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+73. Verify the corresponding KeymaWeb Sample page opens.
+74. Switch to Swedish keyboard.
+75. Verify that the Swedish keyboard appears on the display screen.
+76. Long press . (period) on the OSK.
+77. Verify that there is a subkey ' appears over the basekey.
+78. Touch the subkey ' .
+79. Press letter e.
+80. Verify that the two characters should not combine. (‘ e)
+81. Long press p.
+82. Verify that it shows the subkey.
+83. Long press G.
+84. Verify that it shows the subkey.
+85. Click Safari browser in an iPad Tablet with a physical keyboard.
+86. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+87. Verify that the testing index page opens.
+88. Click 'View Keymanweb use samples' link button.
+89. Verify KeymanWeb Samples page opens.
+90. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+91. Verify the corresponding KeymaWeb Sample page opens.
+92. Switch to Swedish keyboard.
+93. Type ‘
+94. Type e
+95. Verify that the output shows é in the text input screen.
+96. Type o
+97. Type \
+98. Type e
+99. Verify that the output shows œ in the text input screen.
+
+
+
+
+Cleanup
+
+1. Uninstall Chrome browser in Android Mobile. (Touch)
+2. Uninstall Chrome browser in Android Mobile attached with Physical Keyboard.(Hardware)
+3. Uninstall Safari browser in an iPhone Mobile.
+4. Uninstall Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Uninstall Safari browser in an iPad Tablet.
+6. Uninstall Safari browser in an iPad Tablet with Physical Keyboard.
+
+
+
+---
+
+**TEST_280**
+
+Test case for Baseline_Cameroon (Touch Platforms),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `280`
+- Product: `Web`
+- Source files: `280.JSON`, `280.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC181
+
+
+Setup
+
+1. Install Chrome browser in an Android Mobile (Touch)
+2. Install Safari browser in an iPhone Mobile (Touch)
+3. Install Safari browser in an iPad Tablet (Touch)
+
+
+
+
+Action
+
+1. Click the Chrome browser icon from the Android Mobile.
+2. Enter https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/448575:id/index.html' in the Search bar.
+3. Verify that the testing index page opens.
+4. Click 'View Keymanweb use samples' link button.
+5. Verify KeymanWeb Samples page opens.
+6. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Click sil_cameroon_qwerty from the ‘Add a keyboard by keyboard name’ section.
+9. Click the Add button.
+10. Verify that the SIL_Cameroon_Qwerty keyboard is added to the list.
+11. Verify that the Cameroon Qwerty keyboard appears on the screen.
+12. Press q.
+13. Verify that the letter q appears on the text input screen.
+14. Press the Shift key.
+15. Verify that the Shift layer appears on the screen.
+16. Press Q.
+17. Verify that the letter Q appears on the screen.
+18. Press the Symbol layer.
+19. Verify that the symbols appear on the screen.
+20. Press $
+21. Verify that the symbol $ appears on the screen.
+22. Press the tri-color key.
+23. Verify that the special keys appear on the keyboard.
+24. Press ŋ
+25. Verify that the letter ŋ appears on the screen.
+26. Click the Safari browser in an iPhone Mobile (Touch)
+27. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/448575:id/index.html' in the Search bar.
+28. Verify that the testing index page opens.
+29. Click 'View Keymanweb use samples' link button.
+30. Verify KeymanWeb Samples page opens.
+31. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+32. Verify the corresponding KeymaWeb Sample page opens.
+33. Click sil_cameroon_qwerty from the ‘Add a keyboard by keyboard name’ section.
+34. Click the Add button.
+35. Verify that the SIL_Cameroon_Qwerty keyboard is added to the list.
+36. Verify that the Cameroon Qwerty keyboard appears on the screen.
+37. Press q.
+38. Verify that the letter q appears on the text input screen.
+39. Press the Shift key.
+40. Verify that the Shift layer appears on the screen.
+41. Press Q.
+42. Verify that the letter Q appears on the screen.
+43. Press the Symbol layer.
+44. Verify that the symbols appear on the screen.
+45. Press $
+46. Verify that the symbol $ appears on the screen.
+47. Press the tri-color key.
+48. Verify that the special keys appear on the keyboard.
+49. Press ŋ
+50. Verify that the letter ŋ appears on the screen.
+51. Click the Safari browser in an iPad Tablet (Touch)
+52. Enter https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/448575:id/index.html' in the Search bar.
+53. Verify that the testing index page opens.
+54. Click 'View Keymanweb use samples' link button.
+55. Verify KeymanWeb Samples page opens.
+56. Click 'Example1 - Toggle UI, all resources in same folder as page' link button.
+57. Verify the corresponding KeymaWeb Sample page opens.
+58. Click sil_cameroon_qwerty from the ‘Add a keyboard by keyboard name’ section.
+59. Click the Add button.
+60. Verify that the SIL_Cameroon_Qwerty keyboard is added to the list.
+61. Verify that the Cameroon Qwerty keyboard appears on the screen.
+62. Press q.
+63. Verify that the letter q appears on the text input screen.
+64. Press the Shift key.
+65. Verify that the Shift layer appears on the screen.
+66. Press Q.
+67. Verify that the letter Q appears on the screen.
+68. Press the Symbol layer.
+69. Verify that the symbols appear on the screen.
+70. Press $
+71. Verify that the symbol $ appears on the screen.
+72. Press the tri-color key.
+73. Verify that the special keys appear on the keyboard.
+74. Press ŋ
+75. Verify that the letter ŋ appears on the screen.
+
+
+
+
+Cleanup
+
+1. Uninstall Chrome browser in Android Mobile. (Touch)
+2. Uninstall Safari browser in an iPhone Mobile. (Touch)
+3. Uninstall Safari browser in an iPad Tablet. (Touch)
+
+
+
+---
+
+**TEST_281**
+
+Test case for Element Attachment Tests (Touch / Hardware platforms),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `281`
+- Product: `Web`
+- Source files: `281.JSON`, `281.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC182
+
+
+Setup
+
+1. Install Chrome browser in an Android Mobile (Touch)
+2. Install Chrome browser in an Android Mobile attached with Physical Keyboard. (Hardware)
+3. Install Safari browser in an iPhone Mobile (Touch)
+4. Install Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Install Safari browser in an iPad Tablet (Touch)
+6. Install Safari browser in an iPad Tablet attached with Physical Keyboard. (Hardware)
+
+
+
+
+Action
+
+1. Click the Chrome browser icon in an Android Mobile.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3. Verify that the testing index page opens.
+4. Click 'View Keymanweb website-oriented manual test pages' link button.
+5. Verify KeymanWeb 17 Testing page opens.
+6. Click 'Tests the new Attachment/Enablement API functionality' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Verify there are 2 radio buttons namely auto and manual appear one by one on the page.
+9. Enable ‘auto’ attachment mode radio button.
+10. Verify that it automatically attaches to each dynamically-added control.
+7. Enable ‘’manual’ attachment mode radio button.
+8. Verify that manual attachment mode results in a page with no KMW-activated controls.
+9. Verify that the KeymanWeb is properly attached to and detaches from each relevant type of control with the page’s API-interface controls.
+10. Click the Chrome browser icon in an Android Mobile device attached with a physical keyboard.
+11.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+12. Verify that the testing index page opens.
+13. Click 'View Keymanweb website-oriented manual test pages' link button.
+14. Verify KeymanWeb 17 Testing page opens.
+15. Click 'Tests the new Attachment/Enablement API functionality' link button.
+16. Verify the corresponding KeymaWeb Sample page opens.
+17. Verify there are 2 radio buttons namely auto and manual appear one by one on the page.
+18. Enable ‘auto’ attachment mode radio button.
+19. Verify that it automatically attaches to each dynamically-added control.
+20. Enable ‘’manual’ attachment mode radio button.
+21. Verify that manual attachment mode results in a page with no KMW-activated controls.
+22. Verify that the KeymanWeb is properly attached to and detaches from each relevant type of control with the page’s API-interface controls.
+23. Click the Safari browser icon in an iPhone mobile.
+24. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+25. Verify that the testing index page opens.
+26. Click 'View Keymanweb website-oriented manual test pages' link button.
+27. Verify KeymanWeb 17 Testing page opens.
+28. Click 'Tests the new Attachment/Enablement API functionality' link button.
+29. Verify the corresponding KeymaWeb Sample page opens.
+30. Verify there are 2 radio buttons namely auto and manual appear one by one on the page.
+31. Enable ‘auto’ attachment mode radio button.
+32. Verify that it automatically attaches to each dynamically-added control.
+33. Enable ‘’manual’ attachment mode radio button.
+34. Verify that manual attachment mode results in a page with no KMW-activated controls.
+35. Verify that the KeymanWeb is properly attached to and detaches from each relevant type of control with the page’s API-interface controls.
+36. Click the Safari browser icon in an iPhone attached with a physical keyboard.
+37. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+38. Verify that the testing index page opens.
+39. Click 'View Keymanweb website-oriented manual test pages' link button.
+40. Verify KeymanWeb 17 Testing page opens.
+41. Click 'Tests the new Attachment/Enablement API functionality' link button.
+42. Verify the corresponding KeymaWeb Sample page opens.
+43. Verify there are 2 radio buttons namely auto and manual appear one by one on the page.
+44. Enable ‘auto’ attachment mode radio button.
+45. Verify that it automatically attaches to each dynamically-added control.
+46. Enable ‘’manual’ attachment mode radio button.
+47. Verify that manual attachment mode results in a page with no KMW-activated controls.
+48. Verify that the KeymanWeb is properly attached to and detaches from each relevant type of control with the page’s API-interface controls.
+49. Click the Safari browser on an iPad tablet.
+50. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+51. Verify that the testing index page opens.
+52. Click 'View Keymanweb website-oriented manual test pages' link button.
+53. Verify KeymanWeb 17 Testing page opens.
+54. Click 'Tests the new Attachment/Enablement API functionality' link button.
+55. Verify the corresponding KeymaWeb Sample page opens.
+56. Verify there are 2 radio buttons namely auto and manual appear one by one on the page.
+57. Enable ‘auto’ attachment mode radio button.
+58. Verify that it automatically attaches to each dynamically-added control.
+59. Enable ‘’manual’ attachment mode radio button.
+60. Verify that manual attachment mode results in a page with no KMW-activated controls.
+61. Verify that the KeymanWeb is properly attached to and detaches from each relevant type of control with the page’s API-interface controls.
+62. Click the Safari browser icon in an iPad Tablet attached with a physical keyboard.
+63. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+64. Verify that the testing index page opens.
+65. Click 'View Keymanweb website-oriented manual test pages' link button.
+66. Verify KeymanWeb 17 Testing page opens.
+67. Click 'Tests the new Attachment/Enablement API functionality' link button.
+68. Verify the corresponding KeymaWeb Sample page opens.
+69. Verify there are 2 radio buttons namely auto and manual appear one by one on the page.
+70. Enable ‘auto’ attachment mode radio button.
+71. Verify that it automatically attaches to each dynamically-added control.
+72. Enable ‘’manual’ attachment mode radio button.
+73. Verify that manual attachment mode results in a page with no KMW-activated controls.
+74. Verify that the KeymanWeb is properly attached to and detaches from each relevant type of control with the page’s API-interface controls.
+
+
+
+
+Cleanup
+
+1. Uninstall Chrome browser in Android Mobile. (Touch)
+2. Uninstall Chrome browser in Android Mobile attached with Physical Keyboard.(Hardware)
+3. Uninstall Safari browser in an iPhone Mobile.
+4. Uninstall Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Uninstall Safari browser in an iPad Tablet.
+6. Uninstall Safari browser in an iPad Tablet with Physical Keyboard.
+
+
+
+---
+
+**TEST_282**
+
+Test case for Normal_Use (Touch / Hardware Platforms)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `282`
+- Product: `Web`
+- Source files: `282.JSON`, `282.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC183
+
+
+Setup
+
+1. Install Chrome browser in an Android Mobile (Touch)
+2. Install Chrome browser in an Android Mobile attached with Physical Keyboard. (Hardware)
+3. Install Safari browser in an iPhone Mobile (Touch)
+4. Install Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Install Safari browser in an iPad Tablet (Touch)
+6. Install Safari browser in an iPad Tablet attached with Physical Keyboard. (Hardware)
+
+
+
+
+Action
+
+1. Click the Chrome browser icon in an Android Mobile.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3. Verify that the testing index page opens.
+4. Click 'View Keymanweb website-oriented manual test pages' link button.
+5. Verify KeymanWeb 17 Testing page opens.
+6. Click 'Tests the new Attachment/Enablement API functionality' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+3. Click the “Create Inputs” button one time.
+4. Click / touch the new page element.
+5. Verify the On Screen Keyboard should display.
+6. Type “K” using OSK.
+7. Type “L” using OSK.
+8. Verify that the OSK keys should produce their expected output.
+9. Click / touch a blank area of the page.
+10. Verify that the OSK should automatically hide.
+11. Click the Chrome browser icon in an Android mobile attached with a physical keyboard.
+12. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+13. Verify that the testing index page opens.
+14. Click 'View Keymanweb website-oriented manual test pages' link button.
+15. Verify KeymanWeb 17 Testing page opens.
+16. Click 'Tests the new Attachment/Enablement API functionality' link button.
+17. Verify the corresponding KeymaWeb Sample page opens.
+18. Click the “Create Inputs” button one time.
+19. Click / touch the new page element.
+20. Verify the On Screen Keyboard should display.
+21. Type “K” using OSK.
+22. Type “L” using OSK.
+23. Verify that the OSK keys should produce their expected output.
+24. Click / touch a blank area of the page.
+25. Verify that the OSK should automatically hide.
+26. Click the Safari browser in an iPhone mobile.
+27. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+28. Verify that the testing index page opens.
+29. Click 'View Keymanweb website-oriented manual test pages' link button.
+30. Verify KeymanWeb 17 Testing page opens.
+31. Click 'Tests the new Attachment/Enablement API functionality' link button.
+32. Verify the corresponding KeymaWeb Sample page opens.
+33. Click the “Create Inputs” button one time.
+34. Click / touch the new page element.
+35. Verify the On Screen Keyboard should display.
+36. Type “K” using OSK.
+37. Type “L” using OSK.
+38. Verify that the OSK keys should produce their expected output.
+39. Click / touch a blank area of the page.
+40. Verify that the OSK should automatically hide.
+41. Click the Safari browser in an iPhone mobile attached with a physical keyboard.
+42. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+43. Verify that the testing index page opens.
+44. Click 'View Keymanweb website-oriented manual test pages' link button.
+45. Verify KeymanWeb 17 Testing page opens.
+46. Click 'Tests the new Attachment/Enablement API functionality' link button.
+47. Verify the corresponding KeymaWeb Sample page opens.
+48. Click the “Create Inputs” button one time.
+49. Click / touch the new page element.
+50. Verify the On Screen Keyboard should display.
+51. Type “K” using OSK.
+52. Type “L” using OSK.
+53. Verify that the OSK keys should produce their expected output.
+54. Click / touch a blank area of the page.
+55. Verify that the OSK should automatically hide.
+56. Click Safari browser in an iPad Tablet.
+57. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+58. Verify that the testing index page opens.
+59. Click 'View Keymanweb website-oriented manual test pages' link button.
+60. Verify KeymanWeb 17 Testing page opens.
+61. Click 'Tests the new Attachment/Enablement API functionality' link button.
+62. Verify the corresponding KeymaWeb Sample page opens.
+63. Click the “Create Inputs” button one time.
+64. Click / touch the new page element.
+65. Verify the On Screen Keyboard should display.
+66. Type “K” using OSK.
+67. Type “L” using OSK.
+68. Verify that the OSK keys should produce their expected output.
+69. Click / touch a blank area of the page.
+70. Verify that the OSK should automatically hide.
+71. Click Safari browser in an iPad Tablet with a physical keyboard.
+72. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+73. Verify that the testing index page opens.
+74. Click 'View Keymanweb website-oriented manual test pages' link button.
+75. Verify KeymanWeb 17 Testing page opens.
+76. Click 'Tests the new Attachment/Enablement API functionality' link button.
+77. Verify the corresponding KeymaWeb Sample page opens.
+78. Click the “Create Inputs” button one time.
+79. Click / touch the new page element.
+80. Verify the On Screen Keyboard should display.
+81. Type “K” using OSK.
+82. Type “L” using OSK.
+83. Verify that the OSK keys should produce their expected output.
+84. Click / touch a blank area of the page.
+85. Verify that the OSK should automatically hide.
+
+
+
+
+Cleanup
+
+1. Uninstall Chrome browser in Android Mobile. (Touch)
+2. Uninstall Chrome browser in Android Mobile attached with Physical Keyboard.(Hardware)
+3. Uninstall Safari browser in an iPhone Mobile.
+4. Uninstall Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Uninstall Safari browser in an iPad Tablet.
+6. Uninstall Safari browser in an iPad Tablet with Physical Keyboard.
+
+
+
+---
+
+**TEST_283**
+
+Test case for Element_Hopping (Touch / Hardware Platform),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `283`
+- Product: `Web`
+- Source files: `283.JSON`, `283.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC184
+
+
+Setup
+
+1. Install Chrome browser in an Android Mobile (Touch)
+2. Install Chrome browser in an Android Mobile attached with Physical Keyboard. (Hardware)
+3. Install Safari browser in an iPhone Mobile (Touch)
+4. Install Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Install Safari browser in an iPad Tablet (Touch)
+6. Install Safari browser in an iPad Tablet attached with Physical Keyboard. (Hardware)
+
+
+
+
+Action
+
+1. Click the Chrome browser in an Android mobile. (Touch)
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3. Verify that the testing index page opens.
+4. Click 'View Keymanweb website-oriented manual test pages' link button.
+5. Verify KeymanWeb 17 Testing page opens.
+6. Click 'Tests the new Attachment/Enablement API functionality' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8. Click the ‘Create Inputs’ button one time.
+9. Click the ‘Create Textarea’ button one time.
+10. Click / touch the first of the new page elements.
+11. Verify that the OSK should display.
+12. Click / touch the other page element.
+13. Verify that the OSK should remain visible.
+14. Click / touch the first element again.
+15. Verify that the OSK should remain visible.
+16. Click / touch a blank area of the page.
+17. Verify that the OSK should automatically hide.
+18. Click the Chrome browser in Android mobile attached with physical keyboard
+19.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+20. Verify that the testing index page opens.
+21. Click 'View Keymanweb website-oriented manual test pages' link button.
+22. Verify KeymanWeb 17 Testing page opens.
+23. Click 'Tests the new Attachment/Enablement API functionality' link button.
+24. Verify the corresponding KeymaWeb Sample page opens.
+25. Click the ‘Create Inputs’ button one time.
+26. Click the ‘Create Textarea’ button one time.
+27. Click / touch the first of the new page elements.
+28. Verify that the OSK should display.
+29. Click / touch the other page element.
+30. Verify that the OSK should remain visible.
+31. Click / touch the first element again.
+32. Verify that the OSK should remain visible.
+33. Click / touch a blank area of the page.
+34. Verify that the OSK should automatically hide.
+35. Click the Safari browser icon in an iPhone mobile.
+36. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+43. Verify that the testing index page opens.
+44. Click 'View Keymanweb website-oriented manual test pages' link button.
+45. Verify KeymanWeb 17 Testing page opens.
+46. Click 'Tests the new Attachment/Enablement API functionality' link button.
+47. Verify the corresponding KeymaWeb Sample page opens.
+48. Click the ‘Create Inputs’ button one time.
+49. Click the ‘Create Textarea’ button one time.
+50. Click / touch the first of the new page elements.
+51. Verify that the OSK should display.
+52. Click / touch the other page element.
+53. Verify that the OSK should remain visible.
+54. Click / touch the first element again.
+55. Verify that the OSK should remain visible.
+56. Click / touch a blank area of the page.
+57. Verify that the OSK should automatically hide.
+58. Click the Safari browser icon in an iPhone mobile attached with physical keyboard
+59. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+60. Verify that the testing index page opens.
+61. Click 'View Keymanweb website-oriented manual test pages' link button.
+62. Verify KeymanWeb 17 Testing page opens.
+63. Click 'Tests the new Attachment/Enablement API functionality' link button.
+64. Verify the corresponding KeymaWeb Sample page opens.
+65. Click the ‘Create Inputs’ button one time.
+66. Click the ‘Create Textarea’ button one time.
+67. Click / touch the first of the new page elements.
+68. Verify that the OSK should display.
+69. Click / touch the other page element.
+70. Verify that the OSK should remain visible.
+71. Click / touch the first element again.
+72. Verify that the OSK should remain visible.
+73. Click / touch a blank area of the page.
+74. Verify that the OSK should automatically hide.
+75. Click the Safari browser icon on the iPad device.
+76.Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+77. Verify that the testing index page opens.
+78. Click 'View Keymanweb website-oriented manual test pages' link button.
+79. Verify KeymanWeb 17 Testing page opens.
+80. Click 'Tests the new Attachment/Enablement API functionality' link button.
+81. Verify the corresponding KeymaWeb Sample page opens.
+83. Click the ‘Create Inputs’ button one time.
+84. Click the ‘Create Textarea’ button one time.
+85. Click / touch the first of the new page elements.
+86. Verify that the OSK should display.
+87. Click / touch the other page element.
+88. Verify that the OSK should remain visible.
+89. Click / touch the first element again.
+90. Verify that the OSK should remain visible.
+91. Click / touch a blank area of the page.
+92. Verify that the OSK should automatically hide.
+93. Click the Safari browser icon in the iPad device attached with the physical keyboard.
+94. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+95. Verify that the testing index page opens.
+96. Click 'View Keymanweb website-oriented manual test pages' link button.
+97. Verify KeymanWeb 17 Testing page opens.
+98. Click 'Tests the new Attachment/Enablement API functionality' link button.
+99. Verify the corresponding KeymaWeb Sample page opens.
+100. Click the ‘Create Inputs’ button one time.
+101. Click the ‘Create Textarea’ button one time.
+102. Click / touch the first of the new page elements.
+103. Verify that the OSK should display.
+104. Click / touch the other page element.
+105. Verify that the OSK should remain visible.
+106. Click / touch the first element again.
+107. Verify that the OSK should remain visible.
+108. Click / touch a blank area of the page.
+109. Verify that the OSK should automatically hide.
+
+
+
+
+Cleanup
+
+1. Uninstall Chrome browser in Android Mobile. (Touch)
+2. Uninstall Chrome browser in Android Mobile attached with Physical Keyboard.(Hardware)
+3. Uninstall Safari browser in an iPhone Mobile.
+4. Uninstall Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Uninstall Safari browser in an iPad Tablet.
+6. Uninstall Safari browser in an iPad Tablet with Physical Keyboard.
+
+
+
+---
+
+**TEST_284**
+
+Test case for Specific_Keyboards (Touch / Hardware Platforms),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `284`
+- Product: `Web`
+- Source files: `284.JSON`, `284.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC185
+
+
+Setup
+
+1. Install Chrome browser in an Android Mobile (Touch)
+2. Install Chrome browser in an Android Mobile attached with Physical Keyboard. (Hardware)
+3. Install Safari browser in an iPhone Mobile (Touch)
+4. Install Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Install Safari browser in an iPad Tablet (Touch)
+6. Install Safari browser in an iPad Tablet attached with Physical Keyboard. (Hardware)
+
+
+
+
+Action
+
+1. Click the Chrome browser icon in an Android mobile device.
+2. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+3. Verify that the testing index page opens.
+4. Click 'View Keymanweb website-oriented manual test pages' link button.
+5. Verify KeymanWeb 17 Testing page opens.
+6. Click 'Tests the new Attachment/Enablement API functionality' link button.
+7. Verify the corresponding KeymaWeb Sample page opens.
+8 . Click the ‘Create Inputs’ button three times.
+9. Click / touch Dynamic area #0.
+10. Click the element’s “Set to Dzongkha’ button.
+11. Change the keyboard to French.
+12. Click Dynamic area #1 ‘s ‘Set to Dzongkha button.
+13. Click Dynamic area #1.
+14. Verify the Dzongkha keyboard should be displayed.
+15. Click Dynamic area #2.
+16. Change the keyboard to Lao.
+17. Click Dynamic area#0.
+18. Verify that the French keyboard should be displayed.
+19. Click Dynamic area #2.
+20. Verify that the Lao keyboard should be displayed.
+21. Click the Chrome browser icon in an Android mobile device with a physical keyboard.
+22. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+23. Verify that the testing index page opens.
+25. Click 'View Keymanweb website-oriented manual test pages' link button.
+26. Verify KeymanWeb 17 Testing page opens.
+27. Click 'Tests the new Attachment/Enablement API functionality' link button.
+28. Verify the corresponding KeymaWeb Sample page opens.
+29. Click the ‘Create Inputs’ button three times.
+30. Click / touch Dynamic area #0.
+31. Click the element’s “Set to Dzongkha’ button.
+32. Change the keyboard to French.
+33. Click Dynamic area #1 ‘s ‘Set to Dzongkha button.
+34. Click Dynamic area #1.
+35. Verify the Dzongkha keyboard should be displayed.
+36. Click Dynamic area #2.
+37. Change the keyboard to Lao.
+38. Click Dynamic area#0.
+39. Verify that the French keyboard should be displayed.
+40. Click Dynamic area #2.
+41. Verify that the Lao keyboard should be displayed.
+42. Click the Safari browser icon in an iPhone mobile device.
+43. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+44. Verify that the testing index page opens.
+45. Click 'View Keymanweb website-oriented manual test pages' link button.
+46. Verify KeymanWeb 17 Testing page opens.
+47. Click 'Tests the new Attachment/Enablement API functionality' link button.
+48. Verify the corresponding KeymaWeb Sample page opens.
+49. Click the ‘Create Inputs’ button three times.
+50. Click / touch Dynamic area #0.
+51. Click the element’s “Set to Dzongkha’ button.
+52. Change the keyboard to French.
+53. Click Dynamic area #1 ‘s ‘Set to Dzongkha button.
+54. Click Dynamic area #1.
+55. Verify the Dzongkha keyboard should be displayed.
+56. Click Dynamic area #2.
+57. Change the keyboard to Lao.
+58. Click Dynamic area#0.
+59. Verify that the French keyboard should be displayed.
+60. Click Dynamic area #2.
+61. Verify that the Lao keyboard should be displayed.
+62. Click the Safari browser icon in an iPhone mobile device attached with a physical keyboard.
+63. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+64. Verify that the testing index page opens.
+65. Click 'View Keymanweb website-oriented manual test pages' link button.
+66. Verify KeymanWeb 17 Testing page opens.
+67. Click 'Tests the new Attachment/Enablement API functionality' link button.
+68. Verify the corresponding KeymaWeb Sample page opens.
+69. Click the ‘Create Inputs’ button three times.
+70. Click / touch Dynamic area #0.
+71. Click the element’s “Set to Dzongkha’ button.
+72. Change the keyboard to French.
+73. Click Dynamic area #1 ‘s ‘Set to Dzongkha button.
+74. Click Dynamic area #1.
+75. Verify the Dzongkha keyboard should be displayed.
+76. Click Dynamic area #2.
+77. Change the keyboard to Lao.
+78. Click Dynamic area#0.
+79. Verify that the French keyboard should be displayed.
+80. Click Dynamic area #2.
+81. Verify that the Lao keyboard should be displayed.
+82. Click the Safari browser icon on an iPad device.
+83. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+84. Verify that the testing index page opens.
+85. Click 'View Keymanweb website-oriented manual test pages' link button.
+86. Verify KeymanWeb 17 Testing page opens.
+87. Click 'Tests the new Attachment/Enablement API functionality' link button.
+88. Verify the corresponding KeymaWeb Sample page opens.
+89. Click the ‘Create Inputs’ button three times.
+90. Click / touch Dynamic area #0.
+91. Click the element’s “Set to Dzongkha’ button.
+92. Change the keyboard to French.
+93. Click Dynamic area #1 ‘s ‘Set to Dzongkha button.
+94. Click Dynamic area #1.
+95. Verify the Dzongkha keyboard should be displayed.
+96. Click Dynamic area #2.
+97. Change the keyboard to Lao.
+98. Click Dynamic area#0.
+99. Verify that the French keyboard should be displayed.
+100. Click Dynamic area #2.
+101. Verify that the Lao keyboard should be displayed.
+102. Click the Safari browser icon in an iPad device attached with a physical keyboard.
+103. Enter ‘https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/391530:id/index.html' in the Search bar.
+104. Verify that the testing index page opens.
+105. Click 'View Keymanweb website-oriented manual test pages' link button.
+106. Verify KeymanWeb 17 Testing page opens.
+107. Click 'Tests the new Attachment/Enablement API functionality' link button.
+108. Verify the corresponding KeymaWeb Sample page opens.
+109. Click the ‘Create Inputs’ button three times.
+110. Click / touch Dynamic area #0.
+111. Click the element’s “Set to Dzongkha’ button.
+112. Change the keyboard to French.
+113. Click Dynamic area #1 ‘s ‘Set to Dzongkha button.
+114. Click Dynamic area #1.
+115. Verify the Dzongkha keyboard should be displayed.
+116. Click Dynamic area #2.
+117. Change the keyboard to Lao.
+118. Click Dynamic area#0.
+119. Verify that the French keyboard should be displayed.
+120. Click Dynamic area #2.
+121. Verify that the Lao keyboard should be displayed.
+
+
+
+
+Cleanup
+
+1. Uninstall Chrome browser in Android Mobile. (Touch)
+2. Uninstall Chrome browser in Android Mobile attached with Physical Keyboard.(Hardware)
+3. Uninstall Safari browser in an iPhone Mobile.
+4. Uninstall Safari browser in an iPhone Mobile attached with Physical Keyboard. (Hardware)
+5. Uninstall Safari browser in an iPad Tablet.
+6. Uninstall Safari browser in an iPad Tablet with Physical Keyboard.
+
+
+
+---
+
+**TEST_285**
+
+Test case for (web): intermittent K_BKSP rule is deleting more than it should #9268,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `285`
+- Product: `Web`
+- Source files: `285.JSON`, `285.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC211
+
+
+Setup
+
+1. Install Keyman Developer's latest Stable build in a browser.
+2.
+Action Setup:
+1. Open a project in Keyman Developer.
+2. Click the Build tab
+3. Click the ‘Test Keyboard on web’ button in the web debugger pane.
+4. Verify that the localhost list appeared in the keyboard web pane
+5. Select the Keyboard from the Keyboard dropdown list.
+6. Type ‘x / k ‘
+7. Select x letter
+8. Press Backspace key.
+9. Verify that it deletes only the x letter.
+
+
+
+
+Action
+
+No steps recorded.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Taskbar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully
+
+
+
+---
+
+**TEST_286**
+
+fix(web): correctly handle cross-origin stylesheets when calculating keyboard size and key cap font size #11472
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `286`
+- Product: `Web`
+- Source files: `286.JSON`, `286.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC216
+
+
+Setup
+
+1. Install Keyman's latest stable build from the Keyman.com site.
+2. Install the Chrome browser.
+
+
+
+
+Action
+
+1. Open the Chrome browser.
+2. Open the developer tool by pressing the F12 key.
+3. Verify that the "developer" tool pane appeared on the browser.
+4. Click on the console tab.
+5. Clear the existing log by pressing CTRL+L.
+6. Paste the "https://build.palaso.org/repository/download/Keymanweb_TestPullRequests/463931:id/index.html" URL in the address bar.
+7. Verify that the "KeymanWeb Repo Index" page appeared.
+8. Click the "View Keymanweb website-oriented manual test pages" link button.
+9. Verify that the "KeymanWeb Testing" page appeared.
+10. Verify that the URL changed to "/src/test/manual/web/index.html" in the address bar.
+11. Click the "Tests keyboard documentation rendering" link button.
+12. Verify that the URL changed to "/src/test/manual/web/build-visual-keyboard/index.html" in the address bar.
+13. Verify that the "KeymanWeb: Keyboard documentation rendering" page is on the browser.
+14. Verify that the page rendering happened successfully.
+15. Verify that no error appeared on console tab.
+16. Close the Chrome browser.
+
+
+
+
+Cleanup
+
+1. Type ‘Control Panel’ in the search bar (in the taskbar).
+2. Verify that the ‘Control Panel’ appeared on the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the keyman uninstallation was completed successfully.
+
+
+
+---
+
+**TEST_312**
+
+TC - fix(web): numpad + and - with zoom shortcut
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `312`
+- Product: `Web`
+- Source files: `312.JSON`, `312.html`
+
+
+
+**Description**
+
+TC - fix(web): numpad + and - with zoom shortcut use #12865
+
+
+Setup
+
+1. Install Firefox in windows.
+2. Install Chrome in windows.
+3. Install Safari in macOS.
+4. Install Chrome in macOS.
+5. Install Firefox in macOS.
+6. Install Firefox in Linux OS.
+
+
+
+
+Action
+
+1. Open the "KeymanWeb Test Home" link on Chrome.
+2. Click on the "View Keymanweb website-oriented manual test pages." link
+3. Click on the "Test unminified Keymanweb" link
+4. Verify that the "KeymanWeb Sample Page - Unminified Source" page appears.
+5. Click in the text area box.
+6. Verify that the OSK appears for english.
+7. Select the "Norwegian - EuroLatin (SIL)" keyboard.
+8. Verify that the OSK appears for Norwegian - EuroLatin.
+9. Enter some "other letters"
+10. Select the text.
+11. Press the CTR + plus(+ on the numpad) using a physical keyboard.
+12. Verify that the web page's size increased. (zoom in)
+13. Press the CTR + minus(- on the numpad) using a physical keyboard.
+14. Verify that the web page's size decreased. (zoom out)
+
+
+
+
+Cleanup
+
+1. Uninstall Firefox browser in Windows.
+2. Uninstall Chrome in Windows.
+3. Uninstall Safari in macOS.
+4. Uninstall Chrome in macOS.
+5. Uninstall Firefox in macOS.
+6. Uninstall Firefox in Linux OS.
+
+
+
+---
+
+**TEST_334_334**
+
+Cancel flicks when both returning to and releasing at original tap location_TEST_FLICK_GENERAL_USE
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `334`
+- Product: `Web`
+- Source files: `334.JSON`, `334.html`
+
+
+
+**Description**
+
+TC - change(web): cancel flicks when both returning to and releasing at original tap location_TEST_FLICK_GENERAL_USE #13683
+
+
+Setup
+
+1. Install the latest Keymanan (.apk) build on the Android device or emulator.
+2. Accept all the Android permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Select the "Eurolatin" keyboard by clicking the globe key.
+3. Click on the "t" key and then pull down.
+4. Verify that the flick gesture is working fine and the output is correct.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon on the Android device/emulator.
+2. Verify that the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman appears on the list.
+5. Click the Keyman option.
+6. Verify that the Keyman menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message, “Do you want to uninstall this app?” appears with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman uninstallation completed successfully.
+
+
+
+---
+
+**TEST_337_337**
+
+Cancel flicks when both returning to and releasing at original tap location_TEST_FLICK_RESET_FULL
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `337`
+- Product: `Web`
+- Source files: `337.JSON`, `337.html`
+
+
+
+**Description**
+
+TC - change(web): cancel flicks when both returning to and releasing at original tap location_TEST_FLICK_RESET_FULL #13683
+
+
+Setup
+
+1. Install the latest Keymanan (.apk) build on the Android device or emulator.
+2. Accept all the Android permission requests for storage.
+3. Open the Keyman app.
+4. Navigate to the settings page.
+5. Check the "Enable Keyman as system-wide keyboard" box.
+6. Check the "Set the keyboard as the default keyboard" box.
+7. Enable the "Predictions" to install the "Dictionary."
+
+
+
+
+Action
+
+1. Launch the Keyman app.
+2. Select the "Eurolatin" keyboard by clicking the globe key.
+3. Flick down the t key.
+4. Verify that the 5 appears.
+5. Flick back up to the center of the key and the 5 change back to t
+6. Flick down again, and the 5 appear in the preview again
+7. Release the key.
+8. Verify that the key has output 5.
+
+
+
+
+Cleanup
+
+1. Click the Settings icon on the Android device/emulator.
+2. Verify that the Settings menu opens.
+3. Click the Apps option.
+4. Verify that the Keyman appears on the list.
+5. Click the Keyman option.
+6. Verify that the Keyman menu opens.
+7. Click the uninstall option.
+8. Verify that a Keyman warning message, “Do you want to uninstall this app?” appears with Cancel and OK buttons.
+9. Click the OK button.
+10. Verify that the Keyman uninstallation completed successfully.
+
+
+
+---
+
diff --git a/docs/tests/acceptance/windows.md b/docs/tests/acceptance/windows.md
new file mode 100644
index 0000000000..b8edc32dc9
--- /dev/null
+++ b/docs/tests/acceptance/windows.md
@@ -0,0 +1,2966 @@
+# Windows Acceptance Tests
+
+**TEST_1**
+
+Test case for INSTALL Keyman
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `1`
+- Product: `Windows`
+- Source files: `1.JSON`, `1.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC01
+
+
+Setup
+
+1. Download Keyman latest Stable build from Keyman.com Site
+
+
+
+
+Action
+
+1. Double click on Keyman shortcut icon from Desktop
+2. Verify that 'Do you want to allow this app to make changes to your device?' warning message with Yes or No button.
+3. Click the 'Yes' button.
+4. Verify the 'Keyman Setup' dialog appears on the screen.
+5. Click the "Install Options" blue link button.
+6. Verify that the Keyman Setup window appears with the ‘Install’ button.
+7. Verify that the ‘Install Options’ blue link button appears at the bottom of the dialog.
+8. Click on the ‘Install Options’ blue link button.
+9. Verify that the ‘Install Options’ dialog box appears on the Screen.
+10. Verify that the dialog box appears with the ‘OK’ and ‘Cancel’ button.
+11. Click the OK button.
+12. Verify that the Keyman Setup dialog box appears.
+13. Click the UI drop down list box.
+14. Click ‘Bura-Pabir’ on the list box.
+15. Verify that the UI language of Keyman Setup window has been changed into ‘Bura-Pabir’.
+16. Click the ‘Install Options’ blue link button.
+17. Verify that the UI language menu has been changed into ‘Bura-Pabir’.
+18. Click the Install button.
+19. Verify that the In-progress window with the message Downloading Keyman desktop.msi appears on the Screen.
+20. Verify that the Keyman Welcome Windows appears on the Screen.
+21. Verify that the Start Keyman, Configuration and Exit button appears on the dialog.
+22. Verify that the Open Configuration blue link button appears on the dialog.
+23. Click the ‘Start Keyman’ button.
+24. Verify that the Keyman is started and visible in the Notification area (in the task bar).
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation completed successfully.
+
+
+
+---
+
+**TEST_2**
+
+Test case for KEYBOARD_INSTALLATION_REMOTE,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `2`
+- Product: `Windows`
+- Source files: `2.JSON`, `2.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC02
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+
+
+
+
+Action
+
+1. Double click on the Keyman icon from the desktop.
+2. Verify that the Keyman Welcome dialog appears on the Screen.
+3. Click the ‘Configuration’ button.
+4. Verify that the Keyman configuration dialog opens.
+5. Click the Download Keyboard button.
+6. Verify that the ‘Download keyboard from..’ dialog box opens.
+7. Type ‘Khmer Angkor’ in the Search box.
+8. Verify that the Khmer Angkor Keyboard appears under ‘Results’.
+9. Click the ‘Khmer Angkor’ link.
+10. Verify that the ‘Install Keyboard’ green button appears.
+11. Click the ‘Install Keyboard’ green button.
+12. Verify that the ‘Downloading File’ dialog box appears.
+13. Verify that the Install Keyboard / Package dialog box appears.
+14. Verify that Details and Readme tabs appear on this dialog.
+15. Click the Readme tab.
+16. Verify that the readme file opens.
+17. Click the Cancel button.
+18. Verify that the Install Keyboard / Package dialog box Closes.
+19. Click the Install button.
+20. Verify that a Warning message appears on the screen stating whether we are allowed to install the Keyman in our Desktop.
+21. Click the Okay button.
+22. Verify that the Welcome dialog appears on the Screen.
+23. Click the OK button on the Welcome dialog.
+24. Click the Okay button to close the Keyman Configuration dialog.
+25. Click the Keyman icon from the Taskbar.
+26. Verify that the Keyman menu appears.
+27. Click the ‘Khmer - Khmer Angkor’ option.
+28. Open Notepad.
+29. Verify that the Khmer Keyboard icon appears instead of the Keyman icon.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_3**
+
+Test case for INSTALL_PKG_DISK,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `3`
+- Product: `Windows`
+- Source files: `3.JSON`, `3.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC03
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Download Khmer Angkor.kmp file on the Desktop
+
+
+
+
+Action
+
+1. Double click on the Khmer Angkor.kmp file.
+2. Verify that the Install Keyboard / Package dialog box appears.
+3. Verify that Details and Readme tabs appear on this dialog.
+4. Click the Readme tab.
+5. Verify that the readme file opens.
+6. Click the Cancel button.
+7. Verify that the Install Keyboard / Package dialog box Closes.
+8. Click the Install button.
+9. Verify that a Warning message appears “Do you want to allow this app to make changes to your device?” with a Yes or No button.
+10. Click the Yes button.
+11. Verify that the Welcome dialog appears on the Screen on the OK button.
+12. Click the OK button on the Welcome dialog.
+13. Click the Okay button to close the Keyman Configuration dialog.
+14. Click the Keyman icon from the Taskbar.
+15. Verify that the Keyman menu appears.
+16. Click the ‘Configuration’ option from the menu.
+17. Verify the Keyman Configuration dialog box opens.
+18. Click the ‘Keyboard Layouts’ tab.
+19. Verify that the ‘Khmer Angkor’ keyboard is successfully installed.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_4**
+
+Test Case for KEYBOARD_OUTPUT,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `4`
+- Product: `Windows`
+- Source files: `4.JSON`, `4.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC04
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install Khmer Angkor Keyboard.
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click on the Keyman icon from the Taskbar.
+4. Verify that the Keyman menu opens.
+5. Click Khmer - Khmer Angkor keyboard.
+6. Verify that the Keyman icon changes in the Task bar.
+7. Type ‘xEjmr’ on the Notepad.
+8. Verify that the output results ខ្មែរ
+9. Double Click on LibreOffice Writer app
+10. Verify that the LibreOffice Document opens.
+11. Click on the Keyman icon from the Taskbar.
+12. Verify that the Keyman menu opens.
+13. Click Khmer - Khmer Angkor keyboard.
+14. Verify that the Keyman icon changes in the Task bar.
+15. Type ‘xEjmr’ on the Document.
+16. Verify that the output results ខ្មែរ
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_5**
+
+Test Case for ON_SCREEN_KEYBOARD,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `5`
+- Product: `Windows`
+- Source files: `5.JSON`, `5.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC05
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install Khmer Angkor Keyboard.
+
+
+
+
+Action
+
+1. Click the Keyman icon from the taskbar.
+2. Verify that the Keyman menu opens.
+3. Click the Khmer - Khmer Angkor keyboard option.
+4. Verify that the Keyman icon changes in the task bar.
+5. Click On Screen Keyboard option from the menu.
+6. Verify that the On Screen Keyboard
+7. Open Notepad app
+8. Type ស ដថ from the OSK.
+9. Verify the output results of the same words.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.yman 16.0’ from the list.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_6**
+
+Test case for Uppercase with Virtual key (Capslock-1) ,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `6`
+- Product: `Windows`
+- Source files: `6.JSON`, `6.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC06
+
+
+Setup
+
+1.Install Keyman latest Stable build from Keyman.com site.
+2.Install CapsLock Keyboard.
+3.CapsLock is currently on
+4. Currently active keyboard is the CapsLock Keyboard.
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Type ‘a’
+4. Verify that the word ‘pass’ appears on the Notepad.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_7**
+
+Test case for Lowercase with Virtual Key (Capslock-2),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `7`
+- Product: `Windows`
+- Source files: `7.JSON`, `7.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC07
+
+
+Setup
+
+1.Install Keyman latest Stable build from Keyman.com Site.
+2.Install CapsLock Keyboard.
+3. CapsLock is currently on
+4.Currently active keyboard is the CapsLock Keyboard.
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Press Shift + b keys.
+4. Verify that the word ‘pass’ should appear on the Notepad.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_8**
+
+Test case for Capslock ignored for numbers (capslock-3),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `8`
+- Product: `Windows`
+- Source files: `8.JSON`, `8.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC08
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install Capslock Keyboard.
+3. CapsLock is currently on
+4. Currently active keyboard is the CapsLock Keyboard
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Press Shift + 3 keys.
+4. Verify that the text ‘pass’ should appear on the Notepad.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_9**
+
+Test case for UpperCase (Capslock-4),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `9`
+- Product: `Windows`
+- Source files: `9.JSON`, `9.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC09
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install Capslock Keyboard.
+3. CapsLock is currently on
+4. Currently active keyboard is the CapsLock Keyboard
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Type ‘c’
+4. Verify that the text ‘pass’ should appear on the Notepad.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_10**
+
+Test case for Lowercase (Capslock-5),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `10`
+- Product: `Windows`
+- Source files: `10.JSON`, `10.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC10
+
+
+Setup
+
+1. Install Keymanlatest Stable build from Keyman.com Site.
+2. Install Capslock keyboard.
+3. CapsLock is currently on
+4. Currently active keyboard is the capslock.kmp keyboard
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Press Shift + d keys.
+4. Verify that the text ‘pass’ should appear on the Notepad.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_11**
+
+Test case for Caps Always off (Capsoff-1 ),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `11`
+- Product: `Windows`
+- Source files: `11.JSON`, `11.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC11
+
+
+Setup
+
+1. Install Keyman latest stable build from Keyman.com Site.
+2. Install caps_always_off keyboard.
+3. CapsLock is currently off
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Click ‘capsalwaysoff’ keyboard.
+6. Verify that the CapsalwaysOff icon appears in the taskbar.
+7. Type ‘a’ in the Notepad.
+8. Verify that the result should show ‘ncaps_little_a’ in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_12**
+
+Test case for Caps lock stays off (capsoff-2),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `12`
+- Product: `Windows`
+- Source files: `12.JSON`, `12.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC12
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install caps_always_off Keyboard.
+3. CapsLock is currently off
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Select Capsalwaysoff keyboard.
+6. Verify that the Capsalwaysoff keyboard icon appears in the taskbar.
+7. Press CapsLock key.
+8. Type ‘a’
+9. Verify that the caps lock indicator stays turned off.
+10. Verify that the result should show ‘ncaps_little_a’ in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_13**
+
+Test case for No Caps lock while holding capslock key (capsoff-3),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `13`
+- Product: `Windows`
+- Source files: `13.JSON`, `13.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC13
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install Caps_always_off Keyboard.
+3. CapsLock is currently off
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Click Capsalwaysoff keyboard.
+6. Verify that the Capsalwaysoff keyboard icon appears in the taskbar.
+7. Hold the CapsLock key
+8. Type ‘a’
+9. Release CapsLock key
+10. Verify that the results should show ‘ncaps_little_a’ in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_14**
+
+Test case for Caps lock while holding capslock key (capsoff-4),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `14`
+- Product: `Windows`
+- Source files: `14.JSON`, `14.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC14
+
+
+Setup
+
+1. Install Keyman latest build from Keyman.com Site.
+2. Install Caps_always_off Keyboard.
+3. CapsLock is currently off
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Click Capsalwaysoff keyboard.
+6. Verify that the Capsalwaysoff keyboard icon appears in the taskbar.
+7. Press ’ CapsLock Key + Shift Key + a ‘ keys.
+8. Verify that output should show ‘ncaps_shift_A’ in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_15**
+
+Test case for switching turns off caps lock (capsoff-5),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `15`
+- Product: `Windows`
+- Source files: `15.JSON`, `15.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC15
+
+
+Setup
+
+• Install Keyman latest Stable build from Keyman.com Site.
+• Install caps_always_off.kmp.
+• CapsLock is currently off
+
+
+
+
+Action
+
+1. Turn on caps lock
+2. Double Click on Notepad icon from the desktop.
+3. Verify that the Notepad app opens
+4. Click the Keyman icon from the taskbar.
+5. Verify that the Keyman menu opens.
+6. Click Capsalwaysoff keyboard.
+7. Type ‘a’
+8. Verify that the caps lock indicator turned off
+9. Verify that output should show ‘ncaps_little_a’ in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_16**
+
+Test case for No Caps (CapsOnly-1),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `16`
+- Product: `Windows`
+- Source files: `16.JSON`, `16.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC16
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install Shift_frees_caps Keyboard.
+3. CapsLock is currently off
+4. Currently active keyboard is shift_frees_caps keyboard
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Type 1
+4. Verify the output results should show ‘pass.’ in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_17**
+
+Test case for Caps (CapsOnly-2),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `17`
+- Product: `Windows`
+- Source files: `17.JSON`, `17.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC17
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install Shift_frees_caps Keyboard.
+3. CapsLock is currently off
+4. Currently active keyboard is shift_frees_caps keyboard
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Press CapsLock key.
+4. Type 2
+5. Verify that the caps lock indicator turned on
+6. Verify that the output should show ‘pass.’ in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_18**
+
+Test case for Caps doesn’t toggle (CapsOnly-3),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `18`
+- Product: `Windows`
+- Source files: `18.JSON`, `18.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC18
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install Shift_frees_caps Keyboard.
+3. CapsLock is currently off
+4. Currently active keyboard is shift_frees_caps keyboard
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop
+2. Verify that the Notepad app opens
+3. Press CapsLock key.
+4. Release CapsLock key.
+5. Type 6
+6. Verify that the Caps lock indicator is turned ON.
+7. Verify that the output should show the result ‘pass.’ in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_19**
+
+Test case for Shift turns off (CapsOnly-4),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `19`
+- Product: `Windows`
+- Source files: `19.JSON`, `19.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC19
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install Shift_frees_caps Keyboard.
+3. CapsLock is currently off
+4. Currently active keyboard is shift_frees_caps keyboard
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Enable CapsLock Key.
+4. Press Shift + 3 Key.
+5. Verify that the Caps lock indicator turned OFF
+6. Verify that the output results show ‘pass.’ in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_20**
+
+Test case for Shift by itself turns off (CapsOnly-5),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `20`
+- Product: `Windows`
+- Source files: `20.JSON`, `20.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC20
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install Shift_frees_caps Keyboard.
+3. CapsLock is currently off
+4. Currently active keyboard is shift_frees_caps keyboard
+(Be aware of limitations when testing this on virtual machines as noted above)
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Enable CapsLock key.
+4. Press and release the Shift key.
+5. Verify that the caps lock indicator turned OFF
+6. Verify there was no output should appear in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_21**
+
+Test case for Double_Processing_Firefox(TSF),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `21`
+- Product: `Windows`
+- Source files: `21.JSON`, `21.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC21
+
+
+Setup
+
+1. Install Keyman Developerlatest Stable build from Keyman.com Site.
+2. Install Firefox browser.
+3. Download and install EuroLatin (SIL) Keyboard.
+
+
+
+
+Action
+
+1. Double click on the Keyman Developer icon from the Desktop.
+2. Verify the Keyman Developer window opens.
+3. Click Project from the menu bar.
+4. Verify that the project Submenu opens.
+5. Click the ‘Open Project…’ option.
+6. Verify that the Open dialog box opens.
+7. Select ‘gff_amharic’ Source file.
+8. Click the Open button.
+9. Verify that the gff_amharic project opens in the Keyman Developer window.
+10. Click the Keyboards tab.
+11. Click the EuroLatin(SIL) blue link button.
+12. Verify that EuroLatin(SIL) .kmn dialog opens.
+13. Click the build tab.
+14. Verify that there is a panel ‘Web and Mobile Targets’ appearing on the screen.
+15. Click the ‘Test Keyboard on Web’ button.
+16. Verify that there should be some web addresses that include ‘http://localhost:8008’ appears in the web address pane.
+17. Click ‘http://localhost:8008’ from the pane.
+18. Click the ‘Open in browser’ button.
+19. Verify the Keyman Developer Keyboard Test Site opens in the Firefox browser.
+20. Click the Keyboard dropdown list.
+21. Select the EuroLatin Keyboard
+22. Verify that the Keyboard has been changed to the EuroLatin Keyboard.
+23. Type “a b c d Backspace” in the text area.
+24. Verify the output should show abc in the text area.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_22**
+
+Test case for Double_Processing_Searchbar(TSF),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `22`
+- Product: `Windows`
+- Source files: `22.JSON`, `22.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC22
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install Firefox browser.
+3. Download and install EuroLatin (SIL) Keyboard.
+
+
+
+
+Action
+
+1. Click the Keyman icon from the taskbar.
+2. Verify that the Keyman menu opens.
+3. Click EuroLatin (SIL) Keyboard.
+4. Verify that the EuroLatin Keyboard icon appears in the taskbar.
+5. Click the Windows Search bar.
+6. Type a b c d backspace in the windows search bar.
+7. Verify that the output should show ‘abc’ in the windows search bar.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_23**
+
+Test case for Double_Processing_Notepad (TSF),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `23`
+- Product: `Windows`
+- Source files: `23.JSON`, `23.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC23
+
+
+Setup
+
+1. Install Keyman Developer latest Stable build from Keyman.com Site.
+2. Install Keyman latest build.
+3. Download and install EuroLatin (SIL) Keyboard.
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Select the EuroLatin Keyboard
+6. Type a b c d in the Notepad.
+7. Verify the output should show ‘abcd’ in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_24**
+
+Test case for IMSAMPLE_INPUT,CONT,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `24`
+- Product: `Windows`
+- Source files: `24.JSON`, `24.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC24
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install imsample keyboard.
+3. In the Computer\HKEY_CURRENT_USER\SOFTWARE\Keyman\Keyman Engine\Active Keyboards\imsample, create New > DWORD(32-bit) key.
+4. Rename ‘ShowIMWindow’ to the new DWORD key.
+5. Set the Key value to 0.
+6. Create New>DWORD(32-bit) key.
+7. Rename ‘ShowIMWindowAlways’ to the new DWORD key.
+8. Set the Key value to 0
+9. Open Notepad.
+10. Type ‘he’ in the text area.
+11. Verify the Output should show h[1ɛ 2ɜ 3ə 4e 5ɘ].
+12. Type number 3.
+13. Verify that the displayed output should show ‘hə’
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Click IMTest Keyboard from the Keyman menu.
+6. Verify that the Keyboard icon appears in the task bar.
+7. Type f
+8. Type e
+9. Verify that f[1ɛ 2ɜ 3ə 4e 5ɘ] should be displayed in the Notepad app.
+10. Enter Backspace.
+11. Verify that the whole option menu including the square brackets [ ] should be deleted.
+12. Verify the output results should show ‘ f ‘ in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_25**
+
+Test case for IMSAMPLE_BACKSPACE:
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `25`
+- Product: `Windows`
+- Source files: `25.JSON`, `25.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC25
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install imsample keyboard.
+3. In the Computer\HKEY_CURRENT_USER\SOFTWARE\Keyman\Keyman Engine\Active Keyboards\imsample, create New > DWORD(32-bit) key.
+4. Rename ‘ShowIMWindow’ to the new DWORD key.
+5. Set the Key value to 0.
+6. Create New>DWORD(32-bit) key.
+7. Rename ‘ShowIMWindowAlways’ to the new DWORD key.
+8. Set the Key value to 0
+9. Open Notepad.
+10. Type ‘he’ in the text area.
+11. Verify the Output should show h[1ɛ 2ɜ 3ə 4e 5ɘ].
+12. Type number 3.
+13. Verify that the displayed output should show ‘hə’
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Click IMTest Keyboard from the Keyman menu.
+6. Verify that the Keyboard icon appears in the task bar.
+7. Type f
+8. Type e
+9. Verify that f[1ɛ 2ɜ 3ə 4e 5ɘ] should be displayed in the Notepad app.
+10. Enter Backspace.
+11. Verify that the whole option menu including the square brackets [ ] should be deleted.
+12. Verify the output results should show ‘ f ‘ in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_26**
+
+Test case for IMSAMPLE_KEYBOARD_IM_WINDOW,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `26`
+- Product: `Windows`
+- Source files: `26.JSON`, `26.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC26
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com Site.
+2. Install imsample keyboard.
+3. In the Computer\HKEY_CURRENT_USER\SOFTWARE\Keyman\Keyman Engine\Active Keyboards\imsample, create New > DWORD(32-bit) key.
+4. Rename ‘ShowIMWindow’ to the new DWORD key.
+5. Set the Key value to 1.
+6. Create New>DWORD(32-bit) key.
+7. Rename ‘ShowIMWindowAlways’ to the new DWORD key.
+8. Set the Key value to1
+9.This keyboard uses the letters aeom to allow IMX input. This time a IM window should display.
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Click IMTest Keyboard from the Keyman menu.
+6. Verify that the Keyboard icon appears in the task bar.
+7. Type t r y
+8. Enter key.
+9. Verify that the option menu appears on the screen.
+10. Click the 1st option.
+11. Verify that the output results show show ‘ try æ ‘
+12. Type 'm'
+13. Verify that the option menu appears on the screen.
+14. Select the 3rd ### option.
+15. Verify that the output results should show ‘ try æ### ‘
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_27**
+
+Test case for SIMPLIFIED_CHINESE_SINGLE,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `27`
+- Product: `Windows`
+- Source files: `27.JSON`, `27.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC27
+
+
+Setup
+
+1. Install Keymanlatest build from Keyman.com site.
+2. Install the Simplified Chinese Keyboard
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Click Simplified Chinese Keyboard from the Keyman menu.
+6. Verify that the Keyboard icon appears in the task bar.
+7. Type o -
+8. Verify that the IMX window should appear on the Screen.
+9. Click the 4th option
+10. Verify the output results 喔 should appear in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_28**
+
+Test case for SIMPLIFIED_CHINESE_MULTIPLE:
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `28`
+- Product: `Windows`
+- Source files: `28.JSON`, `28.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC28
+
+
+Setup
+
+1. Install Keymanlatest build from Keyman.com site.
+2. Install the Simplified Chinese Keyboard from Keyman site.
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Click Simplified Chinese Keyboard from the Keyman menu.
+6. Verify that the Keyboard icon appears in the task bar.
+7. Type h a n z i -
+8. Verify that the IMX window will appear and in the top left the letters hanzi should be present
+9. Click the 5th option
+10. Verify the output results 汉字变换 should appear in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_29**
+
+Test case for SIMPLIFIED_CHINESE_BACKSPACE_1:
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `29`
+- Product: `Windows`
+- Source files: `29.JSON`, `29.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC29
+
+
+Setup
+
+1. Install Keyman latest build from Keyman.com site.
+2. Install the Simplified Chinese Keyboard from Keyman site.
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Click Simplified Chinese Keyboard from the Keyman menu.
+6. Verify that the Keyboard icon appears in the task bar.
+7. Type h a n z i
+8. Verify that the IMX window will appear and in the top left the letters hanzi should be present
+9. Enter twice
+10. Verify that the IMX window should now have the top left letters of han in the Notepad app.
+11. Click the 5th option
+12. Verify the output results 汗 should appear in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_30**
+
+Test case for SIMPLIFIED_CHINESE_BACKSPACE_2:
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `30`
+- Product: `Windows`
+- Source files: `30.JSON`, `30.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC30
+
+
+Setup
+
+1. Install Keyman latest build from Keyman.com site.
+2. Install the Simplified Chinese Keyboard from Keyman site.
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Click Simplified Chinese Keyboard from the Keyman menu.
+6. Verify that the Keyboard icon appears in the task bar.
+7. Type h a n z i
+8. Verify that he IMX window will appear and in the top left the letters hanzi should be present.
+9. Click the 5th option
+10. Verify the output results 汉字变换 should appear in the Notepad app.
+11. Enter twice.
+12. Verify the output results 汉字 should appear in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_31**
+
+Test case for OPTION_STORE,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `31`
+- Product: `Windows`
+- Source files: `31.JSON`, `31.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC31
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com site.
+2. Install store_context Keyboard.
+3. Install 021 - options Keyboard.
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Click 021-options Keyboard from the Keyman menu.
+6. Verify that the 021-options keyboard icon appears in the task bar.
+7. Type a1a0a
+8. Verify the output results "no foo.foo.no foo" should appear in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_32**
+
+Test case for OUTPUT_KEYSTROKE (#10065)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `32`
+- Product: `Windows`
+- Source files: `32.JSON`, `32.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC32
+
+
+Setup
+
+1. Install Keymanlatest Stable build from Keyman.com site.
+2. Install store_context Keyboard.
+3. Install 043 - output and keystroke Keyboard.
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Click 043 - output and keystroke Keyboard from the Keyman menu.
+6. Verify that the 043 - output and keystroke Keyboard icon appears in the task bar.
+7. Type 123
+8. Verify the output results "abd3" should appear in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_33**
+
+Test case for OUTPUT_KEYSTROKE_INVALID_CONTEXT,(#10061),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `33`
+- Product: `Windows`
+- Source files: `33.JSON`, `33.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC33
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com site.
+2. Install store_context Keyboard.
+3. Install 043 - output and keystroke Keyboard.
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Click 043 - output and keystroke Keyboard from the Keyman menu.
+6. Verify that the 043 - output and keystroke Keyboard icon appears in the task bar.
+7. Type 1 2
+8. Type
+9. Type 3
+10. Verify the output results
+"abc
+3"
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_34**
+
+Test case for DEADKEY_AND_CONTEXT, (#10061),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `34`
+- Product: `Windows`
+- Source files: `34.JSON`, `34.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC34
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com site.
+2. Install store_context Keyboard.
+3. Install 045 - deadkey and context Keyboard.
+
+
+
+
+Action
+
+1. Double Click on Notepad icon from the desktop.
+2. Verify that the Notepad app opens
+3. Click the Keyman icon from the taskbar.
+4. Verify that the Keyman menu opens.
+5. Click 045 - deadkey and context keyboard from the Keyman menu.
+6. Verify that the 045 - deadkey and context keyboard icon appears in the task bar.
+7. Type y z Shift + /
+8. Verify the output results "correct" should appear in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_35**
+
+Test case for installing offline build (PR #10000):
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `35`
+- Product: `Windows`
+- Source files: `35.JSON`, `35.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC186
+
+
+Setup
+
+1. Download the latest alpha build from the link “https://downloads.keyman.com/windows/”
+
+
+
+
+Action
+
+1. Open the Command prompt on the Windows desktop via the “cmd” command.
+2. Change the directory path to where we downloaded the Keyman Alpha Build.
+3. Type the command : keyman latest version number.exe -o (say “17.0.210.exe -o”).
+4. Verify that the self extract process happened without any errors.
+5.) Verify the build was installed successfully without showing any error messages.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Click the Control Panel option.
+3. Click the ‘Uninstall a Program’ option.
+4. Select the installed Keyman version from the list.
+5. Click the Uninstall option.
+6. Verify that the keyman uninstallation was completed successfully.
+
+
+
+---
+
+**TEST_36**
+
+Test case for DEAD_CONTEXT_FRAME_KEY(#10061),
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `36`
+- Product: `Windows`
+- Source files: `36.JSON`, `36.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC187
+
+
+Setup
+
+1. Install Keyman latest Stable build from Keyman.com site.
+2. Install store_context Keyboard.
+3. Install 045 - deadkey and context Keyboard.
+4. Install Text Editor (64-bit).exe
+5. Install WordPad
+
+
+
+
+Action
+
+1. Open the TextEditor (64-bit) on the desktop.
+2. Verify that the TextEditor (64-bit) app opens
+3. Click 045 - deadkey and context keyboard from the Keyman menu.
+4. Verify that the 045 - deadkey and context keyboard icon appears in the task bar.
+5. Type y z
+6. Press
+7. Press
+8. Press
+9. Verify the output results "?" should appear in the TextEditor app.
+10. Open the WordPad on the desktop.
+11. Verify that the WordPad app opens
+12. Click 045 - deadkey and context keyboard from the Keyman menu.
+13. Verify that the 045 - deadkey and context keyboard icon appears in the task bar.
+14. Type ‘y z’
+15. Press
+16. Press
+17. Press
+18. Verify the output results "?" should appear in the WordPad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Task bar)
+2. Verify that the ‘Control panel’ appears in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the the Keyman Uninstallation completed successfully
+
+
+
+---
+
+**TEST_38**
+
+Test case for (windows): Chrome 86.0 no longer accepts backspace #3698,
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `38`
+- Product: `Windows`
+- Source files: `38.JSON`, `38.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC205
+
+
+Setup
+
+1. Install Keyman's latest Stable build from the Keyman.com site.
+2. Install Chrome browser.
+
+
+
+
+Action
+
+1. Open Chrome browser.
+2. Set Keyman keyboard.
+3. Verify the ‘English - EuroLatin(SIL)’ appeared on the system keyboard.
+4. Click the Search bar in the Chrome browser.
+5. Type ‘Keyman Testing’ in the Search bar.
+6. Press Backspace key.
+7. Verify it should delete the character to the left of the insertion point.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the Search bar (in Taskbar)
+2. Verify that the ‘Control panel’ appeared in the menu list.
+3. Click the Control panel option.
+4. Verify that the Control Panel dialog appeared.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully
+
+
+
+---
+
+**TEST_41**
+
+KMX_PROCESSOR_NON_COMPLIANT_TEST_CONTROL_1_GROUP_WINDOWS: TextEditor
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `41`
+- Product: `Windows`
+- Source files: `41.JSON`, `41.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC218
+
+
+Setup
+
+1. Install Keyman build.
+2. Install TextEdit app.
+
+
+
+
+Action
+
+1. Click on the TextEdit App icon from Windows Desktop.
+2. Verify that the TextEdit Application opens.
+3. Press `
+4. Verify it produces `.
+5. Type e
+6. Verify it produces è
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Windows
+2. Uninstall the TextEdit app.
+
+
+
+---
+
+**TEST_43**
+
+KMX_PROCESSOR_NON_COMPLIANT_TEST_FRAME_KEY_RESET_NOMARKERS_GROUP_WINDOWS: TextEditor
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `43`
+- Product: `Windows`
+- Source files: `43.JSON`, `43.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC220
+
+
+Setup
+
+1. Install Keyman build.
+2. Install TextEdit app.
+
+
+
+
+Action
+
+1. Click on the TextEdit App icon from Windows Desktop.
+2. Verify that the TextEdit Application opens.
+3. Press 1 \ \
+4. Verify it produces 1 \ \
+5. Press the "right arrow"
+6. Type 2
+7. Verify it produces 1//2
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Windows
+2. Uninstall the TextEdit app.
+
+
+
+---
+
+**TEST_46**
+
+KMX_PROCESSOR_COMPLIANT_TEST_FRAME_KEY_RESET_MARKERS_GROUP_WINDOWS: WordPad
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `46`
+- Product: `Windows`
+- Source files: `46.JSON`, `46.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC232
+
+
+Setup
+
+1. Install Keyman build.
+
+
+
+
+Action
+
+1. Click on the WordPad App icon from Windows Desktop.
+2. Verify that the WordPad Application opens.
+3. Press `
+4. Verify it produces `
+5. Press the "right arrow"
+6. Type e
+7. Verify it produces `e
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Windows
+
+
+
+---
+
+**TEST_48**
+
+KMX_PROCESSOR_COMPLIANT_TEST_SCROLLLOCK_KEY_NO_RESET_GROUP_WINDOWS: WordPad
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `48`
+- Product: `Windows`
+- Source files: `48.JSON`, `48.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC234
+
+
+Setup
+
+1. Install Keyman build.
+
+
+
+
+Action
+
+1. Click on the WordPad App icon from Windows Desktop.
+2. Verify that the WordPad Application opens.
+3. Press `
+4. Verify it produces `
+5. Press the "scroll lock"
+6. Type e
+7. Verify it produces è
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Windows
+
+
+
+---
+
+**TEST_51**
+
+LDML_PROCESSOR_NON_COMPLIANT_TEST_FRAME_KEY_RESET_NO_MARKERS_GROUP_WINDOWS: TextEditor
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `51`
+- Product: `Windows`
+- Source files: `51.JSON`, `51.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC246
+
+
+Setup
+
+1. Install Keyman build.
+2. Install TextEdit app.
+
+
+
+
+Action
+
+1. Click on the TextEdit App icon from Windows Desktop.
+2. Verify that the TextEdit Application opens.
+3. Press a
+4. Verify it produces a
+5. Press the "right arrow"(->)
+6. Press the SHIFT + 8
+7. Verify it produces a*
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Windows
+2. Uninstall the TextEdit app.
+
+
+
+---
+
+**TEST_53**
+
+LDML_PROCESSOR_NON_COMPLIANT_TEST_MODIFIER_TAP_NO_RESET_GROUP_WINDOWS: TextEditor
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `53`
+- Product: `Windows`
+- Source files: `53.JSON`, `53.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC248
+
+
+Setup
+
+1. Install Keyman build.
+2. Install TextEdit app.
+
+
+
+
+Action
+
+1. Click on the TextEdit App icon from Windows Desktop.
+2. Verify that the TextEdit Application opens.
+3. Press ^
+4. Verify it produces ^
+5. Press and Release CTRL key.
+6. Type e
+7. Verify it produces ê
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Windows
+2. Uninstall the TextEdit app.
+
+
+
+---
+
+**TEST_56**
+
+LDML_PROCESSOR_COMPLIANT_TEST_FRAME_KEY_RESET_NO_MARKERS_WINDOWS: WordPad
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `56`
+- Product: `Windows`
+- Source files: `56.JSON`, `56.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC261
+
+
+Setup
+
+1. Install Keyman build.
+2. Install WordPad app.
+
+
+
+
+Action
+
+1. Click on the WordPad App icon from Windows Desktop.
+2. Verify that the WordPad Application opens.
+3. Press a
+4. Verify it produces a
+5. Press the "right arrow"(->)
+6. Press the SHIFT + 8
+7. Verify it produces “Star”
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Windows
+2. Uninstall the WordPad app.
+
+
+
+---
+
+**TEST_58**
+
+LDML_PROCESSOR_COMPLIANT_TEST_MODIFIER_TAP_NO_RESET_GROUP_WINDOWS: WordPad
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `58`
+- Product: `Windows`
+- Source files: `58.JSON`, `58.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC263
+
+
+Setup
+
+1. Install Keyman build.
+2. Install WordPad app.
+
+
+
+
+Action
+
+1. Click on the WordPad App icon from Windows Desktop.
+2. Verify that the WordPad Application opens.
+3. Press ^
+4. Verify it produces ^
+5. Press and Release CTRL key.
+6. Type e
+7. Verify it produces ê
+
+
+
+
+Cleanup
+
+1. Uninstall Keyman build on the Windows
+2. Uninstall the WordPad app.
+
+
+
+---
+
+**TEST_61**
+
+feat(windows): add right modifier included in hotkey optional functionality #12259(TEST_LANGUAGE_HOTKEYS_LEFT_SIDE)
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `61`
+- Product: `Windows`
+- Source files: `61.JSON`, `61.html`
+
+
+
+**Description**
+
+Original TestLodge ID: TC295
+
+
+Setup
+
+1. Install Keyman's latest stable build from the Keyman.com site.(or state.keyman.com)
+2. Install Notepad (64-bit).exe
+
+
+
+
+Action
+
+1. Open the "Keyman configuration" dialog by pressing the icon from the Windows tray.
+2. Verify the "Keyman configuration" dialog appears.
+3. Navigate to the "Keyboard Layouts" tab.
+4. Installed the Tamil99 and IPA SIL keyboards by clicking the "Download keyboard" button.
+5. Verify the keyboards appear in the "Keyboard Layouts" tab.
+6. Navigate to the "HotKeys" tab
+7. Set the left side of the CTRL+G key to the Tamil keyboard.
+8. Set the left side of the CTRL_Shift+I key to the IPA SIL keyboard.
+9. Verify the key appears on the assigned keyboard.
+10. Open the Notepad application.
+11. Press the left side of the CTRL+G key in the Notepad app.
+12. Verify the keyboard switch to the Tamil keyboard.
+13. Enter some letters using the Tamil keyboard.
+14. Verify the Tamil text appears in the notepad app.
+15. Press the left side of the CTRL_Shift+I key in the note app.
+16. Verify the keyboard switch from Tamil to IPA SIL keyboard.
+17. Enter some IPA letters using the IPA SIL keyboard.
+18. Verify the IPA text appears in the Notepad app.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the search bar (in the taskbar)
+2. Verify that the ‘Control Panel’ appears in the menu list.
+3. Click the Control Panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully.
+
+
+
+---
+
+**TEST_304**
+
+kmshell switch handling for the installing state_TEST_INSTALL_UPDATE
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `304`
+- Product: `Windows`
+- Source files: `304.JSON`, `304.html`
+
+
+
+**Description**
+
+TC - feat(windows): kmshell switch handling for the installing state_TEST_INSTALL_UPDATE #12956
+
+
+Setup
+
+1. Install the older version of Keyman.
+2. Install the older version of any Keyman keyboard (e.g. Gff_Amharic 3.1.1 version)
+
+
+
+
+Action
+
+1. Start the Keyman.
+2. Open the Keyman Configuration dialog.
+3. Navigate to the "Keyboard Layouts tab".
+4. Verified that the installed keyboard shows an older version.
+5. Navigate to the "Update" tab.
+6. Open the "C:\Users"yourusername"\AppData\Local\Keyman\UpdateCache" folder.
+7. Open the regedit window (Computer\HKEY_CURRENT_USER\SOFTWARE\Keyman\Keyman Engine).
+8. WinR type regedit Go the current user key update state
+9. Press F5 to keep it refreshing it.
+10. The state will go to usDownloading to usInstalling at the same time keep checking the UpdateCache folder.
+11. Select the "update state" under the "Keyman Engine" in the regedit window.
+12. In Keyman Configuration: press the "Check for new updates" button.
+13. Verified that the "UpdateCache" folder is updating or adding files
+14. On Regedit window: Verified that the state is changes from usUpdateAvailable--> usDownloading --> usWaitingRestart
+15. Click the "Apply update now" button.
+16. Verified that the "Keyman Update" popup
+17. Click the "Update" button.
+18. Verified that the "UpdateCache" folder has the cache.json and the keyboard gff_amharic. and a Keyman.version.exe if available.
+19. On Regedit window: the state is changing to "usldle"
+20. Restart the machine by clicking the "Yes" button on the "Keyman setup" dialog.
+21. Login to the machine.
+22. Click ˘the "Yes" button on the "Do you want to allow to make the change?" dialog.
+23. Keyman Installation is completed successfully.
+24. Open the configuration window.
+25. On the Keyboard Layouts: Verified that the gff_amharic keyboard is updated.
+26. On the Update Tab: Verified there are no updates available.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the search bar (in the task bar)
+2. Verify that the ‘Control Panel’ appears in the menu list.
+3. Click the Control Panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully.
+
+
+
+---
+
+**TEST_309**
+
+Handle keyboard package not downloaded
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `309`
+- Product: `Windows`
+- Source files: `309.JSON`, `309.html`
+
+
+
+**Description**
+
+TC - fix(windows): handle keyboard package not downloaded #12948
+
+
+Setup
+
+1. Install the latest version of Keyman.
+2. Install the older version of any Keyman keyboard (e.g. Gff_Amharic 3.1.1 version)
+
+
+
+
+Action
+
+1. Start the Keyman.
+2. Open the Keyman Configuration dialog.
+3. Navigate to the "Keyboard Layouts tab".
+4. Verified that the installed keyboard shows an older version.
+5. Navigate to the "Update" tab.
+6. Verified that the "Apply update now" button appeared disabled.
+7. Verified that the "Check for new updates" button appeared enabled.
+8. Press the "Check for new updates" button.
+9. Verified that the newer version appeared in the "Updated component" column for GFF's Keyboard and Keyman.
+10. Verified that the "Apply update now" button appeared in the enabled state.
+11. Click the "Apply update now" button to upgrade the Keyman version.
+12. Verified that the "Keyman update" dialog appeared.
+13. Click the "Update now" button on the dialog.
+14. Verified that the "Do you want to allow this app to make changes to your device?" dialog appeared
+15. Click the "Yes" button on that dialog.
+16. Verified that no crash appeared on the Keyman configuration dialog.
+17. Verified that the "Keyman Setup" dialog appeared.
+18. Click the "Yes" button on the "Keyman Setup" dialog.
+19. Verified that the machine restarted.
+20. Login to the machine.
+21. Again, verified that the "Do you want to allow this app to make changes to your device?" dialog appeared.
+22. Click the "Yes" button.
+23. Open the "Keyman Configuration".
+24. Navigate to the "Update" tab.
+25. Press the "Check for new updates" button.
+26. Verified that no update appears for the keyboard.
+27. Navigate to the "Keyboard Layouts tab".
+28. Verified that the Keyman keyboard updated with the latest version.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the search bar (in the task bar)
+2. Verify that the ‘Control Panel’ appears in the menu list.
+3. Click the Control Panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully.
+
+
+
+---
+
+**TEST_324**
+
+UI layout for update tab_TEST_UI_UPDATES_KBD
+
+Status: `Active`
+
+
+Metadata
+
+- Source ID: `324`
+- Product: `Windows`
+- Source files: `324.JSON`, `324.html`
+
+
+
+**Description**
+
+TC - feat(windows): UI layout for update tab_TEST_UI_UPDATES_KBD #12840
+
+
+Setup
+
+1. Install the latest version of Keyman.
+2. Install the SIL_Euro_Latin 3.0.2 version keyboard. (older version)
+3. Installed the Gff_Amharic 3.1.1 version keyboard. (older version)
+
+
+
+
+Action
+
+1. Start the Keyman.
+2. Open the Keyman Configuration dialog.
+3. Navigate to the "Keyboard Layouts tab".
+4. Verify that the installed keyboard shows an older version.
+5. Navigate to the "Update" tab.
+6. Verify that the "Apply update now" button appears disabled.
+7. Verify that the "Check for new updates" button appears enabled.
+8. Press the "Check for new updates" button.
+9. Verify that the "Update Component", "Old version" and "Size" columns appeared.
+10. Verify that the newer version appears in the "Updated component" column for GFF's and SIL_Euro_Latin keyboard and Keyman.
+11. Verify that the "Apply update now" button appears in the enabled state.
+12. Verify that the "Updates are available which will be applied when Windows is next restarted." This message appears above the columns.
+
+
+
+
+Cleanup
+
+1. Type ‘Control panel’ in the search bar (in the task bar)
+2. Verify that the ‘Control Panel’ appears in the menu list.
+3. Click the Control Panel option.
+4. Verify that the Control Panel dialog appears.
+5. Click the ‘Uninstall a Program’ option.
+6. Verify that the Programs and Features dialog box opens.
+7. Select the installed Keyman version from the list.
+8. Click the Uninstall option.
+9. Verify that the Keyman Uninstallation was completed successfully.
+
+