Quapi blueprints are written in plain English Gherkin.
Gherkin can be written by an analyst, scrum master, SME or product manager.
Quapi test can be written to run against a database of credentials, endpoints, and variables.
A security expert can design a test to check for certificate credentials, and make it available to a project to run against their end points.
A set of tests, actions and configuration information.
These are combined into a tree structure allowing SMEs to build and organise a library of predefined tests and actions.
Quapi can make decisions and perform actions dependent on a test outcome.
For example: If a test fails Quapi could fix it, log a configuration change, order a certificate or alert a security specialist.
Quapi keeps the results of all tests in a statistical database.
Identifying exactly when errors were introduced and keeping track of a project's progress to release.
All logic and information is available in the cloud, allowing it to be running in minutes.
Specific location dependent tests can be executed on “Runners” that can be anywhere, including on a laptop.