Skip to content
Bitassert
Documentation

Web Automation

Guides for authoring, running and analysing tests across web automation, API and performance — plus setup, collaboration and release notes.

Test Run Configs

Test Run Configs define how a Web test runs in the cloud. They control browser and OS settings, timeouts, delays, screenshot capture, and what happens when a step fails. Create and manage them per project from Web → Test Run Configs. When you start a cloud run, select a config together with a run tag.

Test Run Config settings

Web Test Run Config overviewCommon settings (all types)Namelabel (ex:Ubuntu_Chrome)Automation Type(ex:automation_web)Step Delayseconds between steps (ex:1)On Step Failureaction (ex:Stop)Web automation settings (automation_web)Resolutionscreen size (ex:1920x1080)Step/Page Timeoutmax wait (ex:5s)Element Timeoutfind element (ex:1s)Action Delaybetween actions (ex:1s)Screenshot Capturewhen taken (ex:On failure)List viewshows OS + browser per configOS Type(ex:Ubuntu)OS Version(ex:11)Browser Name(ex:Chrome)Browser Version(ex:141)Create: Web → Test Run Configs → Create → set fields → SaveCloud runs only · not used for Local Agent

Note:

  • Test Run Configs are used for Cloud runs only. They are not used for Local Agent runs.
  • At least one Web testcase exists if you plan to run immediately after creating a config.

Create a Test Run Config

  1. Go to Web > Test Run Configs and click Create.
    2. Web Testcases tab with stepgroup execution
  2. In the Create Test Run Config modal, set Name (for example ubuntuChrome141), Automation Type automation_web, Resolution 1920x1080, timeouts 5 / 1, delays 1 / 1, OS Ubuntu 22, and browser Chrome 141.
    3. Web Testcases tab with stepgroup execution
  3. Click Create to store the config.

How configs are used

Select a saved config when you run via Cloud (tag + config + optional release). See for the full run workflow.

Create from the run dialog

  1. Go to Web > Testcases and click Run on a testcase (for example SalesLeadCreation) in the Actions column.
    2. Web Testcases list with Run button in the Actions column
  2. In the Test Run Config field, click + Add Item.
    3. Web Testcases list with Run button in the Actions column
  3. Enter config details (for example ubuntuChrome141, automation_web, 1920x1080, OS Ubuntu 22, browser Chrome 141) and click Create.
    4. Web Testcases list with Run button in the Actions column
  4. In the Add Tag dialog, enter a Tag (for example TestRun), select the Test Run Config (for example Ubuntu_ChromeV), and optionally choose Major Release and Minor Release.
    5. Web Testcases list with Run button in the Actions column
  5. Click Save to start the cloud execution.

Practical tips

  • Create separate configs for different environments (for example, Chrome on Windows, Firefox on macOS) so teams can run the same tests on the right setup without changing the testcase.
  • Use clear config names that include browser and OS so runners pick the right one quickly.
  • Review timeout and screenshot settings before running long or flaky flows in the cloud.

Expected outcome

Reusable Web Test Run Configs are saved in the project and available when starting cloud runs. Each config captures the browser, OS, timing, screenshot, and failure settings needed for consistent cloud execution.