Sauce Labs Python Bindings
Hello, welcome to the Sauce Python bindings! Let’s make using Sauce Labs Simple!
Example Usage
The goal of the Sauce bindings is to provide a straightforward approach to connecting your automated scripts to Sauce. Here’s an example. The Sauce Python bindings can be used like this:
from saucebindings.session import SauceSession
session = SauceSession()
driver = session.driver driver.get(“www.saucedemo.com”)
session.stop(True)
Requirements
Set your Sauce username and Sauce access key as environment variables.
Installation
Clone this project to build from source
git clone https://github.com/saucelabs/sauce_bindings
python setup.py install
or install from pip
pip install saucebindings
Development
This project will be developed initially in Python 3.x so please create a virtual environment:
python3 -m venv venv
source venv/bin/activate
To install dependencies, do the following:
pip install -r requirements.txt
Testing
To run all tests, run the following:
pytest
Package and Release
python setup.py sdist twine check dist/* twine upload dist/*
Metadata
Release files for saucebindings 1.3.0
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 | Actions |
|---|---|---|---|---|
| saucebindings-1.3.0.tar.gz | 7.1 kB | Without provenance | Details for saucebindings-1.3.0.tar.gz |
Release files / saucebindings-1.3.0.tar.gz
| Download URL | saucebindings-1.3.0.tar.gz |
|---|---|
| Size | 7.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
105e7b0590561b4dc30cf8327b5ecb3dc591f593f29356d91842794bedbab403
|
|
BLAKE2b-256 checksum How to use checksums |
1c7d6be1551ddb7e5f6b3fd9b3e3133012a1232d09bc5e9c317318b73a02c9ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.3
|
Security for saucebindings 1.3.0
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.