You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3d8334b
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: CHANGELOG.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/).
11
11
12
12
-**Fix: `@PreCondition` session restore on a fresh browser** — the cached cookies and localStorage were silently dropped when the next test started on `about:blank`, so only the first test per thread was logged in. Restore now navigates to the origin the session was captured on first.
13
13
14
+
-**LambdaTest cloud provider** — `execution.mode: lambdatest` now creates W3C
15
+
`LT:Options` sessions, supports environment-based credentials and capability
16
+
overrides, and links each cloud session from the HTML report. (#197)
17
+
18
+
-**Cloud execution mode validation** — `execution.mode` now accepts the
19
+
existing `browserstack` and `saucelabs` providers, alongside `local`,
20
+
`remote`, and the new `lambdatest` provider.
21
+
14
22
-**Trace shows browser console errors** — when `browser.captureConsoleErrors: true`, the JS errors collected for a test now appear in its trace file under "Console Errors", next to the steps and failure details, so a shared trace includes what the browser logged. No change when the option is off. (#130)
15
23
16
24
-**Network mocking on Firefox via WebDriver BiDi** — `networkMock().stub(...)` now uses WebDriver BiDi network interception under the hood when supported by the driver (including Firefox and BiDi-enabled drivers), falling back to Chrome DevTools Protocol (CDP) for Chromium-based drivers. The existing stubbing API (`returnJson`, `returnBody`, `returnStatus`, `delay`, `clear`) works identically across Chrome and Firefox. (#196)
Copy file name to clipboardExpand all lines: docs-site/docs/changelog.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,14 @@ All notable changes to Selenium Boot are documented here.
11
11
12
12
## [Unreleased]
13
13
14
+
-**LambdaTest cloud provider** — `execution.mode: lambdatest` now creates W3C
15
+
`LT:Options` sessions, supports environment-based credentials and capability
16
+
overrides, and links each cloud session from the HTML report. (#197)
17
+
18
+
-**Cloud execution mode validation** — `execution.mode` now accepts the
19
+
existing `browserstack` and `saucelabs` providers, alongside `local`,
20
+
`remote`, and the new `lambdatest` provider.
21
+
14
22
-**Trace shows browser console errors** — when `browser.captureConsoleErrors: true`, the JS errors collected for a test now appear in its trace file under "Console Errors", next to the steps and failure details, so a shared trace includes what the browser logged. No change when the option is off. (#130)
15
23
16
24
-**Network mocking on Firefox via WebDriver BiDi** — `networkMock().stub(...)` now uses WebDriver BiDi network interception under the hood when supported by the driver (including Firefox and BiDi-enabled drivers), falling back to Chrome DevTools Protocol (CDP) for Chromium-based drivers. The existing stubbing API (`returnJson`, `returnBody`, `returnStatus`, `delay`, `clear`) works identically across Chrome and Firefox. (#196)
Copy file name to clipboardExpand all lines: docs-site/docs/cloud-execution.md
+73-4Lines changed: 73 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,16 @@
1
1
---
2
-
description: "Run Selenium tests on BrowserStack and Sauce Labs with zero code changes. Switch from local Chrome to cloud browsers by editing one config line."
2
+
description: "Run Selenium tests on BrowserStack, Sauce Labs, and LambdaTest with zero code changes. Switch from local Chrome to cloud browsers by editing one config line."
3
3
id: cloud-execution
4
4
title: Cloud Execution
5
5
sidebar_position: 12
6
6
---
7
7
8
8
# Cloud Execution
9
9
10
-
Selenium Boot supports running your test suite on **BrowserStack** and **Sauce Labs** with zero test-code changes. Switch from local Chrome to a cloud browser farm by changing one line in `selenium-boot.yml`.
10
+
Selenium Boot supports running your test suite on **BrowserStack**, **Sauce Labs**, and **LambdaTest** with zero test-code changes. Switch from local Chrome to a cloud browser farm by changing one line in `selenium-boot.yml`.
11
11
12
12
:::caution Requires Selenium Boot 3.2.1+
13
-
Cloud execution (`execution.mode: browserstack`or `saucelabs`) requires **Selenium Boot 3.2.1 or later**. It does not work in any earlier release — config loading rejects any `execution.mode` other than `local` or `remote` at startup — regardless of what the examples on this page show.
13
+
Cloud execution (`execution.mode: browserstack`, `saucelabs`, or `lambdatest`) requires **Selenium Boot 3.2.1 or later**.
14
14
:::
15
15
16
16
---
@@ -25,6 +25,7 @@ All four execution modes share the same driver lifecycle — tests use `getDrive
25
25
|`remote`| Your own Selenium Grid / Selenoid / Moon |
26
26
|`browserstack`| BrowserStack Automate cloud |
27
27
|`saucelabs`| Sauce Labs cloud |
28
+
|`lambdatest`| LambdaTest cloud |
28
29
29
30
---
30
31
@@ -242,6 +243,64 @@ Ensure your BrowserStack / Sauce Labs plan allows the number of concurrent sessi
242
243
243
244
---
244
245
246
+
## LambdaTest
247
+
248
+
### Prerequisites
249
+
250
+
1. Sign up at [lambdatest.com](https://www.lambdatest.com)
251
+
2. Copy your LambdaTest username and access key from your account settings
252
+
253
+
### Config
254
+
255
+
```yaml title="selenium-boot.yml"
256
+
execution:
257
+
mode: lambdatest
258
+
lambdatest:
259
+
username: ${LT_USERNAME}
260
+
accessKey: ${LT_ACCESS_KEY}
261
+
platform: "Windows 11"
262
+
browser: chrome
263
+
browserVersion: latest
264
+
265
+
browser:
266
+
name: chrome
267
+
268
+
timeouts:
269
+
explicit: 10
270
+
pageLoad: 30
271
+
```
272
+
273
+
The provider uses LambdaTest's W3C `LT:Options` capability and the
274
+
`https://hub.lambdatest.com/wd/hub`hub URL. Keys under `capabilities` are
275
+
merged into `LT:Options`, so they override the generated defaults:
276
+
277
+
```yaml
278
+
execution:
279
+
mode: lambdatest
280
+
lambdatest:
281
+
username: ${LT_USERNAME}
282
+
accessKey: ${LT_ACCESS_KEY}
283
+
platform: "Windows 11"
284
+
browser: chrome
285
+
browserVersion: latest
286
+
capabilities:
287
+
build: "v2.1.0"
288
+
video: true
289
+
```
290
+
291
+
Set environment variables before running:
292
+
293
+
```bash
294
+
export LT_USERNAME=your_username
295
+
export LT_ACCESS_KEY=your_access_key
296
+
mvn test
297
+
```
298
+
299
+
After each test, the HTML report includes a **☁ View Session** link to the
300
+
LambdaTest session logs.
301
+
302
+
---
303
+
245
304
## Switching between environments
246
305
247
306
Use Maven profiles or environment variables to switch execution targets without changing any YAML file:
@@ -265,7 +324,7 @@ Keep separate YAML files per environment — each imports shared settings and on
265
324
266
325
```yaml title="selenium-boot.yml"
267
326
execution:
268
-
mode: browserstack # local | remote | browserstack | saucelabs
0 commit comments