Introduction
RobotFramework-MobileLibrary is an appium testing library for RobotFramework.
It uses Appium (version 1.x) to communicate with Android and iOS application, that leverages the Appium libraries. We wrap the KWs(Mobile_xxxx) on it according to our project requirements. similar to how Selenium WebDriver talks to web browser.
It support Python 2.x only.
Installation
Using pip
The recommended installation method is using pip:
pip install robotframework-mobilelibrary
The main benefit of using pip is that it automatically installs all dependencies needed by the library. Other nice features are easy upgrading and support for un-installation:
pip install --upgrade robotframework-mobilelibrary pip uninstall robotframework-mobilelibrary
Project Contributors
1 maintainer
Metadata
1 maintainer
Release files for robotframework-mobilelibrary 2.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| robotframework-mobilelibrary-2.0.5.tar.gz | 28.2 kB | Without provenance | Details |
Release files / robotframework-mobilelibrary-2.0.5.tar.gz
| Download URL | robotframework-mobilelibrary-2.0.5.tar.gz |
|---|---|
| Size | 28.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
61f6cc7afec56f1a7484b631dbe5a70b5a50ee9619f04d5c581f2b7868a33f16
|
|
BLAKE2b-256 checksum How to use checksums |
9186109aab30e4b9b1480e02bf3a88287f9724ba6aa543365b42d1c0b3ca6477
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for robotframework-mobilelibrary 2.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
