AutoApiTestRunner
Automation Command Line Tool
Installation
Method-1: Using https://pypi.org/project/AutoApiTestRunner/1.0.1/
Installation Command:
sudo -H pip install AutoApiTestRunner==1.0.1
Method-2: Using pip
Installation Command: NOTE: you must have a working git over ssh configuration.
ssh -T git@github.com
“Hi kshamashuttl! You've successfully authenticated, but GitHub does not provide shell access.”
sudo -H python -m pip install --no-cache-dir "git+ssh://git@github.com/Shuttl-Tech/AutoApiTestRunner.git"
Validate the installation by running
auto --help
Configuration
you need to configure it before it can access Drone API. You are going to need a Drone Token and Drone server URL. Now head over to https://ci.shuttl.xyz/account, under Example CLI Usage section you will see the token and server URL. Copy both of them and keep them safe.
You can start initialisation process by executing
auto init
and provide the information on prompt.
- Drone token:your personal token (https://ci.shuttl.xyz/account)
- Drone host:https://ci.shuttl.xyz/
- Full name: Your Name
- Github org [Shuttl-Tech]:Shuttl-Tech
Trigger API Sanity
Command:
auto runner
Repo name:Name of GH repo
Branch:Custom branch name
1 maintainer
Metadata
1 maintainer
Release files for AutoApiTestRunner 1.0.3
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 | |
|---|---|---|---|---|
| AutoApiTestRunner-1.0.3.tar.gz | 3.4 kB | Without provenance | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| AutoApiTestRunner-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
| AutoApiTestRunner-1.0.3-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 13.8 kB
Release files / AutoApiTestRunner-1.0.3.tar.gz
| Download URL | AutoApiTestRunner-1.0.3.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1088d284b4502e10606b1ea5f2207e207dc3945f8a450556afa906828d454cc4
|
|
BLAKE2b-256 checksum How to use checksums |
c7fdb2ac1bf1bac58a9b114248b1ad508693e96165b3ffbaa761df96b4ab192b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.7.0 requests/2.25.1 setuptools/44.1.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/2.7.16
|
Release files / AutoApiTestRunner-1.0.3-py3-none-any.whl
| Download URL | AutoApiTestRunner-1.0.3-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8662e8b068ed4fa0ee47cec7be6ee3783816af06abd519a6b2ae0a6232873a05
|
|
BLAKE2b-256 checksum How to use checksums |
e21db9b847fe953b69622b3fd46d9158a6c386c83a3c1dfc5469f2041ce4569f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.7.0 requests/2.25.1 setuptools/44.1.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/2.7.16
|
Release files / AutoApiTestRunner-1.0.3-py2-none-any.whl
| Download URL | AutoApiTestRunner-1.0.3-py2-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
7049f2d4c4b252a51e2fe0aeca17bd59e3070f2461c413e0c42dfd62aef89b52
|
|
BLAKE2b-256 checksum How to use checksums |
d89314e23204dd8c3a66a5aa07f55affe9facd3e348d07595e4a4247bfda8357
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.7.0 requests/2.25.1 setuptools/44.1.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/2.7.16
|
Security for AutoApiTestRunner 1.0.3
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.
