test(windows): Regression Test Report 18.0.158 Alpha (14failures)

[sillsdev-dondillard]

Test Report for Keyman 18.0.158 Alpha Windows
Results 

 Expected Start Date 12/2/2024
 Actual Start Date 12/2/2024

 Overall Results: 89% (110/124 passed)

Regression Tests
 Windows 10 89% (55/62 passed)
 Windows 11 89% (55/62 passed)

Issues Found:

• bug(windows): Chromium typing issue with Spotify for Podcasters (slate.js) #8594

TC-39 Test case for bug(windows): Chromium typing issue with Spotify for Podcasters
 "ഇംഗ്ലീഷ്" output does not appear when typing the "imgleesh" for new episode podcast "ഇംഗ്ല്െീസ്ഷ്" this output appeared. So, the test case failed at step 11.

• fix(core): reset on frame keys 🙀  #11172

TC-44 KMX_PROCESSOR_NON_COMPLIANT_TEST_SCROLLLOCK_KEY_NO_RESET_GROUP_WINDOWS: TextEditor 
  "è" is expected output. But we got the output as"`e"  at step 7. 

TC-48 KMX_PROCESSOR_COMPLIANT_TEST_SCROLLLOCK_KEY_NO_RESET_GROUP_WINDOWS:  "è" is expected output.  But we got the output as"`e"  at step 7.  So we failed this test case. 

TC-52 LDML_PROCESSOR_NON_COMPLIANT_TEST_FRAME_SCROLL_LOCK_NO_RESET_GROUP_WINDOWS10: TextEditor
 "ê" is expected output.  But we got the output as "^e" . 

TC-57 LDML_PROCESSOR_COMPLIANT_TEST_FRAME_SCROLL_LOCK_NO_RESET_WINDOWS: WordPad
 "ê" is expected output.  But we got the output as "^e".So we failed this test case.

• bug(developer): The web server does not start after clicking the "Test Lexical Model". #12673

TC-21 Test case for Double_Processing_Firefox(TSF), 
The web server does not start after clicking the "Test keyboard on web". Unable to start the server in the developer tool and not appearing in the browser. This test case failed at step 16. 

• bug(windows): text output does not appear in the notepad when typing the "try + click 1" using the "IMSample" keyboard. #12850

TC-26 Test case for IMSAMPLE_KEYBOARD_IM_WINDOW,
 ‘ try æ ‘ letters does not show the result and test case is failed at step 11.

[mcdurdin]

@rc-swag, process here is to review the failing cases, determine if any of them impact beta, then can close this again once we have other open issues tracking those failures (unless already resolved, of course).