BlinqIO Documentation

Execution Planner ​

Running tests manually works for quick checks, but real confidence comes from tests that run automatically on a schedule. The Execution Planner lets you define when and how your scenarios execute, so your test suite runs unattended at the times that matter most: before a release, overnight, or on a recurring cadence.

Creating a Schedule ​

  1. Go to the Executions page and click Plan Executions.
  2. Enter an Execution Name and select the Environment where scenarios will run.
  3. Create a Scenario Group: give it a name and select the scenarios to include by choosing tags.
  4. Set the Date and Time for when the execution should run.
  5. Click Apply to save the schedule.

INFO

You can skip the date/time step to save the execution as a Draft. It will not run automatically until you set a schedule.

Managing Executions ​

The Executions page lists all your scheduled and active plans. Two counters at the top provide a quick overview:

  • Active: the number of executions currently running.
  • All: the total count of all executions.

Execution List Details ​

Each execution entry displays:

  • Execution Info: the execution name and the user who created it.
  • Schedule: the configured day(s) and time.
  • Status: the current state of the execution.
    • Planned: a schedule has been set and the execution will run automatically.
    • Active: the execution is currently running.
    • Draft: the execution has been saved but no schedule is configured yet.
  • Enable/Disable Toggle: activate or deactivate the execution without deleting it.

Actions Menu ​

Hover over any execution in the list to reveal the actions menu:

  • Schedule Execution: set or update the schedule.
  • Run Now: trigger the execution immediately, regardless of the schedule.
  • Edit Execution: modify the execution plan, flows, or scenario groups.
  • Delete Execution: permanently remove the execution.

Execution Structure ​

Each execution follows a structured hierarchy that controls parallelism and ordering.

Flows ​

Flows run in parallel. Use multiple flows to maximize concurrency and reduce total execution time.

  • Add a new flow to an existing execution.
  • Duplicate an existing flow to reuse its scenario groups.
  • Delete a flow when it is no longer needed.

Scenario Groups ​

Scenario Groups run sequentially within their parent flow. This guarantees that scenarios inside a group execute one after another, in order.

  • Add multiple scenario groups inside a flow to organize different sets of scenarios.
  • Reorder scenario groups within a flow to change the execution sequence.
  • Edit any scenario group to add or remove scenarios.

Thread Allocation ​

Threads are assigned at the Scenario Group level. Multiple scenario groups can run in parallel across flows, depending on thread availability.

TIP

Structure your execution with independent flows for unrelated test areas and sequential scenario groups within each flow for tests that share state or depend on execution order.