home Terminology guide
How it comes together,
-
After signing up,
the first thing you do is build a test suite
using the wizard.
The wizard will scan your
Open API/Swagger specification
then guide you through providing more examples, credentials
and scenarios. -
A plan is then generated which
estimates how many requests will be made,
and to ensure there's enough information
to run tests. -
When a report starts,
an up-to-date plan will be generated
and the test runner will use it to create
a report that contains the results. -
Results are broken down into
timeline based on their test signature.
It includes information about the request, response, steps, and context. -
A suite timeline logs useful information, including any problems encountered running the suite's tests.
Further refine what is built by the plan by skipping specific operations or signatures. -
Results can be filtered, sorted, grouped
and re-visualized, in realtime.
Insights can be saved to a personalised dashboard which can then be shared with other users of your organisation -
Suites can be automated using a
schedule, github webhooks, or API requests.
After each report completes, emails are sent out to users, and a webhook can be fired to continue your workflow.