Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(windows): removed cached context windows engine #10065

Merged
merged 7 commits into from
Nov 30, 2023

Conversation

rc-swag
Copy link
Contributor

@rc-swag rc-swag commented Nov 23, 2023

Fixes #10052

User Testing

I have taken the context and store test for the acceptance tests on the wiki. We don't need the stores will just use the
043 - output and keystroke.kmx and 045 - deadkey and context.kmx
Use the text editor available on this PR in the User Testing section

  • GROUP_TEXT_EDITOR
  • GROUP_WORD_PAD (TSF)

Test cases

click to expand

The key referred to as "enter" is alternatively labelled "return" on some keyboards.

Keyboards for the following test are found in the zip file store_context_kbd.zip

TEST_OUTPUT_KEYSTROKE

  1. Install 043 - output and keystroke.kmx
  2. Open Text Editor
  3. Select 043 - output and keystroke.kmx as the current keyboard.
  4. Type 123

Expected Result: "abd3"

TEST_OUTPUT_KEYSTROKE_INVALID_CONTEXT

  1. If not installed from the previous test - Install 043 - output and keystroke.kmx
  2. Open Text Editor
  3. Select 043 - output and keystroke.kmx as the current keyboard.
  4. Type 12Enter3

Expected Result:
"abc
3"

TEST_OUTPUT_KEYSTROKE_CONTEXT_FRAME_KEY

  1. If not installed from the previous test - Install 043 - output and keystroke.kmx
  2. Open Text Editor
  3. Select 043 - output and keystroke.kmx as the current keyboard.
  4. Type 12left arrow keyright arrow key3

Expected Result WordPad: "abd3"

Expected Result TextEditor: "abc3"

TEST_DEADKEY_AND_CONTEXT

  1. Install 045 - deadkey and context.kmx
  2. Open Text Editor
  3. Select 045 - deadkey and context.kmx as the current keyboard.
  4. Type yzShift+/

Expected Result: "correct"

TEST_DEAD_CONTEXT_FRAME_KEY

  1. Install 045 - deadkey and context.kmx
  2. Open Text Editor
  3. Select 045 - deadkey and context.kmx as the current keyboard.
  4. Type yz left arrow keyright arrow keyShift+/

Expected Result: "<ab>?"

Removed the cached context from the windows engine
@keymanapp-test-bot keymanapp-test-bot bot added the user-test-missing User tests have not yet been defined for the PR label Nov 23, 2023
@keymanapp-test-bot
Copy link

keymanapp-test-bot bot commented Nov 23, 2023

User Test Results

