Emoji panel and clipboard history system tests#12487
Conversation
|
CC @michaelDCurran as it could open up a possibility to test IME candidates support in the future (IME candidates also covers hardware keyboard input suggestions, but not sure how to get that going in the future). Thanks. |
See test results for failed build of commit 82c07fa303 |
See test results for failed build of commit 011f36421f |
|
Could we ensure that these tests never run on older versions, i.e. Windows 8.1 and older? This doesn't matter for appveyor, but for manual testing, exclusion would be appreciated. |
|
Hi, I think perhaps a condition flag should be specified in Robot somehow that will exclude certain tests from being performed if winVersion.getWinVer() </>= winVersion.WIN*. For Windows Insider Preview, we need to rely on winVersion.getWinVer().build as we won’t know what the final build number will be until it ships to beta channel. Thanks.
|
Would it be troublesome to just include |
|
I've added some more explicit tags so that you can |
d3ad0a3 to
faf01ff
Compare
See test results for failed build of commit 7a878dfa7d |
|
I want to change this to use our notepad system tests when that is merged in on #11856 |
See test results for failed build of commit dba58804c7 |
373848a to
9aec4b6
Compare
See test results for failed build of commit 1097d6edff |
See test results for failed build of commit ec35121eda |
See test results for failed build of commit b7c1fa0af4 |
See test results for failed build of commit acf63d4b71 |
See test results for failed build of commit 21685cfecd |
Link to issue number:
None
Summary of the issue:
To aid reviewing future work on the emoji panel and clipboard history and #11485, system tests for these Windows features are needed.
Description of how this pull request fixes the issue:
Introduces system tests which (covers most of the manual testing in #11485):
Testing strategy:
See PR builds. Run system tests locally as well as windows versions implement these features differently.
Known issues with pull request:
As discussed on #11485 (comment), Windows versions implement these features differently and Microsoft plans to update them further. As a result, the AppVeyor tests may need to be updated or excluded if they start to fail and work on fixing the emoji panel or clipboard history can be prioritised. Additionally, these tests ideally should be run on various Windows versions to ensure nothing has broken across implementations.
For example: searching for emojis is not implemented on the AppVeyor implementation of the emoji panel. As such, this test fails and needs to be excluded.
https://ci.appveyor.com/project/NVAccess/nvda/builds/39392852/tests
Emoji related tests need to be excluded until #11485, as the emoji panel does not always announce an emoji when opening the
emoji panel. This can be observed with this build, where 2 tests involve opening the emoji panel and expecting an emoji announced but only one passes. https://ci.appveyor.com/project/NVAccess/nvda/builds/39404151/tests
Change log entries:
None needed
Code Review Checklist: