Parallel Testing Redefined: The Browserpooling Method
summary
Claim: WebDriver BiDi user contexts let multiple tests share one browser process while keeping storage isolated, so parallel tests run without spinning up separate browsers. Demo uses Selenium Java + WebDriver BiDi on Firefox Nightly, creates three tabs each assigned a new user context, runs them on three threads against a local Selenium Grid and in-cloud grid, and the tests pass. Result: one browser instance replaces three browser processes, cutting startup overhead and memory/CPU use — browserpooling and single browser multiple isolated tabs.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:04Private browsing modes
- 5:39Parallel testing challenges
- 7:23WebDriver Bidi overview
- 10:29User contexts for isolation
- 12:14Demo: Cookie-based isolation
- 14:45Traditional Selenium setup
- 17:31Sequential multi-browser tests
- 19:24Why single-browser parallel fails
- 20:52Parallel testing with WebDriver Bidi
- 23:07Code walkthrough: WebDriver Bidi tests
- 25:13Demo: Single-browser parallel execution
- 26:35Scaling with Grid and WebDriver Bidi
- 27:36Demo: Grid-based parallel testing
- 29:13Language support for contexts
- 30:21Benefits of browser pooling
- 31:29Q&A
related talks
17mParallel Execution of Auto-Tests with Selenium Grid
31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and its Integration with Selenium- 31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and...
30mLessons from testing browsers using WebDriver
42mReliable and Maintainable Webdriver Tests
40mSelenium Grid
30mBrowser Testing
26mHow browser automation works behind the scenes