A Framework for orchestrating, asserting and reporting on API calls with templates
Project description
Installation
pip install api-compose
Get Started
# creates a sample project for you to build on
acp scaffold <your_project_name>
Run the programme
acp run
Explore the CLI’s capabilities by running acp or acp –help
Examples
Examples are in ./examples folder
Features
Declaration-based API Call Composition
Allows API calls to be declared as Models.
Distinguishes between Compile Time Rendering and Run Time Rendering
Leverages networkx to determine the execution order of each API call.
Exposes decorator @JinjaFunctionlRegistry to for users to create jinja functions.
Useful Builtin Jinja Globals
Builtin Jinja Globals allow users to specify which part (e.g. headers, body etc.) of an API action (e.g. login, get_images etc.) to use.
## Get the value of the field field_one of the returned body from the login_action API call
{{ acp.actions.output_body('login_action', '$.field_one') }}
## Get the value of the field field_one of the input headers from the login_action API call
{{ acp.actions.input_headers('login_action', '$.field_one') }}
## Get the rendered body of the current API call
{{ acp.actions.config_body('self') }}
Supported API Calls Type - Adapters
Below is the table which breaks down the type of API Call by
Protocol (Column)
Data Format (Row)
HTTP |
WebSocket |
FIX |
|
---|---|---|---|
json |
True |
TBD |
TBD |
xml |
WIP |
TBD |
TBD |
WIP means Working in Progress. It means it is being worked on now.
TBD means to be determined. It means it will be planned in the future.
Schema Validation
Leverages jsonschema and xmlschema to validate returned json and xml data respectively.
Assertion
Allows users to use Jinja to make assertions between API Calls Result
# assert that two different fields in two different actions have the same value
{{ acp.actions.output_body('action_one', $.field_one) == acp.actions.output_body('action_two', '$.field_two') }}
Reporting
Presents Test Results nicely in HTML reports
Architectural Diagram
Jinja Templating
Compile Time Rendering
To make templates reusable, the programme exposes the means to render template files using the below syntax:
block_start_string='[%'
block_end_string='%]'
variable_start_string='[['
variable_end_string=']]'
comment_start_string='[#'
comment_end_string='#]'
Run Time Rendering
To allow for inter-API Call dependencies within a given scenario, the programme also exposes the means to render templated fields using the below syntax:
block_start_string='{%'
block_end_string='%}'
variable_start_string='{{'
variable_end_string='}}'
comment_start_string='{#'
comment_end_string='#}'
Config File
File name is config.yaml
# Generate config.yaml
acp cfg init
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
File details
Details for the file api_compose-0.0.11.tar.gz
.
File metadata
- Download URL: api_compose-0.0.11.tar.gz
- Upload date:
- Size: 73.8 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/4.0.2 CPython/3.10.13
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 6d3fe061cf2a974570c3fcea880d9b65665db8768bf4b4e922b4588370f4fff9 |
|
MD5 | 0032c5c911447b264b7e41c970c4d52f |
|
BLAKE2b-256 | f44c7f373ac090bf0a66f3853d9a2b9ac50b3b3ab84289379c977d1befb99ef3 |