Skip to main content

Execution Behavior: Max Retries & Max Parallelism

Written by Ines
Updated over 3 weeks ago

Overview

The Execution Behavior settings allow users to configure how test cases are executed, including concurrency control and retry behavior. These settings are available in the Run Settings modal when executing test sets or bulk test cases.

Max parallelism Purpose

Some Test Cases may impact shared application state or behavior, causing other tests to fail when run in parallel. This feature enables users to control execution concurrency to prevent flaky test failures caused by concurrent execution.

Settings overview

You can configure Max retries and Max parallelism in the Run modal, under Execution behavior.

Setting

Description

Default Value

Max Retries

Maximum number of retries for a failed test case during this run

0

Max Parallelism

Number of test cases run at the same time

2

This modal appears whenever you execute:

  • A single test case.

  • Multiple test cases (from a Test Set or through bulk execution).

Max Retries

The Max Retries setting controls how many times a failed test case will be automatically re-executed during a test run.

Property

Value

Default Value

0 (no retries)

Minimum Value

0

Maximum Value

2 (all plans)

Input Type

Number input with increment/decrement controls

Behavior

  • When a test case fails, it will be automatically retried up to the specified number of times

  • In the Test Runs view, only the final execution result is displayed

  • In the Test Case list view, all execution attempts are shown

Max Parallelism

The Max Parallelism setting controls how many test cases can be executed simultaneously.

Property

Value

Default Value

2

Minimum Value

1 (sequential execution)

The maximum is automatically capped based on your subscription plan:

  • Starter plan: up to 2 concurrent test cases

  • Pro / Enterprise plans: up to 10 concurrent test cases, or the total number of test cases in the run, whichever is lower

API / CI/CD Integration

The Max Parallelism and Max Retries parameters are also available through the API for CI/CD integrations. When queuing test cases via the API, include these optional parameters:

Parameter

Type

Description

maxParallelism

integer

Number of test cases to run concurrently

maxRetries

integer

Maximum retry attempts for failed tests (0-2)

Did this answer your question?