This project has been archived by its maintainers, and is no longer receiving any updates.
A Python fixture for working with SauceLabs’ services.
For more information see the Launchpad project page.
Getting started
Use like any other fixture:
from saucelabsfixture import (
SauceConnectFixture,
SauceOnDemandFixture,
)
capabilities = {...}
def test_something(self):
connect = self.useFixture(SauceConnectFixture())
on_demand = SauceOnDemandFixture(
capabilities, connect.control_url)
self.useFixture(on_demand)
driver = on_demand.driver
...
This will start up a Connect service using your credentials (see below). It will also download Sauce-Connect.jar if it’s not already available. The driver will be set up to send commands via the secure tunnel that the Connect service provides.
Credentials for the Connect service
Credentials for the Connect service can be passed into the SauceConnectFixture constructor, but otherwise they can be put into a file in your home directory:
$ mkdir -p ~/.saucelabs/connect $ touch ~/.saucelabs/connect/credentials $ chmod go-rwx ~/.saucelabs/connect/credentials $ echo "$username $api_key" > ~/.saucelabs/connect/credentials
Metadata
Release files for saucelabsfixture 0.1
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 | |
|---|---|---|---|---|
| saucelabsfixture-0.1.tar.gz | 4.9 kB | Without provenance | Details |
Release files / saucelabsfixture-0.1.tar.gz
| Download URL | saucelabsfixture-0.1.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2ef893a930f69c9d23c5a3774e41fddfc41dd2e1bff96d894d83f5607717e8fe
|
|
BLAKE2b-256 checksum How to use checksums |
c8963daf21f326443d43508a03c1989bdcec7bfd479ff2bb134d3a2aec88388d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for saucelabsfixture 0.1
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.