BlinqIO Documentation

Schedule Executions ​

The Execution Planner lets you automate test runs in the BlinqIO Cloud at scheduled times. This eliminates the manual effort of running tests every day on your system and ensures consistent, hands-free testing.

INFO

Execution Planner is currently in beta. Improvements are underway.

Create a Schedule Plan ​

  1. Go to the Executions page and click Plan Executions.
  2. Enter an Execution Name and select the Environment where tests will run.
    schedule-1
  3. Define a Scenario Group Name, then select the scenarios to include.
    schedule-2

TIP

Use meaningful tags for your scenarios. Tags make it easier to filter and group scenarios when creating schedules.

Define the Schedule ​

  1. Select the Date and Time for the execution.
    schedule-3

    INFO

    You can skip scheduling at this stage. The plan will be saved as a Draft and scheduled later.

  2. Click Apply to confirm.
    The plan appears in the Executions list and runs automatically at the configured time.
    image-20250613143150224

Manage Executions ​

The Executions page lists all scheduled and active runs. From here, you can view details, monitor progress, and manage plans.

Execution Counters ​

At the top of the page, you will see:

  • Active Executions: Number of executions currently running.
  • All Executions: Total number of scheduled executions.

Execution List ​

image-20250613151956141

Each execution shows:

  • Execution Info: Name and user who scheduled it.
  • Schedule: Planned day(s) and time.
  • Status:
    • Planned: A schedule is set.
    • Active: Execution is running.
    • Draft: Plan saved with no schedule.
  • Enable/Disable: Toggle to activate or deactivate the execution.
    image-20250613152200007

Hover over any execution to access the actions menu:

  • Schedule Execution: Set or update the schedule.
  • Run Now: Start immediately.
  • Edit Execution: Modify details.
  • Delete Execution: Remove the plan.

You can also sort by columns or search to quickly find an execution.
schedule-4

Execution Structure ​

Scheduled runs follow a structured format to control how scenarios are executed.

Flows ​

  • An execution can include one or more Flows. Flows run in parallel to maximize concurrency.
    schedule-5
  • Add new flows or duplicate existing ones to reuse groups.
    image-20250613120747005
  • Delete flows when they are no longer needed.
    image-20250613142217890

Scenario Groups ​

  • Each flow contains one or more Scenario Groups.
    image-20250613122313128
  • Scenario groups run sequentially within a flow.
  • Add multiple groups to organize scenarios logically.
    schedule-6
  • Reorder groups to change execution order.
    schedule-7
  • Edit groups to add or remove scenarios.
    schedule-8

Thread Allocation ​

  • Threads are assigned at the Scenario Group level.
    image-20250613142442150
  • Multiple groups can run in parallel depending on available threads.

INFO

Upcoming Enhancements

  • Browser selection: Choose which browser to use.
  • Viewport configuration: Set screen size or resolution (for example, Desktop 1024px).
  • Git branching: Current executions run on the main branch. Future updates will allow selecting branches.
    image-20250616101322447

Best Practices

  • Use clear execution names that describe the purpose of the run.
  • Organize scenarios with tags for easier grouping.
  • Start with smaller flows to verify schedules before scaling up.
  • Regularly review and disable unused executions to keep the list clean.
  • Use drafts for test planning before finalizing the schedule.