Metadata-Version: 2.1
Name: cvapianalyser
Version: 1.3.6
Summary: plugin tool for capturing API coverage with input of a SPEC file against API shark of CloudVector
License: MIT
Keywords: cvapianalyser,cloudvector,apianalyser
Author: Bala Kumaran
Author-email: balak@cloudvector.com
Requires-Python: >=3.2,<4.0
Classifier: Environment :: Console
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.4
Classifier: Programming Language :: Python :: 3.5
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Topic :: Software Development :: Documentation
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Classifier: Topic :: Software Development :: Quality Assurance
Requires-Dist: cvapianalyser
Requires-Dist: jinja2
Requires-Dist: pyyaml
Requires-Dist: requests (==2.22.0)
Description-Content-Type: text/markdown

# CV-APIAnalyser

cvapianalyser is a Python library for analysing the api traffic captured by CloudVector's APIShark against an APISPEC for identifying the gap in API coverage mostly useful in a QA environment to understand the gap in test coverage. 

Visit https://www.cloudvector.com/api-shark-free-observability-security-monitoring-tool/#apishark

## Installation

Use the package manager [pip](https://pip.pypa.io/en/stable/) to install foobar.

```bash
pip install cvapianalyser
```

## Usage

```python 
cvapianalyser 

****************************************************************************************************
CloudVector CommunityEdition - Coverage analysis plugin
****************************************************************************************************

Enter CommunityEdition(CE) host in format <host>:<port> : x.x.x.x:y
Enter your CommunityEdition(CE) username : sandeep
CommunityEdition(CE) password:
Enter recording in CE to compare with : recording1
```

instead of giving inputs every single time you can also alternatively create a file called my_cesetup.yaml in the path from where you are running the tool

```yaml 
ce_host:
ce_username:
ce_recording:
input_apispec:
```
you can have multiple such my_cesetup.yaml for different CE setup or different recordings and run them from specific paths for its corresponding reports

## License
[MIT](https://choosealicense.com/licenses/mit/)
