aiqDocTests
AiqDocTests A framework to validate request/response's json and create documentation for applications maintained by the devs of the most greedy-gut app on the internet!
Install with pip3
pip3 install aiqDocTests
Init in the project folder
aiqdoctests --init
Will be created the folder data_scructures_io and static.
In the data_scructures_io, is the json files to test the request. Example
We using Cerberus to validate the structure. So if any valid in the json response is a name, type or don't send. Will occurs a exception in tests.
In the static folder, will be the json file to Swagger, with this file you can any package in any language what you want to read.
This swagger.json is generate, so every time that you run the command aiqdoctests -g in the folder this file will be update.
The .aiqdoctests.config file
This json file is for configuration, so the name folders and other things can be personalizable.
docs_url
with the command aiqdoctests --docs will be up un flask server in the port 3000 and read the swagger file, this value is for which url will run. default: localhost:3000/docs
save_file_swagger
The name file generate to swagger. default: swagger.json
data_structures_folder
The name folder that are the data scructures for requests. default: data_structures_io
tests_folder
The name folder that will be the tests. default: tests
tests_before_cmd
Sometimes in the project, we wanna run command/script before start the tests, example create the tables in the bd. Will run this command before start the tests.
tests_between_cmd
This command is for run between tests, in the tearDown, so after run a test, this is for a script or migration that you want to run for clean the bd for example.
swagger
The header for swagger file.
For more information
For more you can see in the example (https://github.com/aiqfome/aiqDocTests-example)
Relax, this documentation is still in construction 👷
Any doubt create a issue.
Made with 🍕 & ♥️! Enjoy it!
Metadata
Release files for aiqDocTests 1.7.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aiqDocTests-1.7.1-py3-none-any.whl | Python 3 | none | any | Details for aiqDocTests-1.7.1-py3-none-any.whl |
Release files / aiqDocTests-1.7.1-py3-none-any.whl
| Download URL | aiqDocTests-1.7.1-py3-none-any.whl |
|---|---|
| Size | 152.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
21a820576cae197a76c20199598d8117825d69e2ca093a9fff44cf813e09a5c5
|
|
BLAKE2b-256 checksum How to use checksums |
de2de3d282f8864e498f27a06238dab48ad5a207f13a26408d8a6eae93b778e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/46.4.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.2
|
Security for aiqDocTests 1.7.1
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.