Skip to content

Emoji panel and clipboard history system tests#12487

Closed
seanbudd wants to merge 16 commits into
masterfrom
emojiPanelSystemTests
Closed

Emoji panel and clipboard history system tests#12487
seanbudd wants to merge 16 commits into
masterfrom
emojiPanelSystemTests

Conversation

@seanbudd

@seanbudd seanbudd commented May 31, 2021

Copy link
Copy Markdown
Member

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):

  • Opening clipboard history and navigating it
  • Opening emoji panel, ensure the first item read is an emoji. (Note: excluded, see known issues)
  • Toggling between emoji panel and clipboard history without closing them. (Note: excluded, see known issues)
  • Searching for emoji items, navigating them. (Note: excluded, see known issues)

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:

  • Pull Request description is up to date.
  • Unit tests.
  • System (end to end) tests.
  • Manual testing.
  • User Documentation.
  • Change log entry.
  • Context sensitive help for GUI changes.
  • UX of all users considered:
    • Speech
    • Braille
    • Low Vision
    • Different web browsers

@seanbudd seanbudd requested a review from a team as a code owner May 31, 2021 08:37
@seanbudd seanbudd requested a review from michaelDCurran May 31, 2021 08:37
@seanbudd seanbudd changed the title Emoji panel system tests Emoji panel and clipboard history system tests May 31, 2021
@josephsl

Copy link
Copy Markdown
Contributor

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.

@AppVeyorBot

Copy link
Copy Markdown
  • PASS: Translation comments check.
  • PASS: Unit tests.
  • PASS: Lint check.
  • FAIL: System tests. See test results for more information.
  • Build (for testing PR)

See test results for failed build of commit 82c07fa303

@seanbudd seanbudd marked this pull request as draft May 31, 2021 08:57
@AppVeyorBot

Copy link
Copy Markdown
  • PASS: Translation comments check.
  • PASS: Unit tests.
  • PASS: Lint check.
  • FAIL: System tests. See test results for more information.
  • Build (for testing PR)

See test results for failed build of commit 011f36421f

@LeonarddeR

Copy link
Copy Markdown
Collaborator

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.

@josephsl

josephsl commented Jun 1, 2021 via email

Copy link
Copy Markdown
Contributor

@seanbudd

seanbudd commented Jun 3, 2021

Copy link
Copy Markdown
Member Author

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.

Would it be troublesome to just include --exclude windowsTests if you wish to ignore these? Having expected failures locally shouldn't really be an issue if it is clear why they are failing. I think ideally we should make a separate robot args files for appveyor and various developer environments. As it stands now, system tests are used mostly by appveyor. Locally, I tend to only run tests relevant to the work I'm doing.

@seanbudd

seanbudd commented Jun 3, 2021

Copy link
Copy Markdown
Member Author

I've added some more explicit tags so that you can --exclude emojiPanel and --exclude clipboard instead if preferred.

@seanbudd seanbudd force-pushed the emojiPanelSystemTests branch from d3ad0a3 to faf01ff Compare June 3, 2021 00:45
@AppVeyorBot

Copy link
Copy Markdown
  • PASS: Translation comments check.
  • PASS: Unit tests.
  • PASS: Lint check.
  • FAIL: System tests. See test results for more information.
  • Build (for testing PR)

See test results for failed build of commit 7a878dfa7d

@seanbudd seanbudd marked this pull request as draft June 14, 2021 09:06
@seanbudd

Copy link
Copy Markdown
Member Author

I want to change this to use our notepad system tests when that is merged in on #11856

@AppVeyorBot

Copy link
Copy Markdown

See test results for failed build of commit dba58804c7

@seanbudd seanbudd force-pushed the emojiPanelSystemTests branch from 373848a to 9aec4b6 Compare July 7, 2021 07:53
@AppVeyorBot

Copy link
Copy Markdown

See test results for failed build of commit 1097d6edff

@AppVeyorBot

Copy link
Copy Markdown

See test results for failed build of commit ec35121eda

@AppVeyorBot

Copy link
Copy Markdown

See test results for failed build of commit b7c1fa0af4

@AppVeyorBot

Copy link
Copy Markdown

See test results for failed build of commit acf63d4b71

@AppVeyorBot

Copy link
Copy Markdown

See test results for failed build of commit 21685cfecd

@seanbudd seanbudd closed this Sep 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants