Schedule Executions

The Execution Planner enables automated test runs at scheduled times in the BlinqIO Cloud environment. This removes the need for manual execution and ensures consistent, hands-free testing.

Note

Execution Planner is currently in beta with improvements underway.

Create a Schedule Plan

1. Open the Executions page and click Plan Executions.

2. Enter an Execution Name and select the Environment where tests will run.

   

3. Define a Scenario Group Name, then select the relevant scenarios to include in the group.

   

TIP

Scenarios are grouped using tags. Adding meaningful tags improves filtering and grouping during schedule creation.

Define the Schedule

1. Select the desired Date and Time for the test execution.

   

Optional

A schedule can be skipped at this stage. The plan will be saved in Draft mode and can be scheduled later.

2. Click Apply to confirm and create the schedule.

The plan appears in the Executions list and will run automatically at the configured time.

Manage Executions

The Executions page lists all your scheduled and running executions. From here, you can view execution details, monitor active runs, and manage existing plans.

View Executions List

The page shows two main counters at the top:

• Active Executions : The number of executions currently running.
• All Executions : The total count of scheduled executions.

Execution List Details

Each execution entry displays:

• Execution Info : Shows the Execution Name and the User who scheduled it.

• Schedule : Displays the scheduled day(s) and time.

• Status :

  Planned: Execution has a scheduled time set.

  Active: Execution is currently running.

  Draft: Execution has been saved but no schedule is set yet.

• Enable/Disable: Toggle button to activate or deactivate the execution.

• An actions menu which appears when you hover any execution from the list, with the following options:
  • Schedule Execution: Set or update the schedule.
  • Run Now: Start the execution immediately.
  • Edit Execution: Modify the execution plan.
  • Delete Execution: Remove the execution.

Additionally,

• You can sort the list using any column.
• You can also search to quickly find a specific execution from the list.

Execution Structure

When a scheduled run starts, the execution follows a defined structure that organizes and controls how scenarios are executed.

Flows

• Each execution can contain one or more Flows, which run in parallel to maximize concurrency.

  

• You can add new flows to an existing execution, or duplicate an existing flow to reuse its scenario groups.

  

• You can also delete a flow from an execution if it’s no longer needed.

  

Scenario Groups

• Each flow contains one or more Scenario Groups.

  

• Scenario groups run sequentially within their flow. This ensures scenarios inside a group execute one after another, in order.

• You can add multiple scenario groups inside a flow to organize different sets of scenarios logically.

  

• You can reorder scenario group inside a group if you want to change the execution sequence.

  

• You can edit any scenario group to add or remove scenarios as needed.

  

Thread Allocation

• Threads are assigned at the Scenario Group level.

  

• Multiple scenario groups can run in parallel depending on thread availability.

Upcoming Enhancements

Support for

• Browser selection : choose the browser used for execution
• Viewport configuration : set the screen size or resolution for test execution ( for example, Desktop 1024px )
• Git branching : currently, planned executions run on the main branch for Git-integrated projects. In future, branching support will allow selecting different branches for executions.