BlinqIO Documentation

Running Tests ​

BlinqIO supports multiple ways to run your tests: locally during development, in the cloud for parallel execution, and from CI/CD pipelines for automated workflows. Choose the method that fits your current need, or combine them for full coverage.

Execute Tests Locally ​

Local execution is the fastest way to verify a scenario while you are building or debugging it.

  1. Go to the Features page.
  2. Select the scenario you want to run.
  3. Click Execute all steps.
  4. A browser window opens alongside a terminal showing real-time execution progress.
  5. When the run completes, open the Reports page to view the results.

Execute with AI Recovery ​

AI Recovery detects failures at runtime, identifies the root cause, and attempts to regenerate the failing step automatically.

  1. On the scenario page, click the dropdown arrow beside the Execute button.
  2. Select Execute scenario with AI Recovery.
  3. The scenario runs with recovery enabled. If a step fails, BlinqIO's AI analyzes the error, regenerates the step, and resumes execution from that point.

The resulting report includes root cause details and the retraining reason. See Root Cause Analysis for more information.

Execute in BlinqIO Cloud ​

Cloud execution is designed for running large test suites with parallel support across multiple browsers.

  • Browser support: Chromium is the default browser. Additional browsers can be configured per execution.
  • Parallelism: use Flows to run scenario groups in parallel (see Execution Structure).
  • Scheduling: set a specific date and time, or trigger runs on demand.

To schedule a cloud execution, see Creating a Schedule.

Monitor Executions ​

While tests are running in the cloud, you can track progress in real time:

  1. Go to the Executions page.
  2. Open the Active tab to see all currently running executions.
  3. Each active execution shows live status updates as scenarios complete.
  4. Once the run finishes, open Reports to review the full results.

Execute from CI/CD ​

Integrate test execution into your build pipeline by using the pre-filled command available from the Executions page.

  1. Go to the Executions page.
  2. Click How to run in CI/CD to get a ready-to-use command.
  3. Copy the command into your CI/CD pipeline configuration.

Customizing the CI/CD Command ​

The generated command can be customized with the following flags:

FlagDescription
--run-nameSet a custom name for the execution run
BROWSERSpecify the browser to use (e.g., chromium, firefox, webkit)
HEADLESSRun the browser in headless mode (true or false)
--nameTarget a specific scenario by name

Example ​

bash
BROWSER=chromium HEADLESS=true npx blinqio run --run-name "Nightly Regression" --name "Login Flow"

Combining Execution Methods ​

These execution methods are not mutually exclusive. A common workflow:

  1. Develop locally: run scenarios with local execution while building tests.
  2. Validate with AI Recovery: enable recovery for complex scenarios to catch and auto-fix flaky steps.
  3. Schedule in the cloud: set up nightly or pre-release runs in the Execution Planner.
  4. Gate deployments: add the CI/CD command to your pipeline so tests run before every merge or deploy.