TestY Jira Defect Report Plugin
TestY Jira Defect Report Plugin provides the report for defects found in a test plan results.
Installation
Installation is not required. The plugin will be installed as a part of TestY.
How to use
How to add defect to results
If you add a new test result and would like to mention a defect issued in your JIRA system you need following:
- Add attribute named
DefectorDefectsto the result. Use attribute type TEXT or LIST - Put the full URL (usually it formatted as
http(s)://<JIRA host>/browse/XXX-NNNN) to JIRA issue in the attribute above
How to get the defect report
- Open the plugin page
- Choose the project
- Choose the attribute where JIRA issues stored
- Choose the test plan
- Choose how to aggregate results (None, use latest, use actual)
Plugin will provide a table containing following:
- The link to JIRA issue
- The test plan name
- The link to test from the plan above
- The test status
- The date
Notes
The plugin has russian UI.
Metadata
Release files for defect-megareport 0.0.2
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 |
|---|---|---|---|---|
| defect_megareport-0.0.2.tar.gz | 87.1 kB | Without provenance | Details for defect_megareport-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| defect_megareport-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for defect_megareport-0.0.2-py3-none-any.whl |
Total release size: 177.3 kB
Release files / defect_megareport-0.0.2.tar.gz
| Download URL | defect_megareport-0.0.2.tar.gz |
|---|---|
| Size | 87.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f40c92a8a8480e257a88ce1ebb7e70a689214c97472218f07cc3d4da6577fe90
|
|
BLAKE2b-256 checksum How to use checksums |
311d5adcf13d92d5c4deb2f0f065bba8e96c18ab15f4a337085db1d200f0141e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Release files / defect_megareport-0.0.2-py3-none-any.whl
| Download URL | defect_megareport-0.0.2-py3-none-any.whl |
|---|---|
| Size | 90.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a2ee173c99e85fe58648983e5591a83f5c7f36c4ee38243f9b7b3a38fe75356
|
|
BLAKE2b-256 checksum How to use checksums |
085195c21c6e9d5cb01a929cc4805d6e0df8dbb527221e3262f13cb73a5510d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Security for defect-megareport 0.0.2
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.