Dump testcases results to xunit file; submit files to Polarion importers
Project description
Usage
Automatic submission of testing results from the CSV, SQLite, junit-report.xml (from pytest) or Ostriz JSON input file to Polarion® XUnit Importer, or submission of pre-generated XUnit or Test Case xml files to corresponding Polarion® Importer:
polarion_dumper.py -i {input_file}By default test results are submitted to Polarion®. You can disable this bahavior with -n option. In this case the XML file used for results submission will be saved to disk. Default file location is current directory, default file name is testrun_TESTRUN_ID-TIMESTAMP.xml (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 will be PATH/testrun_TESTRUN_ID-TIMESTAMP.xml.
When the input file is a XML file with results (e.g. saved earlier with -o FILE -n) or test cases to be imported, it is submitted to Polarion®.
Configuration
You need to set the following environment variables (the same are used for pylarion):
export POLARION_USERNAME=kerberos_username
export POLARION_PASSWORD=kerberos_passwordOr you can specify credentials on command line with --user kerberos_username --password kerberos_password. Or you can specify credentials in dump2polarion.yaml file.
The default user config file is ~/.config/dump2polarion.yaml. You can also specify the config file on command line with -c config_file.yaml.
Install
You don’t need to install the package, you can use the scripts directly from the cloned repository.
To install the package to your virtualenv, run
pip install dump2polarionor install it from cloned directory
pip install .Package on PyPI <https://pypi-hypernode.com/pypi/dump2polarion>
Requirements
You need sqlite3, all recent python versions include it by default. The rest is listed in requirements.txt.
CSV format
There needs to be a row with field names - it is 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
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 output.xml --user {user} --password {password}or
curl -k -u {user}:{password} -X POST -F file=@./output.xml https://polarion.engineering.redhat.com/polarion/import/xunitMore 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>
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
File details
Details for the file dump2polarion-0.17.tar.gz.
File metadata
- Download URL: dump2polarion-0.17.tar.gz
- Upload date:
- Size: 41.9 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 29d8ffb77a514cff876a44bae753e51c48bcfb8b7d0b497e1e17e03390b971af |
|
| MD5 | 0fdebddb0d1b9eaebfceee40c4b86b26 |
|
| BLAKE2b-256 | dae3ff8a6c5df46c3bf5ee93fe12a583568eb944fce33adaf3392caeafc9a9d3 |
