Selenium enables the automation of web browsers and is particularly useful for testing web applications. It supports multiple programming languages and browsers, providing a flexible API for interacting with web pages.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Selenium is an open-source project for automating web browsers, allowing applications to be tested and controlled through their real browser interface.
Selenium began at ThoughtWorks in 2004, when Jason Huggins created JavaScriptTestRunner, which became Selenium. The project grew into a suite including WebDriver and became further grounded in the W3C WebDriver standard.
A test describes actions and expectations from a browser user’s perspective. WebDriver connects test code to the browser, which performs interactions and returns state. Robust tests wait for meaningful states and assert behavior rather than implementation details.
A standardized interface through which test code drives a browser natively.
Checks a flow across multiple layers from a user’s perspective.
Distributes browser execution across environments and devices.
Selenium matters for reproducible browser and regression tests across browsers and operating systems. Test stability depends on synchronized state, isolated data, and well-chosen assertions.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.