Bromine focuses on end-to-end tests: it relies on Selenium to exercise a
real system, not to simulate it.

While Selenium serves as the essential foundation enabling end-to-end testing,
WebDriver alone offers too low a level of abstraction.
When we describe some behaviour that our system must exhibit, we usually think
about how users interact with the UI and how this one is expected to respond to
those interactions. We do not think about the browser as the main actor, but
indeed as part of the application. In the context of Object-Oriented Programming,
as developers we tend to reason in terms of UI objects interacting with the user
or with other parts of the system.
Given this perspective shift, Bromine adopts PageObject Pattern as its cornerstone.

The three basic building blocks of Bromine's conceptual model are WebApplication,
WebPage and WebElement.

WebElements are responsible for locating and automatically refreshing themselves relieving the programmer of the burden of explicitly handling Selenium's
StaleElementExceptions.