TheReportStack CLI
A powerful CLI and Python package to seamlessly upload your automated test execution reports to the TheReportStack Dashboard.
⚡ Features
- Upload Instantly: Upload PyTest, Cucumber, and Newman JSON reports directly to your TheReportStack Dashboard project.
- Smart Tags: Supports parsing complex tag expressions (e.g.
["@smoke and @wallet"]). - Flexible Authentication: Authenticate via project tokens, Environment Variables, or email & password.
- Zero Coding Required: Configure once with a simple json file and trigger from anywhere in your CI/CD pipelines.
📦 Installation
Install the package via pip:
pip install thereportstack
🚀 Quick Start
1. Initialize Configuration
Navigate to your project directory and run the initialization command. This creates the configuration structure.
thereportstack init
This generates a thereportstack/config.json file in your current directory with default values.
You can also configure the project directly from the command line by passing arguments. This will instantly populate or update the config.json file:
thereportstack init --projectId YOUR_PROJECT_ID --tags "smoke" "regression" --typeOfReport pytest
2. Configure Your Project
Edit the generated thereportstack/config.json with your project's specifics.
{
"typeOfReport": "pytest",
"projectId": "YOUR_PROJECT_ID",
"file": "path/to/report.json",
"testEnv": "QA",
"testType": "WEB",
"tags": ["smoke", "regression"],
"browser": "chrome",
"browserVersion": "latest",
"iterationId": "Batch1",
"baseUrl": "https://app.thereportstack.com/api/v1/public"
}
Don't want to expose your token in code? Remove the "token" field from the config and export it as an environment variable in your CI/CD tool:
export DASHBOARD_TOKEN="YOUR_API_TOKEN"
3. Upload Report
Once your config is set and your testing framework has generated the JSON report, run:
thereportstack start
That's it! 🚀 Your test execution report is now beautifully cataloged on the TheReportStack Dashboard.
🔧 Configuration Reference
| Parameter | Description | Default Value |
|---|---|---|
typeOfReport |
The framework generating the report (pytest, cucumber, newman, normal) |
pytest |
projectId |
Your unique project ID from the TheReportStack dashboard | "" |
file |
Relative or absolute path to the generated JSON test report | report.json |
testEnv |
Environment where the test triggered (QA, Staging, Prod, etc.) |
QA |
testType |
Type of Testing (WEB, API, MOBILE) |
WEB |
tags |
Array of strings representing your test suites/scenario tags (["smoke", "regression"]) |
["smoke"] |
browser |
Name of the executed browser (chrome, firefox, safari, edge) |
chrome |
browserVersion |
Version of the browser | latest |
token |
Personal access token. Overridden by the DASHBOARD_TOKEN environment variable if present. |
"" |
🔑 Authentication Methods
TheReportStack gives you several options for secure authentication:
- Config Token: Place
"token": "YOUR_TOKEN"directly in theconfig.json. - Environment Variable: Export
DASHBOARD_TOKENon your machine or CI/CD runner. - Email & Password: You can provide
"email"and"password"fields inconfig.jsonand the CLI will automatically securely negotiate an authentication token. (Token/Environment Token takes precedent).
✨ Tag Parsing Support
To make QA tagging flexible, thereportstack CLI automatically normalizes boolean-style or nested BDD tags coming from your project definitions before sending them to the dashboard:
["@smoke and @wallet"]➡️["smoke", "wallet"]["smoke, regression"]➡️["smoke", "regression"]["(checkout)"]➡️["checkout"]
🤝 Support
If you encounter any issues integrating this into your Python, Node, Java, or Ruby pipelines, please reach out directly to the TheReportStack maintainers.
Metadata
Release files for thereportstack 1.0.4
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 |
|---|---|---|---|---|
| thereportstack-1.0.4.tar.gz | 8.8 kB | Without provenance | Details for thereportstack-1.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| thereportstack-1.0.4-py3-none-any.whl | Python 3 | none | any | Details for thereportstack-1.0.4-py3-none-any.whl |
Total release size: 16.9 kB
Release files / thereportstack-1.0.4.tar.gz
| Download URL | thereportstack-1.0.4.tar.gz |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d7b98104184f4d0077e9259d6025dd4a9bddbc816269323035a06be00f2151b
|
|
BLAKE2b-256 checksum How to use checksums |
f874ff3afcbd0be1b245412faedeefa8746a2865f124529343852be43f0f3598
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.0
|
Release files / thereportstack-1.0.4-py3-none-any.whl
| Download URL | thereportstack-1.0.4-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8bde53220841100a67d375bb695f315b01ada72cd8a56f3adff358971dde8424
|
|
BLAKE2b-256 checksum How to use checksums |
d5acccab109d2ad90072fdee3147ad9c297625331fe69de7d946e726370347e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.0
|
Security for thereportstack 1.0.4
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.