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

WinAppDriver test infrastructure #846

Closed
crutkas opened this issue Dec 3, 2019 · 6 comments
Closed

WinAppDriver test infrastructure #846

crutkas opened this issue Dec 3, 2019 · 6 comments
Assignees
Labels
Area-Tests issues that relate to tests Cost-Large Large work item - 3+ days worth of work (chances are needs to be broken down) Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release.

Comments

@crutkas
Copy link
Member

crutkas commented Dec 3, 2019

We can do unit testing on a lot of parts, but true app testing is needed. We will enable WinAppDriver testing in common scenarios to verify end to end scenarios continue to work.

@crutkas crutkas added the Area-Tests issues that relate to tests label Dec 3, 2019
@crutkas crutkas added this to the 0.16 milestone Dec 3, 2019
@enricogior enricogior removed this from the 20.02 release milestone Feb 24, 2020
@crutkas
Copy link
Member Author

crutkas commented Mar 10, 2020

@SeraphimaZ what is the game plan for what is being implemented here? what items are planned / phases to get checked in?

@SeraphimaZykova
Copy link
Collaborator

@crutkas I’ve done some tests for fancy zones settings: I interact with elements and check if they are saved correctly in settings file. I’m planning to finish this part today.
After that I was planning to do same thing with editor: create and modify zone layouts and check settings file. It would take about a week I think.
Then I’ll do tests for applying zones and interacting with them with different settings, there should be many tests and it’ll take a time.

@crutkas
Copy link
Member Author

crutkas commented Mar 11, 2020

Rather than once big PR, let’s do a few smaller ones. I would love to see this checked in and start playing with it.

@enricogior
Copy link
Contributor

Sure, we can do it.

@enricogior enricogior added Status-In progress This issue or work-item is under development Cost-Large Large work item - 3+ days worth of work (chances are needs to be broken down) labels Mar 17, 2020
@SeraphimaZykova
Copy link
Collaborator

SeraphimaZykova commented Mar 18, 2020

Current progress with tests:

Tray tests:

  • Open settings by clicking on tray icon
  • Open settings with context menu
  • Exit PowerToys

FancyZones Settings: all tests interact with elements and check saved settings file

  • Click toggles
  • Set zone highlight opacity
    • valid value
    • negative value
    • too big value
    • non-digit characters
    • insert from clipboard
  • Change highlight opacity by clicking increase/decrease buttons
  • Send to rgb/hex inputs different symbols and combinations
  • Write excluded apps
  • Set hotkey combinations
  • Test exit/save/cancel buttons if there were unsaved changes on closing

Editor:

  • Open editor by clicking button/by hotkey
    • without settings file
    • without settings folder
    • with valid settings file
    • with valid settings file contained cyrillic characters
    • with invalid settings file
    • with cropped settings file
  • Increase/decrease zone count, check min and max possible values
  • Test if settings are saved in file properly
    • Show spacing checked/unchecked
    • Space around zone saved correctly
  • Space around zone possible input values
  • Edit templates, check settings files
  • Apply templates, check settings files
  • Create new different custom layouts
  • Remove custom layout
  • Edit custom layout
    • resize canvas zones
    • resize grid zones
    • create splitters for grid layout
    • merge zones in grid layout

@yevhenii44-zz yevhenii44-zz self-assigned this Mar 19, 2020
@enricogior enricogior added Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release. and removed Status-In progress This issue or work-item is under development labels Mar 26, 2020
@enricogior
Copy link
Contributor

The core of the WinAppDriver testing is completed, more test are under development but we can consider this work item done.
We should move the test list to a wiki page and continue adding test cases there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Tests issues that relate to tests Cost-Large Large work item - 3+ days worth of work (chances are needs to be broken down) Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release.
Projects
None yet
Development

No branches or pull requests

4 participants