# Managing plans

Virtuoso provides the ability to create Plans to aid in testing, allowing quick or scheduled execution of a specific scenario with the same configuration. The execution planner lists plans associated with your projects, allowing you to view configurations and perform a set of operations.

Plans for your project can be access by clicking on the plans icon in the sidebar. The plans page includes a summary of the jobs that were executed, and trends from recent executions.

Execution planner with plans

# Creating a plan

Click on Create execution plan to get started.

Execution planner

Identify the plan by providing a name, and choose a Goal (only goals with at least one journey will be presented).

Creating a plan (goal selected)

Now you can select the optional configuration desired for when the plan runs.

# Version selection

You can control the goal version a plan executes against using this option (by default it is set to the latest version).

# Maximum parallelism

Limits the number of browsers that can interact with your application at the same time.

Maximum parallelism with multiple device configurations

This limit is for each individual device configuration in the plan. That is, if you add a second configuration and have a maximum parallelism of 1, the effective max parallelism will be 2.

# Device configurations

Virtuoso's default Chrome browser always executes for a plan.

However, you can add a number of custom configurations to the plan. Each device configuration will be shown as its own job on the main dashboard page when the plan's project is active.

# Environment

By default, the plan will be executed using the default environment. Selecting an environment here will make the plan to be executed using the selected environment instead (see Environments for reference).

# Starting URL

You can change the starting point of the goal used by the plan defining a different URL in this field. Using a custom starting URL means that the plan will execute the selected goal using this URL for every journey on the goal in the first test step of the first checkpoint which is a Navigate to <Goal URL> test step.

# Schedule

Plans can run automatically at a specified date, and with a specified recurrence after the scheduled date:

  • Once;
  • Hourly;
  • Daily;
  • Weekly.

# Journeys to run

Specific configurations can be enabled/disabled for journeys associated with the goal and version settings of the plan:

  • Data-driven testing can be enabled using the data-driven toggle at the top right of the list;
  • Fine-grain control over what journeys to execute, and what journeys to execute as data-driven if enabled.

# Plan management

Execution planner with plans

The execution planner allows access to the following operations by clicking on the menu icon on the right side of a plan entry you can:

  • Execute the plan independent of any schedule settings;
  • Manage notifications customizing notification settings such as information to monitor, team members to notify or configure Slack integration (see Manage plan notifications);
  • Edit the plan, opening the Plan configuration page similar to the page used to create it;
  • Archive/Restore toggling the archived state of a plan. Old information can be stored without losing aggregated information collected by archiving a plan.

Impact on the plan's schedule

Archiving a plan suspends its execution, and restoring it will resume the schedule on the next available date/time according to the plan's schedule configuration.

Next schedule

The next schedule date/time indicates when Virtuoso will evaluate whether a plan should be executed (e.g., if the plan is still archived at this time it will not be executed).

# Manage plan notifications

You can set to be notified (via Email or Slack) about the execution outcome of a plan when a condition is met.

To access the plan notification configuration, click on the menu icon of a plan and select the option Manage Notifications.

Planner notification example

# Notifications enabled:

Enable or disable all notifications related to the plan (email and slack notifications).

# Conditions:

Here you can define a list of conditions to be notified (e.g. you can choose to be notified whenever an execution fails, or if the ratio of journeys passed out of all journeys is below 80%.

You can have multiple conditions and when at least one of the conditions is met you will receive a message.

Get notified when some executions fail

If you want to receive a notification when an execution has failed, you can configure the following condition Execution Status > Failure

Get notified when 10% of the journeys fails

If you want to receive a notification only when 10% or more of your journeys fail, you can configure the following condition Success Ratio > Lower Than > 90%.

# Send notification email to project members:

You can choose between notifing all members of the project or just a specific list of users.

Using the text field you can search for all users with access to the project and add the ones you wish to have them notified.

List of project members

You can also preview the list of project members by hovering the mouse over the total of project members.

# Slack Integration:

Specify an incoming Webhook URL that will be used to integrate with Slack. To achieve this, follow the steps in Incoming Webhooks to setup Slack and generate a new Webhook URL in the format https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX, and paste it on the configuration field below Slack Integration.

Next you will find an example of a slack message from a plan with a failed execution.

Planner notification Slack message

Test incoming webhook

You can test the webhook by clicking in the icon on the right

Last Updated: 2/18/2021, 5:18:45 PM