Test Automation

Test Automation enables you to test your recipe's functionality with mock (simulated) data.

It allows you to:

• Create multiple test cases for each recipe
• Run tests automatically
• Automatically check any step output values
• Avoid using your apps’ data while testing by using mock data
• Use APIs to integrate automatic testing into your CI/CD pipeline

Problems it solves

Test Automation reduces the risk of deploying the wrong logic to production. It also saves you time because it automates the process of testing recipe logic and preparing test data.

How it works

Test Automation uses a test case to test specific steps of a particular recipe.

Before using Test Automation to test your recipe's functionality, you must create a test case.

Permissions

You can control access to Test Automation functionality with permissions using role-based access control (RBAC).

In the new permissions model, Test Automation access is defined by the following project roles:

• Project admin

• Full access

• Advanced builder

• Full access

• Builder

• Full access

• Project operator

• View only

Additionally, you can manage privileges for Test Automation using custom project roles.

In workspaces using the legacy permissions model, the following legacy system roles provide similar access:

• Admin

• Full access

• Analyst

• Full access

• Operator

• View only