# pytest-hue Control your Phillips Hue by PyTest.
The following parameters are used:
Brightness is controlled by the number of run tests against total number of tests
Green hue is controlled by the number of passed tests against total number of tests
Red hue is controlled by the number of failed tests against total number of tests
Blue hue is controlled by the number of passed tests against total number of tests
## Configuration You’ll need to supply the following values:
–hue-ip: Hue Bridge IP Address
–hue-username: Username to connect to Hue Bridge with ([follow instructions here to get a new one](https://developers.meethue.com/develop/get-started-2/))
–hue-rooms: Rooms to control the lights within
## Installing and Running To install
pip install pytest-hue
or clone this repo and run python setup.py install
To run, make sure:
Your Phillips Hue Bridge and lights are turned on
Then run with following command (substituting the appropriate values)
pytest –hue-ip XXX.XXX.XXX.XXX –hue-username XXXXXXXXXX –hue-rooms Office
Metadata
Release files for pytest-hue 1.0.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 |
|---|---|---|---|---|
| pytest-hue-1.0.0.tar.gz | 3.0 kB | Without provenance | Details for pytest-hue-1.0.0.tar.gz |
Release files / pytest-hue-1.0.0.tar.gz
| Download URL | pytest-hue-1.0.0.tar.gz |
|---|---|
| Size | 3.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2452ca28a55521b35b7a335d5db5d44f3184f4c36b21e781533cfd3d0fac3e87
|
|
BLAKE2b-256 checksum How to use checksums |
89695a4f7097e875121d2de55e1add0ae04609f5293df1c4f2a877b785fab84f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/2.7.14
|
Security for pytest-hue 1.0.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.