Unit
- Selenium Suite: Selenium is a collection of tools for automating web browsers. It includes Selenium WebDriver for direct browser control, Selenium Grid for running tests on multiple machines in parallel, and Selenium IDE for recording and playback during exploratory testing. Selenium Remote Control (RC) is deprecated and should not be used in new projects.
- WebDriver: The core component that communicates directly with browsers via native automation APIs. It supports multiple programming languages including Java, Python, C#, Ruby, and JavaScript. Each browser has its own driver implementation, such as ChromeDriver for Google Chrome and GeckoDriver for Firefox.
- Grid: Enables distributed test execution across different browser and operating system combinations. It uses a hub-and-node architecture where a central hub receives test requests and forwards them to registered nodes. This reduces execution time by running tests in parallel.
- Browser Compatibility: Selenium supports all major browsers: Chrome, Firefox, Safari, Edge, and Internet Explorer. Cross-browser testing ensures that web applications function correctly regardless of the user's browser choice. Each browser requires a specific driver executable.
- Language Bindings: Selenium provides official client libraries for Java, Python, C#, Ruby, and JavaScript (Node.js). The choice of language depends on team expertise and project requirements. All bindings expose a consistent API, making it easy to switch between languages.
- Limitations: Selenium cannot automate desktop applications, mobile native apps (without Appium), or CAPTCHA controls. It does not manage test data or reporting built-in, so these must be handled by external frameworks. Performance testing is also beyond its scope.
- When to Automate: Ideal for regression tests, smoke tests, and repetitive scenarios. Tests should be stable, have clear expected outcomes, and run frequently. Automated testing pays off when the same test suite is executed multiple times over the project lifecycle.
- Comparison with Other Tools: Unlike commercial tools like HP UFT (now Micro Focus) or TestComplete, Selenium is open source and highly customizable. It integrates well with DevOps toolchains but requires more coding effort compared to record-and-playback tools. Cypress and Playwright are newer alternatives but have less browser coverage.
Code Example
XML
<!-- Maven dependency for Selenium Java -->
<dependency>
<groupId/org.seleniumhq.selenium</groupId>
<artifactId/selenium-java</artifactId>
<version/4.15.0</version>
</dependency>This Maven dependency pulls in all Selenium WebDriver libraries along with the necessary browser drivers. The version should match the latest stable release. After adding this to your pom.xml, run mvn clean install to download the artifacts.
System Architecture
Pattern: Client-Server with WebDriver Protocol
Components:
- Test Code: Written in Java, Python, etc., using Selenium API calls.
- WebDriver API: Translates commands into HTTP requests to browser driver.
- Browser Driver: A standalone executable (e.g., chromedriver) that receives commands via JSON Wire Protocol (now W3C WebDriver standard) and controls the browser natively.
- Browser: Executes actions like click, type, navigate, and returns page state.
Quick Revision
- Selenium is a suite of tools: WebDriver, Grid, IDE (RC deprecated).
- WebDriver communicates directly with browsers using native automation protocols.
- Grid enables parallel execution across machines and browsers.
- Selenium supports Java, Python, C#, Ruby, and JavaScript.
- Limitations include no CAPTCHA handling and no built-in reporting.
- Automation is most beneficial for regression and repetitive tests.