An extension library for adding Selenium 3.0 draft and Mobile JSON Wire Protocol Specification draft functionality to the Python language bindings, for use with the mobile testing framework Appium.
Since v1.0.0, only Python 3 is supported
There are three ways to install and use the Appium Python client.
-
Install from PyPi, as 'Appium-Python-Client'.
pip install Appium-Python-Client
You can see the history from here
-
Install from source, via PyPi. From 'Appium-Python-Client', download and unarchive the source tarball (Appium-Python-Client-X.X.tar.gz).
tar -xvf Appium-Python-Client-X.X.tar.gz cd Appium-Python-Client-X.X python setup.py install -
Install from source via GitHub.
git clone git@github.com:appium/python-client.git cd python-client python setup.py install
The Appium Python Client is fully compliant with the Selenium 3.0 specification draft, with some helpers to make mobile testing in Python easier. The majority of the usage remains as it has been for Selenium 2 (WebDriver), and as the official Selenium Python bindings begins to implement the new specification that implementation will be used underneath, so test code can be written that is utilizable with both bindings.
To use the new functionality now, and to use the superset of functions, instead of including the Selenium webdriver module in your test code, use that from Appium instead.
from appium import webdriverFrom there much of your test code will work with no change.
As a base for the following code examples, the following sets up the UnitTest environment:
# Android environment import unittest from appium import webdriver desired_caps = dict( platformName='Android', platformVersion='10', automationName='uiautomator2', deviceName='Android Emulator', app=PATH('../../../apps/selendroid-test-app.apk') ) self.driver = webdriver.Remote('http://localhost:4723/wd/hub', desired_caps) el = self.driver.find_element_by_accessibility_id('item') el.click()# iOS environment import unittest from appium import webdriver desired_caps = dict( platformName='iOS', platformVersion='13.4', automationName='xcuitest', deviceName='iPhone Simulator', app=PATH('../../apps/UICatalog.app.zip') ) self.driver = webdriver.Remote('http://localhost:4723/wd/hub', desired_caps) el = self.driver.find_element_by_accessibility_id('item') el.click()If your Selenium/Appium server decorates the new session capabilities response with the following keys:
directConnectProtocoldirectConnectHostdirectConnectPortdirectConnectPath
Then python client will switch its endpoint to the one specified by the values of those keys.
import unittest from appium import webdriver desired_caps = dict( platformName='iOS', platformVersion='13.4', automationName='xcuitest', deviceName='iPhone Simulator', app=PATH('../../apps/UICatalog.app.zip') ) self.driver = webdriver.Remote('http://localhost:4723/wd/hub', desired_caps, direct_connection=True)https://appium.github.io/python-client-sphinx/ is detailed documentation
- Code Style: PEP-0008
- Apply
autopep8,isortandmypyas pre commit hook - Run
makecommand for development. Seemake helpoutput for details
- Apply
- Docstring style: Google Style
gitchangeloggeneratesCHANGELOG.rst
pip install --user pipenvpython -m pipenv lock --clear- If you experience
Locking Failed! unknown locale: UTF-8error, then refer pypa/pipenv#187 to solve it.
- If you experience
python -m pipenv install --dev --systempre-commit install
You can run all of tests running on CI via tox in your local.
$ toxYou also can run particular tests like below.
$ pytest test/unitRun with pytest-xdist
$ pytest -n 2 test/unit$ pytest test/functional/ios/search_context/find_by_ios_class_chain_tests.py- Create simulators named 'iPhone 8 - 8100' and 'iPhone 8 - 8101'
- Install test libraries via pip,
pip install pytest pytest-xdist - Run tests
$ pytest -n 2 test/functional/ios/search_context/find_by_ios_class_chain_tests.pyFollow below steps.
$ pip install twine $ pip install git+git://github.com/vaab/gitchangelog.git # Getting via GitHub repository is necessary for Python 3.7 # Type the new version number and 'yes' if you can publish it # You can test the command with DRY_RUN $ DRY_RUN=1 ./release.sh $ ./release.sh # releaseApache License v2