UP9 - instant test automation platform for microservices, Kubernetes and cloud-native.

UP9 Docs Section


Seamlessly record and test workflows.

UP9 has several modes of operations. It can be deployed 'close' to each Service (e.g. as a sidecar in K8s), however, it can also be used to record workflows and automatically create tests that cover those workflows.

Working on workflows is quite easy and a lot of fun :).

Once you have UP9 CLI installed, you are ready to start recording workflows using Google's Puppeteer.


The following command will open up a browser window and will record session traffic into a new or an existing Workspace. From command prompt, run

up9 tap:start my.new.workspace

We suggest you use a meaningful name instead of ‘my.new.workspace,’ as this will be the name of the new Workspace. If you'd like to add workflows to an existing Workspace, simply use the name of an existing Workspace.

This command will open a new Chromium browser window. Use this browser window to go through the Workflow you'd like to record. All steps made in this browser will be recorded and sent for processing.

Allow permission to Chromium when prompted. As you browse, you will see a requests counter (in separate tab) incrementing, which indicates application traffic is being recorded and sent for processing.

When done, close the Chromium browser and go to your UP9 dashboard to view your new (or existing) Workspace.


UP9 uses machine learning to create a model that is based on the recorded traffic. The more passes found, the stronger the confidence level of the model. In layman's terms, it is best to record the same workflow several times into the same Workspace to make the model more accurate.


To see the outcome of the Workflow, log into your UP9 account. You can see your new (or existing Workspace). You can learn more about the information presented in the Dashboard in the Quick Tour section in the Knowledge Base.

Updated about a year ago

What's Next

Learn how to run tests after you've recorded your workflow.



Seamlessly record and test workflows.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.