Catalog PyPI
PACKAGE EXPLORERView in registry

11automation

PyPI

Automation dashboard report uploader

Versions collected1
Direct dependencies1From release 1.0.1
Last observed20 Oct, 15:11 UTC

README

Version 1.0.1 documentation

11Automation CLI


A powerful CLI and Python package to seamlessly upload your automated test execution reports to the 11Automation Dashboard.


⚡ Features

  • Upload Instantly: Upload PyTest, Cucumber, and Newman JSON reports directly to your 11Automation 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 11automation

🚀 Quick Start

1. Initialize Configuration

Navigate to your project directory and run the initialization command. This creates the configuration structure.

11automation init

This generates an 11automation/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:

11automation init --projectId YOUR_PROJECT_ID --tags "smoke" "regression" --typeOfReport pytest

2. Configure Your Project

Edit the generated 11automation/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.11automation.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:

11automation start

That's it! 🚀 Your test execution report is now beautifully cataloged on the 11Automation Dashboard.

🔧 Configuration Reference

ParameterDescriptionDefault Value
typeOfReportThe framework generating the report (pytest, cucumber, newman, normal)pytest
projectIdYour unique project ID from the 11Automation dashboard""
fileRelative or absolute path to the generated JSON test reportreport.json
testEnvEnvironment where the test triggered (QA, Staging, Prod, etc.)QA
testTypeType of Testing (WEB, API, MOBILE)WEB
tagsArray of strings representing your test suites/scenario tags (["smoke", "regression"])["smoke"]
browserName of the executed browser (chrome, firefox, safari, edge)chrome
browserVersionVersion of the browserlatest
tokenPersonal access token. Overridden by the DASHBOARD_TOKEN environment variable if present.""

🔑 Authentication Methods

11Automation gives you several options for secure authentication:

  1. Config Token: Place "token": "YOUR_TOKEN" directly in the config.json.
  2. Environment Variable: Export DASHBOARD_TOKEN on your machine or CI/CD runner.
  3. Email & Password: You can provide "email" and "password" fields in config.json and the CLI will automatically securely negotiate an authentication token. (Token/Environment Token takes precedent).

✨ Tag Parsing Support

To make QA tagging flexible, 11automation 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 11Automation maintainers.

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 1

Collected releases
VersionPublishedDirect dependenciesOpen version
1.0.120 May 20261

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Metadata history

Meaningful changes
Current collected state Current

Observed since 20 Oct, 15:11 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:f5ba5bf1460b35f5fb0ba797a283950d0c9b64c4eda0b50162f936b3ae0a67c1