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

WIP: macOS implementation of keyboard, mouse, AxElementInfo and Application #841

Open
wants to merge 59 commits into
base: macos
Choose a base branch
from

Conversation

vasily-v-ryabov
Copy link
Contributor

This is initial implementation of the most basic classes for macOS backend "ax".

Any comments and suggestions are highly appreciated.

Big TODOs:

  • Travis CI automation is coming (currently working on macOS 10.11 usage, test apps are built as .dmg packages).
  • AxWrapper and derived classes (even not started yet).

Thanks:

zemtsov-artem and others added 30 commits April 14, 2019 15:04
1.Keyboard module + unit tests
2.Mouse module + unit tests.
Also travis yml file updated to support OS tests.
# Conflicts:
#	pywinauto/application.py
#	pywinauto/unittests/test_keyboard.py

pass

class ApplicationEspecialTestCases(unittest.TestCase):
Copy link
Contributor

Choose a reason for hiding this comment

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

A small suggestion, so if these tests for start/end, let's than call it ApplicationStartEndTestCases.

"""
Unit tests for the application.Application class
There are test cases which has unique start/end logic
"""
Copy link
Contributor

Choose a reason for hiding this comment

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

Even for these special cases it'd be better to have a proper cleanup. Remember that if test fails we don't want any leftovers.

def setUp(self):
    self.app = Application()

def tearDown(self):
    self.app.kill()

@abrichr
Copy link

abrichr commented May 6, 2023

Any update on this? I see there is a related issue that was created after this PR was opened: #1137

The branch currently says:

This branch is 59 commits ahead, 219 commits behind pywinauto:atspi.

Is it worth continuing from here or starting fresh?

@vasily-v-ryabov
Copy link
Contributor Author

@abrichr the most fresh branch is in PR #1213. It is waiting for final polishing. But there is not ETA unfortunately.

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.

None yet

6 participants