---
title: "How to create a test plan"
slug: "how-to-create-a-test-plan"
updated: 2026-07-14T01:12:54Z
published: 2026-07-14T01:12:54Z
canonical: "help.autify.com/how-to-create-a-test-plan"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.autify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to create a test plan

## Introduction

A test plan is an efficient way to plan the execution of multiple terminals and multiple scenarios for a specific build file. The following items can be specified in a test plan:

- One build file
- Multiple execution environments
- Multiple scenarios

## Preparation method

1. Click "Test Plan" in the sidebar. ![01_en.png](https://cdn.document360.io/a099d8a2-cfd2-42ca-9906-68b4a337f4a5/Images/Documentation/01_en.png?sv=2026-02-06&spr=https&st=2026-11-07T12%3A30%3A27Z&se=2026-11-07T13%3A30%3A27Z&sr=c&sp=r&sig=AkFztocUdl6PLhbi6wIAcQa2XlNdW2U7Yqj6ok2UdDM%3D)
2. Click the "New Test Plan" button. ![02_en.png](https://cdn.document360.io/a099d8a2-cfd2-42ca-9906-68b4a337f4a5/Images/Documentation/02_en.png?sv=2026-02-06&spr=https&st=2026-11-07T12%3A30%3A27Z&se=2026-11-07T13%3A30%3A27Z&sr=c&sp=r&sig=AkFztocUdl6PLhbi6wIAcQa2XlNdW2U7Yqj6ok2UdDM%3D)
3. Select a build, execution environment, and scenario ![03_en.png](https://cdn.document360.io/a099d8a2-cfd2-42ca-9906-68b4a337f4a5/Images/Documentation/03_en.png?sv=2026-02-06&spr=https&st=2026-11-07T12%3A30%3A27Z&se=2026-11-07T13%3A30%3A27Z&sr=c&sp=r&sig=AkFztocUdl6PLhbi6wIAcQa2XlNdW2U7Yqj6ok2UdDM%3D)

### Adding an Execution Environment

In the edit screen, select Environment, OS version, and Device, then click "+Device", and finally click the "Save" button.

![Image](https://cdn.document360.io/a099d8a2-cfd2-42ca-9906-68b4a337f4a5/Images/Documentation/EN_testplan_environment.png?sv=2026-02-06&spr=https&st=2026-11-07T12%3A30%3A27Z&se=2026-11-07T13%3A30%3A27Z&sr=c&sp=r&sig=AkFztocUdl6PLhbi6wIAcQa2XlNdW2U7Yqj6ok2UdDM%3D)

Load time

When local devices are connected, it can take up to 1 minute to retrieve their information before the Execution Environment edit page is displayed.

#### Real device Execution Environment

Only the devices set in the “Workspace settings” → “Devices to use” list will be displayed. If you want to change the devices used in the workspace, please check [Workspaces - Devices to use](https://help.autify.com/mobile/docs/settings-workspaces#devices-to-use-for-users-using-real-devices)

Please refer to [this article](https://help.autify.com/mobile/docs/en/overview-of-cloud-based-real-device-support) for more information on the "[Busy](https://help.autify.com/mobile/docs/en/overview-of-cloud-based-real-device-support#devices-that-are-busy)" and "[Any](https://help.autify.com/mobile/docs/en/overview-of-cloud-based-real-device-support#what-is-any)" options displayed in the device selection.

About HIGH DEMAND / HIGHEST DEMAND displayed in device type options

Devices displayed as HIGH DEMAND or HIGHEST DEMAND are often busy.

- HIGH DEMAND: Devices that had a 90~60% probability of being successfully secured and used in the past.
- HIGHEST DEMAND: Devices that had a less than 60% probability of being successfully secured and used in the past.  

![Image](https://cdn.document360.io/a099d8a2-cfd2-42ca-9906-68b4a337f4a5/Images/Documentation/Screenshot%202026-04-28%20at%2015.21.36.png?sv=2026-02-06&spr=https&st=2026-11-07T12%3A30%3A27Z&se=2026-11-07T13%3A30%3A27Z&sr=c&sp=r&sig=AkFztocUdl6PLhbi6wIAcQa2XlNdW2U7Yqj6ok2UdDM%3D)

### Advanced Settings

#### Override assertion failures

Override the behavior of assertion steps [When this step fails](https://help.autify.com/mobile/docs/reviewing-and-editing-your-scenario#when-this-step-fails). This applies to all Assertion, ML Assertion, and Prompt Assert steps in every scenario within the test plan. This setting is prioritized over step level settings. ![Image](https://cdn.document360.io/a099d8a2-cfd2-42ca-9906-68b4a337f4a5/Images/Documentation/Screenshot%202026-03-30%20at%2016.45.19.png?sv=2026-02-06&spr=https&st=2026-11-07T12%3A30%3A27Z&se=2026-11-07T13%3A30%3A27Z&sr=c&sp=r&sig=AkFztocUdl6PLhbi6wIAcQa2XlNdW2U7Yqj6ok2UdDM%3D)

#### Use a Fallback Device

If you have configured a fallback device in your workspace settings, enabling this option ensures that if the device specified for the test plan execution environment becomes unavailable due to a timeout, the test will automatically be re-executed on the device set as the fallback device.

## How to delete a test plan

1. Click on the test plan you want to delete.
2. Click on the vertical three dots menu in the top right corner.
3. Click on “Delete”.  

![deleteTestplan(en).png](https://cdn.document360.io/a099d8a2-cfd2-42ca-9906-68b4a337f4a5/Images/Documentation/deleteTestplan%28en%29.png?sv=2026-02-06&spr=https&st=2026-11-07T12%3A30%3A27Z&se=2026-11-07T13%3A30%3A27Z&sr=c&sp=r&sig=AkFztocUdl6PLhbi6wIAcQa2XlNdW2U7Yqj6ok2UdDM%3D)