Test IT TMS importers
Allure report
Getting Started
Installation
pip install testit-importer-allure
Usage
Configuration
Use the command testit --help to view the configuration setup help:
testit --url <url>
testit --privatetoken <token>
testit --projectid <id>
testit --configurationid <id>
And fill parameters with your configuration, where:
url - location of the TMS instance
privatetoken - API secret key
- go to the https://{DOMAIN}/user-profile profile
- copy the API secret key
projectid - id of project in TMS instance
- create a project
- open DevTools -> network
- go to the project https://{DOMAIN}/projects/{PROJECT_GLOBAL_ID}/tests
- GET-request project, Preview tab, copy id field
configurationid - id of configuration in TMS instance
- create a project
- open DevTools -> network
- go to the project https://{DOMAIN}/projects/{PROJECT_GLOBAL_ID}/tests
- GET-request configurations, Preview tab, copy id field
Importing
Use the command testit --resultsdir allure-results --testrunname <name> to specify the directory with Allure report results and create new test run with the specified name in TMS instance.
The --testrunname parameter is optional. The default name of testrun is "AllureRun"
Or use the command testit --resultsdir allure-results --testrunid <id> to specify the directory with Allure report results and id of test run in TMS instance.
Important: This command initiates the import.
Contributing
You can help to develop the project. Any contributions are greatly appreciated.
- If you have suggestions for adding or removing projects, feel free to open an issue to discuss it, or directly create a pull request after you edit the README.md file with necessary changes.
- Please make sure you check your spelling and grammar.
- Create individual PR for each suggestion.
- Please also read through the Code Of Conduct before posting your first idea as well.
License
Distributed under the Apache-2.0 License. See LICENSE for more information.
1 maintainer
Metadata
1 maintainer
Release files for testit-importer-allure 1.17.2.post580
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 | |
|---|---|---|---|---|
| testit_importer_allure-1.17.2.post580.tar.gz | 19.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| testit_importer_allure-1.17.2.post580-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.2 kB
Release files / testit_importer_allure-1.17.2.post580.tar.gz
| Download URL | testit_importer_allure-1.17.2.post580.tar.gz |
|---|---|
| Size | 19.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b6874ea279c338827d67f45e3d8f0f0dd9cf89a26bb841e71e5314fa5b30cb98
|
|
BLAKE2b-256 checksum How to use checksums |
73da37687c04ea112ee3be2905b2610c404996dc1659cfb17ce9a465bfe5d5cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / testit_importer_allure-1.17.2.post580-py3-none-any.whl
| Download URL | testit_importer_allure-1.17.2.post580-py3-none-any.whl |
|---|---|
| Size | 23.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f8c73df537b958232f8ccee592b3e6ad864b73ec08a0a27002ef6c4a795f414
|
|
BLAKE2b-256 checksum How to use checksums |
ef9eb3a6cd639f0d2045ba594699845a4796644625c457e4e82b9d13bf782043
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for testit-importer-allure 1.17.2.post580
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.
