GitLocker: The Coding Marketplace

Description:

QATLibrary 23.5.3

QATLibrary

QAT (Quick API Tests) Library is a Data/Configuration Driven REST API Test Automation Library.
Can be used as a Robot Framework Library or as standalone tool (CLI). This tool does not solve complex
REST API automation scenarios, rather, provides a simple, lightweight and data-driven approach to create
automated REST API tests quickly. For complex flows, it is recommended to use the library with Robot
Framework.
Features

No coding required. Quick and easy implementation for REST API Tests.
Initialize sample config and Test Data with a single command.
Run from CLI (CI/CD friendly).
Store Test Data, Documentation and Assertions in CSV File.
Authorization: Basic, Digest, OAuth1
Run as a Robot Framework Library with Dynamic Test Generation Support.
Supports all HTTP Methods, SSL Certificates, Proxy Server, Stream, Redirection, Request Timeout etc.
Robot Framework based execution, reports and logs (CLI or Library).

Built-in Assertions

Status Code
JSON Schema
Response Body
Response Headers
Response Time/SLA
Server Certificate

Install QATLibrary
QATLibrary is available in PyPI. You can install using Pip:
pip install qatlibrary

Execution
Getting started from scratch is only a few commands away. Follow -

Generate Sample Test Data CSV and Config YAML from CLI run (Skip this step if you already have Test Data and Config files):
qat init

Execute Tests Using CLI (standalone):
qat run -c config.yaml -f TestCases.csv

Delete report files (*.html and *.xml) in current directory:
qat clean

or to clean a specific report directory:
qat clean -d path/to/dir

For CLI Help (shows all required and optional args, usage etc):
qat --help

Use as Robot Framework Library
Example:
*** Settings ***
Library QATLibrary
Suite Setup QAT Dynamic Tests Setup csvFile=${csvData}
Variables config.yaml # Or can be a robot framework variable (Test/Suite/Variablefile etc.)

*** Variables ***
${host} httpbin.org
${csvData} Tests.csv

*** Test Cases ***
Place Holder Test
[Documentation] Placeholder Test Required by Robot Framework Suite Runner.
No Operaiton

Configurations and Test Data
QATLibrary requires a CSV file with required data to drive the tests. Config yaml or .py files can inject your desired
configurations during execution.
Generating Sample Test Data CSV and Config YAML is easy. Simply run:
qat init

This command should generate two sample files like below -

Sample CSV Test Data: Test Cases or Data file.
Test cases gets generated based on this file's content using Robot Framework.

Sample Config YAML: This file contains various runtime configurations
for tests. Can be utilize to accommodate various CI or Test environments. Please follow the inline comments for more details -
---
# optional args; uncomment as-needed.
# Any block or k/v not required, recommended to keep commented out for reasonable defaults.
base_url: httpbin.org # base url/server name. Default localhost
timeout: 10 # In seconds. Default 5 seconds
allow_redirects: True # Allow Redirects. Default True.
stream: False # True/False. Default False.

## global headers - these are added to every request from your data csv. All headers should be strings.
headers:
user-agent: QATLibrary # this is a static header
Authorization: Basic c29tZXVzZXI6bm90dmVyeXNlY3JldHBhc3M=
# dynamic headers can be added with ${{ }} syntax like below -
X-correlation-id: ${{str(__import__('uuid').uuid4())}} # dynamic headers use python's eval func.
random-digit: ${{str(__import__('random').randint(0,99))}} # dynamic headers use python's eval func.

## To enable proxies for http/https, enable the following config.
#proxies:
# http_proxy: # HTTP proxy. Default None.
# https_proxy: # HTTPS proxy. Default None.
# no_proxy: # Bypass proxy

## SSL/TLS configuration for REST API calls. Enable to configure.
#tls:
# verify_server_cert: True # True/False or path to CA Bundle. Default False.
# certificate: # .pem format certificate. Default None
# private_key: # .pem format private key (unencrypted). Default None.

## Note that the specific details of how to obtain an access token may vary depending on the authentication scheme and API provider.
## Be sure to check the API documentation for instructions on how to obtain an access token for your use case.
## bearer auth / access token config. Enable below configs if required.

#bearer_auth:
# token_url: # token_url for bearer auth
# payload: # generic payload. supports all direct key/value. below are the common ones.
# client_id:
# client_secret:
# scope:
# grant_type:

## Enable following block for bearer auth TLS config.
# tls:
# verify_server_cert: True # True/False or path to CA Bundle. Default False.
# certificate: # .pem format certificate. Default None
# private_key: # .pem format private key (unencrypted). Default None

Once the files are generated, you can rename them according to your test suites or requirements.
Contributing
This is Sharif. I started this project basically to make my life
a bit easier around simple REST API tests. This project is ideal for you if want to get some automated tests done
quickly for your projects without coding and powerful assertion methods out of the box.
QATLibrary is on GitHub.
Get in touch, via GitHub or otherwise, if you've got something to contribute, it'd be most welcome!
Please follow the CONTRIBUTING.md for detailed guidelines.
License
QATLibrary is open source software provided under the MIT License. Please follow LICENSE.md for more details.