Postman-to-CSV
A CLI which consumes a Postman results file in JSON format and outputs a simple CSV file of the results.
Installation
pip install postman-to-csv
Usage
A few examples:
# Convert the JSON results to CSV without any build information
postman-to-csv \
--input 'test-results.json' \
--output 'test-results.csv'
# Flesh out additional information about the build
postman-to-csv \
--input 'test-results.json' \
--output 'test-results.csv' \
--projectname 'my-web-api' \
--branch 'release' \
--buildnumber '1.2.3.4' \
--deployenv 'stage' \
--testtype 'integration'
# Providing all of the available flags
postman-to-csv \
--input 'test-results.json' \
--output 'test-results.csv' \
--projectname 'my-test-project' \
--branch 'release' \
--buildnumber '1.2.3.4' \
--buildtarget 'AnyCPU' \
--buildstatus 'pass' \
--deployenv 'stage' \
--testtype 'integration'
Limitations
This was built to provide a simplified data format that could be used to load the results of Postman tests into a data store for tracking and metrics. It is based on the output format from Newman 4.2.3 and contain minimal information about the test cases and assertions. If you need more complete information, I would recommend that you parse the JSON directly.
Publishing Updates to PyPi
For the maintainer - to publish an updated version of ssm-search, increment the version number in version.py and run the following:
docker build -f ./Dockerfile.buildenv -t postman-to-csv:build .
docker run --rm -it --entrypoint make postman-to-csv:build publish
At the prompts, enter the username and password to the pypi.org repo.
Testing
Test execution in a container using packaged test files.
docker build -f ./Dockerfile.buildenv -t postman-to-csv:build .
docker run -it postman-to-csv:build
postman-to-csv --input <postman JSON> --output <output file name>
Metadata
Release files for postman-to-csv 0.1.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 | Provenance | Actions |
|---|---|---|---|---|
| postman-to-csv-0.1.0.tar.gz | 3.8 kB | Without provenance | Details for postman-to-csv-0.1.0.tar.gz |
Release files / postman-to-csv-0.1.0.tar.gz
| Download URL | postman-to-csv-0.1.0.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
53e1d1b1c664a10e90564a77e164204d2e08b5229d1ecb40528c2618d43a14d6
|
|
BLAKE2b-256 checksum How to use checksums |
72710bed18bd8f08db3f9a663a91ec2295677c7d783a3023834570e709dfc882
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.21.0 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.1
|
Security for postman-to-csv 0.1.0
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.