From 1a1d130d40ad461e8fee85daa25577f384b36aa9 Mon Sep 17 00:00:00 2001 From: Mohammad Saddam Hossain Date: Mon, 27 Jul 2026 07:27:10 +0530 Subject: [PATCH] docs: remove false "parallel: tests" claim from docs (#35) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ExecutionValidator only accepts none/methods/classes at suite bootstrap; docs advertised TestNG's `tests` mode too, sending users who copied it into an IllegalStateException before any test runs. Fixes three lines in guides/parallel.md (inline config comment, the "works with all of them" claim, and the `tests` table row) plus two more instances found in the same sweep in configuration.md (the inline comment and the `parallel` value table). Each spot now states plainly which values are validated and that others are rejected at bootstrap, instead of silently dropping the row — so a TestNG user looking for `tests` finds the explanation, not a gap. The error message itself ("Parallel execution configuration missing" for an unsupported value, not a missing one) is a known follow-up, deliberately out of scope here per the current roadmap gate. Co-Authored-By: Claude Opus 5 (1M context) --- docs-site/docs/configuration.md | 5 ++--- docs-site/docs/guides/parallel.md | 5 ++--- 2 files changed, 4 insertions(+), 6 deletions(-) diff --git a/docs-site/docs/configuration.md b/docs-site/docs/configuration.md index 312dfa1..f40fe60 100644 --- a/docs-site/docs/configuration.md +++ b/docs-site/docs/configuration.md @@ -45,7 +45,7 @@ execution: baseUrl: https://your-app.com gridUrl: http://localhost:4444 # only for remote mode - parallel: none # none | methods | classes | tests + parallel: none # none | methods | classes threadCount: 1 # ignored when parallel: none maxActiveSessions: 5 # max concurrent browser instances (semaphore) @@ -181,14 +181,13 @@ Use `per-suite` when your suite has many sequential tests and browser startup ti ## Execution ### `parallel` -Maps directly to TestNG parallel execution mode. Thread count is set via `threadCount`. +Maps directly to TestNG parallel execution mode. Thread count is set via `threadCount`. Selenium Boot validates this value at suite bootstrap and rejects anything outside the three below — TestNG's `tests` mode is not currently accepted. | Value | Behaviour | |---|---| | `none` | Sequential execution (default) | | `methods` | Each `@Test` method runs in its own thread | | `classes` | Each test class runs in its own thread | -| `tests` | Each `` block in testng.xml runs in its own thread | ### `maxActiveSessions` Maximum concurrent browser instances. Tests wait (up to 30s) for a slot rather than failing immediately. Prevents resource exhaustion in parallel runs. diff --git a/docs-site/docs/guides/parallel.md b/docs-site/docs/guides/parallel.md index bddf3f5..da768af 100644 --- a/docs-site/docs/guides/parallel.md +++ b/docs-site/docs/guides/parallel.md @@ -17,7 +17,7 @@ Selenium Boot supports parallel test execution out of the box. Configure the thr ```yaml title="selenium-boot.yml" execution: mode: local - parallel: methods # none (default) | methods | classes | tests + parallel: methods # none (default) | methods | classes threadCount: 4 # number of concurrent browser sessions maxActiveSessions: 4 # semaphore cap — cannot exceed threadCount @@ -85,13 +85,12 @@ You do not need to do anything special in your tests. `getDriver()` always retur ## Parallel modes -TestNG supports several parallel modes. Selenium Boot works with all of them: +TestNG supports several parallel modes. Selenium Boot currently validates `execution.parallel` against `none`, `methods`, and `classes` — any other value (including TestNG's `tests` mode) is rejected at suite bootstrap, before any test runs. | Mode | Description | Recommended | |---|---|---| | `methods` | Each test method runs in its own thread | Best general choice | | `classes` | Each test class runs in a thread | Use when tests within a class must be sequential | -| `tests` | Each `` tag in suite XML runs in a thread | For suite-level isolation | ---