Test specification and instructions

  • ✅ GROUP_TEXT_EDITOR:

    5 tests PASSED
    • TEST_OUTPUT_KEYSTROKE (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Unzipped then installed the store_context keyboards using Keyman Configuration dialog. 2. Installed Text Editor 64 (EC Test App) from the PR build then Opened it. 3. Selected 043 - output and keystroke.kmx as the current keyboard. 4. Typed "123". Verified that "abd3" appeared on the Text Editor.
    • TEST_OUTPUT_KEYSTROKE_INVALID_CONTEXT (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Opened the Text Editor (64 bit). 2. Selected 043 - output and keystroke.kmx as the current keyboard. 3. Typed "12". Pressed te key. Typed "3". Verified that (notes)
    • TEST_OUTPUT_KEYSTROKE_CONTEXT_FRAME_KEY (PASSED): notes
    • TEST_DEADKEY_AND_CONTEXT (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Opened the Text Editor (64 bit). 2. Selected 045 - deadkey and context.kms as the current keyboard. 3. Typed "yz shift+/". Verified that the text "correct" appear as the output.
    • TEST_DEAD_CONTEXT_FRAME_KEY (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Opened the Text Editor (64 bit). 2. Selected 045 - deadkey and context.kms as the current keyboard. 3. Typed "yz lef arrow key right arrow key shift+/". Verified that "?" text appear as the output. (notes)
  • ✅ GROUP_WORD_PAD: (TSF)

    5 tests PASSED
    • TEST_OUTPUT_KEYSTROKE (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Unzipped then installed the store_context keyboards using Keyman Configuration dialog. 2. Opened WordPad. 3. Selected 043 - output and keystroke.kmx as the current keyboard. 4. Typed "123". Verified that "abd3" appeared on the Text Editor.
    • TEST_OUTPUT_KEYSTROKE_INVALID_CONTEXT (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Opened WordPad. 2. Selected 043 - output and keystroke.kmx as the current keyboard. 3. Typed "12". Pressed te key. Typed "3". Verified that (notes)
    • TEST_OUTPUT_KEYSTROKE_CONTEXT_FRAME_KEY (PASSED): Tested with the attached PR build (Keyman 17.0.220-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Installed the 043 - output and keystroke.kmx keyboard. 2. Opened the WordPad app. 3. Followed the steps mentioned in the instructions and show the expected result. (notes)
    • TEST_DEADKEY_AND_CONTEXT (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Opened WordPad. 2. Selected 045 - deadkey and context.kms as the current keyboard. 3. Typed "yz shift+/". Verified that the text "correct" appears as the output.
    • TEST_DEAD_CONTEXT_FRAME_KEY (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Opened WordPad. 2. Selected 045 - deadkey and context.kms as the current keyboard. 3. Typed "yz lef arrow key right arrow key shift+/". Verified that "?" text appears as the output. (notes)

Test Artifacts

@rc-swag rc-swag marked this pull request as ready for review November 23, 2023 12:03
Copy link
Member

@mcdurdin mcdurdin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove this file from the PR -- Its changes are result of the build and not relevant 😁

windows/src/engine/keyman32/appint/aiTIP.h Outdated Show resolved Hide resolved
windows/src/engine/keyman32/kmprocess.cpp Outdated Show resolved Hide resolved
windows/src/engine/keyman32/kmprocess.cpp Outdated Show resolved Hide resolved
@darcywong00 darcywong00 modified the milestones: A17S26, A17S27 Nov 27, 2023
@keymanapp-test-bot keymanapp-test-bot bot added has-user-test user-test-required User tests have not been completed and removed user-test-missing User tests have not yet been defined for the PR labels Nov 28, 2023
@bharanidharanj
Copy link

Test Results

GROUP_TEXT_EDITOR:

  • TEST_OUTPUT_KEYSTROKE (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Unzipped then installed the store_context keyboards using Keyman Configuration dialog. 2. Installed Text Editor 64 (EC Test App) from the PR build then Opened it. 3. Selected 043 - output and keystroke.kmx as the current keyboard. 4. Typed "123". Verified that "abd3" appeared on the Text Editor.

  • TEST_OUTPUT_KEYSTROKE_INVALID_CONTEXT (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Opened the Text Editor (64 bit). 2. Selected 043 - output and keystroke.kmx as the current keyboard. 3. Typed "12". Pressed te key. Typed "3". Verified that
    "abc
    3" appeared on the Text Editor.

  • TEST_DEADKEY_AND_CONTEXT (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Opened the Text Editor (64 bit). 2. Selected 045 - deadkey and context.kms as the current keyboard. 3. Typed "yz shift+/". Verified that the text "correct" appear as the output.

  • TEST_DEAD_CONTEXT_FRAME_KEY (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Opened the Text Editor (64 bit). 2. Selected 045 - deadkey and context.kms as the current keyboard. 3. Typed "yz lef arrow key right arrow key shift+/". Verified that "?" text appear as the output.

..Text Editor Output

@bharanidharanj
Copy link

Test Results

GROUP_WORD_PAD: (TSF)

  • TEST_OUTPUT_KEYSTROKE (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Unzipped then installed the store_context keyboards using Keyman Configuration dialog. 2. Opened WordPad. 3. Selected 043 - output and keystroke.kmx as the current keyboard. 4. Typed "123". Verified that "abd3" appeared on the Text Editor.

  • TEST_OUTPUT_KEYSTROKE_INVALID_CONTEXT (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Opened WordPad. 2. Selected 043 - output and keystroke.kmx as the current keyboard. 3. Typed "12". Pressed te key. Typed "3". Verified that
    "abc
    3" appeared on the Text Editor.

  • TEST_DEADKEY_AND_CONTEXT (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Opened WordPad. 2. Selected 045 - deadkey and context.kms as the current keyboard. 3. Typed "yz shift+/". Verified that the text "correct" appears as the output.

  • TEST_DEAD_CONTEXT_FRAME_KEY (PASSED): Tested with the attached PR build (keyman 17.0.216-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Opened WordPad. 2. Selected 045 - deadkey and context.kms as the current keyboard. 3. Typed "yz lef arrow key right arrow key shift+/". Verified that "?" text appears as the output.

..in WordPad Editor

@keymanapp-test-bot keymanapp-test-bot bot removed the user-test-required User tests have not been completed label Nov 28, 2023
@bharanidharanj
Copy link

FYI, I got an error message during install the attached PR build (Keyman 17.0.216-alpha-test-10065) on Windows 10 OS. When I press the "Retry" button multiple times, the installation process proceeds further. Just want to bring it to your attention.

..error message during Keyman installation

@mcdurdin
Copy link
Member

FYI, I got an error message during install the attached PR build (Keyman 17.0.216-alpha-test-10065) on Windows 10 OS. When I press the "Retry" button multiple times, the installation process proceeds further. Just want to bring it to your attention.

This is the same issue as you saw earlier -- issues with the keyman.com servers being slow. I am investigating.

@keymanapp-test-bot keymanapp-test-bot bot added the user-test-required User tests have not been completed label Nov 28, 2023
@rc-swag
Copy link
Contributor Author

rc-swag commented Nov 29, 2023

@bharanidharanj I made a typo leaving out the '_' in TEST_OUTPUT_KEYSTROKE_CONTEXT_FRAME_KEY which means it didn't get converted into a checkbox test. I decided to quickly test it myself and it fails! I will have to dig into this later today.

@rc-swag
Copy link
Contributor Author

rc-swag commented Nov 29, 2023

Test Results

GROUP_TEXT_EDITOR:

  • TEST_OUTPUT_KEYSTROKE_CONTEXT_FRAME_KEY (PASS): notes

GROUP_WORD_PAD: (TSF)

  • TEST_OUTPUT_KEYSTROKE_CONTEXT_FRAME_KEY (FAILED): The result is abc3 which suggests getting the context from TSF apps and setting it in the core is failing.

@keymanapp-test-bot keymanapp-test-bot bot added user-test-failed and removed user-test-required User tests have not been completed labels Nov 29, 2023
@rc-swag
Copy link
Contributor Author

rc-swag commented Nov 30, 2023

@keymanapp-test-bot retest GROUP_WORD_PAD TEST_OUTPUT_KEYSTROKE_CONTEXT_FRAME_KEY
@bharanidharanj The failed test is ready for re-test you will need to download the keyman for windows build on this PR again.

@keymanapp-test-bot keymanapp-test-bot bot added user-test-required User tests have not been completed and removed user-test-failed labels Nov 30, 2023
@bharanidharanj
Copy link

Test Results

GROUP_WORD_PAD: (TSF)

  • TEST_OUTPUT_KEYSTROKE_CONTEXT_FRAME_KEY (PASSED): Tested with the attached PR build (Keyman 17.0.220-alpha-test-10065) on Windows 10 OS and here is my observation: 1. Installed the 043 - output and keystroke.kmx keyboard. 2. Opened the WordPad app. 3. Followed the steps mentioned in the instructions and show the expected result.

..in WordPad

@keymanapp-test-bot keymanapp-test-bot bot removed the user-test-required User tests have not been completed label Nov 30, 2023
@rc-swag rc-swag merged commit 864f378 into master Nov 30, 2023
17 checks passed
@rc-swag rc-swag deleted the chore/windows/10052/remove-cached-context branch November 30, 2023 22:33
@keyman-server
Copy link
Collaborator

Changes in this pull request will be available for download in Keyman version 17.0.221-alpha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

chore(windows): remove cached context management from Keyman Engine
5 participants