pytest-slack
Pytest to Slack reporting plugin
Free software: MIT license
Documentation: https://pytest-slack.readthedocs.io.
Requirements
Requests
Installation
You can install “pytest-slack” via pip:
$ pip install pytest-slack
Usage
Setup slack hook
Use this plugin by running pytest normally and use the following options to customize report:
>>> slack:
--slack_channel=SLACK_CHANNEL
Set the channel name to report
--slack_hook=SLACK_HOOK
Used for reporting to slack
--slack_report_link=SLACK_REPORT_LINK
Set the report link
--slack_username=SLACK_USERNAME
Set the reporter name
--slack_timeout=SLACK_TIMEOUT [DEFAULT = 10s ]
Set the timeout for sending results in seconds
--slack_success_emoji=SLACK_SUCCESS_EMOJI [default = :thumbsup:]
Set emoji for a successful run
--slack_failed_emoji=SLACK_FAILED_EMOJI [default = :thumbsdown:]
Set emoji for a failed run
--slack_success_icon=SLACK_SUCCESS_ICON [default = None]
Set icon (a url) for a successful run. Overrides SLACK_SUCCESS_EMOJI
--slack_failed_icon=SLACK_FAILED_ICON [default = None]
Set icon (a url) for a failed run. Overrides SLACK_FAILED_EMOJI
Example
$ pytest tests –slack_hook=https://hooks.slack.com/services/… –slack_channel=test_report_channel –slack_username=”Regression testing results”
All kind of problems:
Passed test:
$ pytest tests –slack_hook=https://hooks.slack.com/services/… –slack_channel=test_report_channel –slack_username=”Regression testing results” –slack_report_link=http://any_address
Passed test with link:
Issues
If you encounter any problems, please file an issue along with a detailed description.
Credits
[ ~ Dependencies scanned by PyUp.io ~ ]
History
1.0.1 (2019-04-18)
First release on PyPI.
2.1.2 (2020-02-10)
Stable release.
Credits
Development Lead
Contributors
Metadata
Release files for pytest-slack 2.3.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 | Actions |
|---|---|---|---|---|
| pytest-slack-2.3.1.tar.gz | 13.0 kB | Without provenance | Details for pytest-slack-2.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pytest_slack-2.3.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for pytest_slack-2.3.1-py2.py3-none-any.whl |
Total release size: 18.4 kB
Release files / pytest-slack-2.3.1.tar.gz
| Download URL | pytest-slack-2.3.1.tar.gz |
|---|---|
| Size | 13.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b21fdf20a9d92a417ce0fda54b2868955e483ead569914ed38314bec9ce6099
|
|
BLAKE2b-256 checksum How to use checksums |
b0766dddb9db53c4a5c30670a7612773332e097e27da0cf431dce95cfd4ccdec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.9.0
|
Release files / pytest_slack-2.3.1-py2.py3-none-any.whl
| Download URL | pytest_slack-2.3.1-py2.py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
1b2e8d2e947e06a38ebdc22da1ef56bb3d958d8a29b9f7e724c69236e227c88c
|
|
BLAKE2b-256 checksum How to use checksums |
edc61a107a666e3c04ef3a73f0af9a6d2ce71a4a6aa70c4e76240f191c4e2db2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.9.0
|
Security for pytest-slack 2.3.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.