Skip to content

docs: fix invalid config keys and missing timeouts in parallel guide #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shossain786 merged 1 commit into from
Jul 23, 2026
Merged

docs: fix invalid config keys and missing timeouts in parallel guide #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 15 additions & 7 deletions docs-site/docs/guides/parallel.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,14 +15,22 @@ Selenium Boot supports parallel test execution out of the box. Configure the thr
## Configuration

```yaml title="selenium-boot.yml"
parallel:
enabled: true
threadCount: 4 # number of concurrent browser sessions
execution:
mode: local
parallel: methods # none (default) | methods | classes | tests
threadCount: 4 # number of concurrent browser sessions
maxActiveSessions: 4 # semaphore cap — cannot exceed threadCount

browser:
maxActiveSessions: 4 # semaphore cap — cannot exceed threadCount
name: chrome

timeouts:
explicit: 10
pageLoad: 30
```

`parallel`, `threadCount` and `maxActiveSessions` all live under `execution:` — see the [Configuration Reference](/docs/configuration#execution). `timeouts.explicit` and `timeouts.pageLoad` are required by every `selenium-boot.yml`, parallel or not.

`maxActiveSessions` acts as a hard ceiling on concurrent browsers. If `threadCount` is 4 but `maxActiveSessions` is 2, at most 2 browsers will run at the same time.

---
Expand Down Expand Up @@ -137,8 +145,8 @@ TestNG creates a new instance of each test class per thread, so instance fields
## Disabling parallel execution

```yaml
parallel:
enabled: false
execution:
parallel: none
```

Or simply omit the `parallel` block — sequential execution is the default.
Or simply omit `execution.parallel` — `none` (sequential execution) is the default.
Loading