1. Overview

2. Creating a test plan 

Navigate to Test Plans and click Create Test Plan.

2.1 Components of a test plan

 

• Name of the plan

• Description about the plan

• Run on: Select an agent to run test cases locally or on the cloud. Different environment options are provided depending on your selection. 
  
  For example, if you have an agent on your device that is connected to virtual devices, you’ll have the choice to run test cases on those virtual machines. On the other hand, selecting the default Zoho Cloud agent will allow you to run test cases on your configured environments.

• Tunnel: Select the required tunnel if you wish to execute your test cases within a remote or private network environment. <Learn more>
  

• Environments: Select an applicable environment to run the test cases. Click +Add Environments

  and select the environment type, such as Web, Android, iOS, or API.
  
  

  
  

  You can then configure details based on the selected platform:
  

  
  

  Web browser: Configure the environment name, browser, browser version, screen resolution, and execution framework. By default, tests run using Selenium, with Playwright (Beta) available as an alternative engine. Selenium is recommended for stable, well-established execution, while Playwright is better suited for faster execution and more modern capabilities.

  
  

  Android/iOS: Configure the environment name, OS version, device, and app to be tested.

  
  

  API: Environment for API will be configured.

Notes:

1. Test cases that don’t apply to the selected environment are skipped and are marked as Passed.

2. Only one platform type can be selected for each test plan. However, you can add multiple environments for the selected platform.

3. Choices for the environment fields vary depending on the selected agent.
   
   For example, if you have selected a local agent that has virtual devices, you’ll find environment options associated with the virtual devices. If you’re using the default Zoho Cloud, you’ll find options to run test cases on your configured environments.
   
   
4. Changing the agent type resets the selected environments in the plan.
   

• Test Suites: Select suites to be run.

• Environment Variable: The variables selected are environment variables. The values of environment variables overwrite the values of global variables during test plan execution.
  
• Parallel Run: This gives the count of how many test suites will run at a time.
  
  
  

• Schedule: Choose whether the test plan should be executed on a weekly basis, or as a one-time configuration.

• Start From: Select the date on which to commence the test plan.

• Run Time: This is the time at which the test plan will be executed. The options for this field will vary based on the selected date in the schedule Start From.

• Select Days: For this option, test plans will be executed only on selected days.

• Re-run on Failure: Choose your preferred action when test cases fail: either None, All Test Cases, or Only Failed Test Cases.

• Notifications: Trigger email notifications at various points in the test plan execution.
  
  
  

1. Started: When the test plan starts

2. Completed: When the test plan is successfully completed

3. Success: Provides an additional field to specify the percentage of execution success at which the notification should be triggered.

4. Fail: Provides an additional field to specify the percentage of execution failure at which the notification should be triggered.

5. Not executed (delay): When the test plan is terminated during its progress. 

When

1. Started: When the test plan starts

2. Completed: When the test plan is successfully completed

3. Success: Provides an additional field to specify the percentage of execution failure at which the notification should be triggered.

4. Fail: Provides an additional field to specify the percentage of execution failure at which the notification should be triggered.

Webhook 

Select the required webhook from the drop-down.

Note: Configuring notifications or webhooks aren’t mandatory —they’re optional fields to get notified on the test plan.

Note: The status toggle bar of the created test plan will be toggled on by default. You can toggle it off if you want to disable the particular test plan's execution.

3. Managing test plans

You can perform the following actions on created test plans:

1. View
   
2. Edit
   
3. Delete
   

3.1 View

This page provides an overview of all created test plans, along with their key details and management options:

 

1. Name: Displays the names of the test plans
2. Test Suites: Displays the count of test suites included within each test plan
3. Agent Type: Indicates the agent currently executing the test plan
4. Run Type: Shows the schedule configuration of the test plan (Once or Weekly)
5. Last Run: Specifies the last execution date and time of the test plan
6. Next Run: Displays the upcoming scheduled execution date and time for the test plan
7. Status:  A toggle button to enable or disable the execution of the test plan
8. Play {}: A button used to execute the test plan immediately
   
9. Test Plan Execution URL: Lets you fetch the test plan's execution URL, which can be used to configure your test plans in CI/CD tools like Jenkins
   

3.2 Edit

To edit a test plan, click on a test plan to open it. Make the necessary updates, then click Update to save your changes.

3.3 Delete

4. Related Links

1. Results
   
2. Test Case Summary
   
3. Run History