Capabilities of the dump2polarion library
generating XML files for XUnit, Testcase and Requirements Importers
submitting XML files to Importers
verifying that the import was successfull
saving the import log files
reading Test Cases data from SVN repository with checked out Polarion project
The library supports all features of the Importers (even iterations). The export to XML files can be customized per project - lookup method, what results will be included in the XUnit (e.g. only PASSed tests), etc.
Both Python 2 and 3 are supported.
The library doesn’t use the legacy webservices API, all the operations are performed using Polarion Importers.
polarion_dumper.py script
Script for importing tests results recorded in the CSV, SQLite, junit-report.xml (generated by pytest) or Ostriz JSON input file to Polarion using the XUnit Importer.
Can be also used for submit of pre-generated XUnit, Test Case or Requirement XML files to corresponding Polarion Importer.
By default the script waits until the Importer finishes the import job and then checks the success of the operation.
Usage
polarion_dumper.py -i {input_file}By default the input data are submitted to Polarion. You can disable this bahavior with -n option. In this case the XML file used for submission will be saved to disk. Default file location is the current directory (can be overriden with -o option).
When output file is specified with -o PATH, the XML file used for results submission will be saved to disk. If PATH is a directory, resulting file name will be generated - PATH/FILE_TYPE-TESTRUN_ID-TIMESTAMP.xml.
When the input file is a XML file in a format supported by one of the Polarion Importers (e.g. saved earlier with -o FILE -n), it is submitted to Polarion.
Configuration
You can specify credentials on command line with --user kerberos_username --password kerberos_password. Or you can set them in a config file.
The config file is specified on command line with -c config_file.yaml.
Another possibility for specifying credentials are environment variables (the same are used for pylarion):
export POLARION_USERNAME=kerberos_username
export POLARION_PASSWORD=kerberos_passwordYou can mix all these approaches, e.g. user name on command line and password in the environment variable.
Install
To install the package to your virtualenv, run
pip install dump2polarionor install it from cloned directory
pip install -e .Package on PyPI <https://pypi.python.org/pypi/dump2polarion>
Requirements
Requirements are listed in requirements.txt.
CSV format for XUnit
There needs to be a row with field names - it is present by default when exported from Polarion.
Fields are ID; Title; Test Case ID (optional but recommended); Verdict; Comment (optional); Time (optional); stdout (optional); stderr (optional) + any other field you want. Order of the fields and case doesn’t matter.
The “Verdict” field and any optional fields must be added manually. Valid values for “verdict” are “passed”, “failed”, “skipped”, “waiting” or empty. It’s case insensitive.
There can be any content before the row with field names and the test results.
SQLite format for XUnit
You can convert the CSV file exported out of Polarion using the csv2sqlite.py script:
csv2sqlite.py -i {input_file.csv} -o {output_file.sqlite3}How to submit the XML file manually
polarion_dumper.py -i input.xml --user {user} --password {password}or
curl -k -u {user}:{password} -X POST -F file=@./output.xml {importer_url}More info
For CFME QE specific instructions see <https://mojo.redhat.com/docs/DOC-1098563>
For info about XUnit Importer see <https://mojo.redhat.com/docs/DOC-1073077>
For info about Test Case Importer see <https://mojo.redhat.com/docs/DOC-1075945>
For info about Requirements Importer see <https://mojo.redhat.com/docs/DOC-1163149>
1 maintainer
Metadata
1 maintainer
Release files for dump2polarion 0.48.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 | |
|---|---|---|---|
| dump2polarion-0.48.0.tar.gz | 98.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dump2polarion-0.48.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 150.6 kB
Release files / dump2polarion-0.48.0.tar.gz
| Download URL | dump2polarion-0.48.0.tar.gz |
|---|---|
| Size | 98.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1e7748fca074d9ffa1803aebe881d56edf1c17150b0f07854ced9fd9946f12d4
|
|
BLAKE2b-256 checksum How to use checksums |
819463bcbcbd3e56c641311a70f2a0cf012ba40e960e6f87d99c1b904e2bf099
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.6.7
|
Release files / dump2polarion-0.48.0-py3-none-any.whl
| Download URL | dump2polarion-0.48.0-py3-none-any.whl |
|---|---|
| Size | 51.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2dd71cd59caa1f9b01de3d195f96cf354cd0bd8004de3fb0f23f97c4a05eca29
|
|
BLAKE2b-256 checksum How to use checksums |
db751f1a78421d49b0c105cf53012aeccf6fd40e883f99c08b174a4d84288425
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.6.7
|
