Sample questions
Ta Cross Browser Parallel ExecutionDifficulty 1
What is the primary purpose of Selenium Grid in a test automation setup?
- aTo distribute WebDriver test execution across multiple machines and browser combinations✓
- bTo automatically generate test cases from user stories without any manual scripting
- cTo replace the need for browser drivers by rendering pages purely in Node.js
- dTo convert manual exploratory testing notes into automated test scripts, a task normally handled by record-and-playback tools rather than any Grid component
Explanation:Selenium Grid lets you route WebDriver sessions to different remote machines (nodes) so tests can run in parallel across multiple browsers, versions, and operating systems instead of one browser at a time on one machine.
Ta Cross Browser Parallel ExecutionDifficulty 1
In the Selenium Grid hub-and-node architecture, what role does the hub play?
- aIt executes the actual browser instances where tests run
- bIt receives test requests and routes each session to an available matching node✓
- cIt stores the final HTML test reports generated by every node after each session finishes, so they can be reviewed later
- dIt compiles the test code before sending it to the browser
Explanation:The hub is the central point that accepts incoming WebDriver session requests and forwards them to a registered node that matches the requested browser/platform capabilities; the actual browser runs on the node, not the hub.
Ta Cross Browser Parallel ExecutionDifficulty 1
In Selenium Grid terminology, what is a "node"?
- aA configuration file that lists which tests should run first
- bA single test case written for one specific browser version
- cA reporting dashboard that aggregates pass/fail counts and screenshots from multiple test runs across the whole Grid
- dA machine (physical, virtual, or containerized) that registers with the hub and runs browser instances✓
Explanation:A node is a machine that registers itself with the hub, advertises the browsers/platforms it supports, and actually launches and runs the browser instances that execute the test steps.
Ta Cross Browser Parallel ExecutionDifficulty 1
Why is running Selenium Grid nodes inside Docker containers a common practice?
- aDocker eliminates the need to install any browser binaries at all
- bContainers automatically fix flaky test locators without configuration
- cEach container provides an isolated, reproducible browser environment that can be started or torn down on demand✓
- dDocker containers always run browser automation faster than any other execution method, purely because of the container runtime itself
Explanation:Docker containers package a specific browser and driver version into an isolated environment that can be spun up or destroyed quickly and consistently, making it easy to scale node capacity up and down without dependency conflicts between environments.
Ta Cross Browser Parallel ExecutionDifficulty 2
What general capability do cloud-based browser grid services (such as commercial device/browser farms) typically provide beyond a self-hosted Selenium Grid?
- aThe ability to skip writing WebDriver-compatible test code entirely
- bA large, ready-made matrix of real browsers, versions, and operating systems without maintaining the infrastructure yourself✓
- cAutomatic conversion of manual test cases into Playwright scripts
- dA guarantee that all flaky tests are eliminated automatically, regardless of how poorly the underlying test code itself is written
Explanation:Cloud browser grid services host and maintain a wide combination of real browsers, versions, and operating systems (including mobile devices) so teams do not have to provision and maintain that infrastructure themselves; they still require valid WebDriver-compatible tests to run against.
Ta Cross Browser Parallel ExecutionDifficulty 2
What does "sharding" mean in the context of Playwright test execution?
- aSplitting the total set of test files across multiple machines or processes so each shard runs only a subset✓
- bSplitting a single test file into multiple smaller assertion functions
- cEncrypting test data before it is sent to the browser
- dAutomatically retrying only the failed assertions within a test, without re-running the rest of that test's steps
Explanation:Sharding in Playwright divides the full test suite into a specified number of shards (e.g. --shard=1/4), and each shard runs on a different machine or process, executing only its assigned subset of test files to reduce wall-clock time.