SeleniumHQ/fluent-selenium

FluentSelenium

FluentSelenium is a wrapper for Selenium 2+ (WebDriver) that adds a fluent interface style for working with the browser. It allows you easier and faster writing of Web UI Tests. Test code using FluentSelenium is terser and more elegant.

Of many benefits, FluentSelenium will attempt to transparently get past the stale element exception business.

FluentSelenium works with JUnit, TestNG, ScalaTest, JBehave, Cucumber for Java, or whatever JDK language you prefer. FluentSelenium works with Java (5+), Groovy, Scala, Clojure, and Kotlin.

Table of Contents

1. Table of Contents
2. Basic Use
3. Situations where the DOM is slowly changing
   • within()
   • without()
   • Elements in the DOM, but not visible immediately
   • Locators for Advanced JavaScript Frameworks
     • AngularJS 1.x
     • Other Web Frameworks
   • Stale Elements
4. Built-in Assertions
   • String Assertions
     • Text Changers
     • Regular Expressions
     • Hamcrest matchers
     • Within a period of time
   • Non-String Assertions
5. Locating Elements
   • Elements not located
6. Multiple elements
7. Using WebDriver and FluentWebDriver at the same time
8. Fluently matching/filtering over multiple elements
9. Visit each element to do something custom
10. Make a map from the matching elements
11. Exceptions
    • Alternate boolean handling of missing elements.
12. Monitoring
    • Take a Screenshot on error
    • Highlights on error
    • Coda Hale's Metrics library
13. Java 8 (and onwards) - more fluency
14. Including it in your project
    • Maven
    • Non-Maven
15. Changes
    • 1.20 (Apr 28, 2018)
    • 1.19 (Dec 31, 2017)
    • 1.18 (Jun 18, 2017)
    • 1.17 (Dec 20, 2016)
    • 1.16.1 (May 22, 2016)
    • 1.16 (Nov 29, 2015)
    • 1.15 (Nov 21, 2015)
16. More Reading

Basic Use

Regular HTML elements have Java methods that are named for them. Locators are optional, and are from WebDriver's regular set (by id, by css selector, by tag name, by xpath):

WebDriver wd = new FirefoxDriver();
FluentWebDriver fwd = new FluentWebDriver(wd);

fwd.div(id("foo")).div(className("bar")).button().click();

fwd.span(id("results")).getText().shouldBe("1 result");

Hyperlinks are marked as 'a' (anchor) in HTML, but we have represented those as link() in the fluent API.

As with all fluent interfaces, there is no point looking at strict API documentation (JavaDoc for Java), and you're better looking at example code, and this page is it (perhaps the blog entries of others too).

These days frameworks (and people) are making their own elements, and there is way to address those too:

WebDriver wd = new FirefoxDriver();
FluentWebDriver fwd = new FluentWebDriver(wd);

fwd.element("fooelementname").element("barelementname", className("bar")).button().click();

fwd.element("bazelementname", id("results")).getText().shouldBe("1 result");

Situations where the DOM is slowly changing

within()

There's a "within" capability in the fluent language. It will keep retrying a locator for a given period of time. The fluent expression (the locator) is given a chance find a slowly appearing element in the page, and do so in the minimum amount of elapsed time needed. Then when found, the fluent expression continues:

fwd.div(id("foo")).div(className("bar")).within(secs(5)).button().click();

fwd.within(secs(5)).div(id("foo")).span(className("baz")).button(className("ok")).click();

The within() operation will throw an exception after the elapsed time, if the element still hasn't appeared in the page's DOM.

As well as secs(..), there is also millis(..) and mins(..) for time periods.

It is explicit in its nature. if you don't do within there is no waiting. It doesn't last beyond the operation to the right of it.

Also see "String Assertions / within" (link) below.

without()

The opposite of "within", the "without" capability is going to wait for something to disappear. If the element is still in the page, it will keep waiting upto a given period of time, for it to disappear:

// No button in the div after 5 seconds:
fwd.div(id("foo")).div(className("bar")).without(secs(5)).button();

The element disappearing in the page means that the fluent expression stops there. Also, disappear means that the locator used to find the element does not find it. Thus the following does not mean that there is no span element, it just means that there is no span element with a class of "baz":

fwd.div(id("foo")).div(className("bar")).without(secs(5)).span(className("baz"));

This will throw an exception after the elapsed time, if it still hasn't disappeared from the page's DOM.

It is explicit in its nature. if you don't do within there is no waiting. It doesn't last beyond the operation to the right of it.

Selenium 1.0 had an API function isElementPresent. The 'without' functionality is akin to isElementNotPresent, or rather waitForElementToNotBePresent.

Elements in the DOM, but not visible immediately

Sometimes elements are within the DOM, but they are invisible for a period of time after an action of some sort. You can wait for elements to become visible, before fluently progressing:

fwd.input(id("textArea")).sendKeys("Mary Had A Little Lamb...");
fwd.div(id("discardChanges")).ifInvisibleWaitUpTo(millis(500)).click();

Locators for Advanced JavaScript Frameworks

AngularJS 1.x

AngularJS is an example of framework that does a huge amount of the heavy lifting in browser. While it's doing its magic, you are going to encounter timing issues. If you prefer, the 'within' and 'without' fluent methods above will help you overcome those issues, but there is a way of being smarter about waiting for Angular's magic to stop:

There's another library you can use in conjunction with Selenium/WebDriver and/or FluentSelenium called ngWebDriver that makes it far easier to test Angular applications.

Other Web Frameworks

Backbone, Knockout (etc) may have similar tricks, that you can use 'executeScript' to invoke, but we've not done the research to hook into them.

Stale Elements

Selenium-WebDriver, by default, does not recover findElement traversals where elements have gone stale. Selenium-WebDriver prefers to throw StaleElementReferenceException, which you have to catch and then do something with yourself. Retry is one option. FluentSelenium has build-in retry capability. Let us discuss that:

new RetryAfterStaleElement() {
    public void toRetry() {
        # will keep retrying from that fist div, if StaleElementReferenceException is encountered (up to 8 seconds)    
        System.out.println(div(id("thirdAddress")).div(className("fromto-column")).getText().toString());
    }
}.stopAfter(secs(8));

In this example, the element can go stale any time within the eight seconds and the whole traversal is restarted again and again. If you're trying to store variables, you'll have a problem with Java's inner-class rules, and have to use member variables/fields or do dirty tricks like:

final String selectedFlight[] = new String[1];
new RetryAfterStaleElement() {    
    public void toRetry() {
        # will keep retrying from that fist div, if StaleElementReferenceException is encountered (up to 8 seconds)
        selectedFlight[0] = div(id("thirdAddress")).div(className("fromto-column")).getText().toString();
    }
}.stopAfter(secs(8));

Use of the single-element array is that dirty trick, because of the need for the final keyword with Java for inner class variable sharing.

FluentSelenium can recover from a subset of StaleElementReferenceException situations. If the element going stale is the one that is leaf-most in your fluent expression, then it can be recovered automatically (and silently). It can do so without the new RetryAfterStaleElement() {...} logic.

This is a one-time deal though - if the element still stale after that hidden second attempt, then the exception is re-thrown. The hope is finding the element again in the DOM, relative to its parent with the same locator. In the case above, the "fromto-column" div being stale can be recovered automatically - even during the getText(). The "thirdAddress" div cannot be, at least when execution has transferred to the next div().

Sometimes your test suite is going to enjoy the hidden second attempt to get past StaleElementReferenceException, and sometimes you're going to have to use new RetryAfterStaleElement() {...}

Built-in Assertions

String Assertions

Many things return a string (actually a TestableString). Some elements of a page are designed to have a string representation. Input fields and spans are obvious, but any element supports getText() and WebDriver will try to make a chunk of text that represents that (often with carriage returns).

fwd.div(id("foo")).getText().shouldBe("1 bar");
fwd.div(id("foo")).getText().shouldNotBe("0 bars");
fwd.div(id("foo")).getText().shouldContain("bar");
fwd.div(id("foo")).getText().shouldNotContain("error");

See hamcrest matcher support below for more string assertions.

Text Changers

The getText() method can also take one or more TextChanger implementations. These can change the value of getText() before handing it rightwards to an assertion, like so:

There are supplied ones too: multiSpaceEliminator(), multiCREliminator(), trimmer(), tabsToSpaces(), toLowerCase(), toUpperCase(), crToChars("|")

Make your own too:

fwd.div(id("foo")).getText(new MyTextChanger()).shouldBe("1 BAR");

Concatenators

There is also a Concatenator that is available for getText() where that was implicitly a findElements (PLURAL). There is one supplied concatenator, delimitWithChars(..) used like so:

fwd.buttons(class("dialog_button")).getText(delimitWithChars("|")).shouldBe("OK|CANCEL");

Specifically we found TWO buttons, one with OK and one with CANCEL and we want to confirm we had both in one operation.

Regular Expressions

Regex is possible too, and it will ignore carriage returns (which Java pre-processes like so \n -> \\n)

fwd.div(id("foo")).getText().shouldMatch("\d bar");
fwd.div(id("foo")).getText().shouldMatch("[1-9] bar");
fwd.div(id("formErrors")).getText().shouldNotMatch("\d errors");

Hamcrest matchers

Any Hamcrest matchers are supported:

// requires static import of equalTo() from Hamcrest.	
fwd.div(id("foo")).getText().shouldMatch(equalTo("1 bar"));
fwd.div(id("formErrors")).getText().shouldNotMatch(equalTo("aardvark"));

Note: shouldMatch(..) and shouldNotMatch(..) work with regexes (above) and hamcrest matchers

Within a period of time

As shown above, you can transparently wait for the thing to become true (within/without to the right of the TestableString, and the shouldXxx rightmost):

fwd.div(id("foo")).getText().within(secs(10)).shouldBe("1 bar");
// text is '1 bar' to start, but within 10 secs is not:
fwd.div(id("foo")).getText().without(secs(10)).shouldBe("1 bar");

Div with ID of 'small' is in the DOM, and within 5 seconds its text changes to something that starts with 'start' -

// requires static import of startsWith() from Hamcrest.	
fwd.div(id("small")).getText().within(secs(5)).shouldMatch(startsWith("start"));	

Div with ID of 'small' is not in the DOM initially, but within 5 seconds it is and its text starts with 'start' -

// requires static import of startsWith() from Hamcrest.	
fwd.div(id("small")).within(secs(5)).getText().shouldMatch(startsWith("start"));	

The assertion is retried for the advised period and no longer. If not found an exception is thrown

Non-String Assertions

Any element has a location via getLocation(), which yields a Point Any element has a size via getSize(), which yields a Dimension Some elements have boolean from isDisplayed(), isEnabled() and isSelected()

All of those have assertions:

fwd.div(id("foo")).getLocation().shouldBe(new Point(1, 1));
fwd.div(id("foo")).getLocation().shouldNotBe(new Point(1, 1));

fwd.div(id("foo")).getSize().shouldBe(new Dimension(640, 480));
fwd.div(id("foo")).getSize().shouldNotBe(new Dimension(640, 480));

fwd.div(id("foo")).isEnabled().shouldBe(true);
fwd.div(id("foo")).isDisplayed().shouldBe(false);

Like for Strings, you can transparently wait for the thing to become true:

fwd.div(id("foo")).isDisplayed().within(secs(10)).shouldBe(true);

The assertion is retried for the advised period.

Locating Elements

WebDriver's own "By" locator mechanism is what is used. Here are examples using that:

by = By.id("id")
by = By.className("name")
by = By.tagName("table")
by = By.xpath("@foo = 'bar'") // XPath should always be your last choice for locating elements

New class FluentBy adds a few more locators:

by = FluentBy.attribute("ng-model")
by = FluentBy.attribute("ng-model", "shopperSelection.payPalPreferred")
by = FluentBy.composite(tagName("table"), className("paymentType"))
by = FluentBy.composite(tagName("table"), attribute("ng-click"))

One new one, strictClassName(), is where there is only one name in the class attribute for that element:

by = FluentBy.strictClassName("name")

The built-in WebDriver By.className() one allows for many names for the class attribute of an element, with the one specified being amongst them. For your app, strictClassName may be faster.

Elements not located

If WebDriver cannot find the element in the DOM for that locator, then an exception FluentExecutionStopped is thrown (see below).

Multiple elements

Just like WebDriver, FluentSelenium can return a collection of Elements matching a locator:

FluentWebElements elems = fwd.div(id("foo")).div(className("bar")).buttons();
elems = fwd.div(id("foo")).divs(className("bar"));
elems = fwd.divs(id("foo");

Look at the pluralization of the methods above, and that it only makes sense if it's the last in the fluent expression.

Using WebDriver and FluentWebDriver at the same time

Keep a hold of the wd instance you made as you instantiated everything and use it as you would expect.

RemoteWebDriver wd = new FirefoxDriver();
FluentWebDriver fwd = new FluentWebDriver(wd);
fwd.button(id("showHandOfCards")).click();
File src = wd.getScreenshotAs(OutputType.FILE);
FileUtils.copyFile(src, new File(pathname));

As you can creenshots and any functions on the sub-classes of WebDriver are possible. There's no need to subclass FluentWebDriver to get access to WebDriver, you had it already.

Turning a WebDriver WebElement into a FluentWebElement

ChromeDriver driver = new ChromeDriver();

driver.get("http://seleniumhq.github.io/fluent-selenium/basic.html");

FluentWebDriver fwd = new FluentWebDriver(driver);

// Classic WebDriver
WebElement div = driver.findElement(By.tagName("div"));

// carry on with FluentSelenium
fwd.fluentize(div).span().getText().shouldBe("Hello");

driver.close();

Fluently matching/filtering over multiple elements

Use a FluentMatcher instance (which is just a predicate)

class MyIntricateFluentMatcher implements FluentMatcher {
  public boolean matches(FluentWebElement webElement, int ix) {
    // do what you like here as long as it return true/false.
  }
}


FluentMatcher fm = new MyIntricateFluentMatcher();
// click on first matching one...
fwd.inputs(className("bar").first(fm).click();

// click on last matching one...
fwd.inputs(className("bar").last(fm).click();

// click on all matching matching ones...
listofMatching elements = fwd.inputs(className("bar").filter(fm)
listofMatching.click() // click them all

There are no instances of FluentMatcher built in, other than CompositeFluentMatcher which allows you to build up a larger matcher, and has 'both', 'any', 'all', 'either' functionality. There's also 'and' & 'or' cabailities to CompositeFluentMatcher.

Visit each element to do something custom

class MyFluentWebElementVistor implements FluentWebElementVistor {
  public void visit(FluentWebElement webElement, int ix) {
    // do what you like here
  }
}

FluentWebElementVistor v = new MyFluentWebElementVistor();
// do something on each element in a list, then click on them
fwd.inputs(className("bar").each(v).click();

Make a map from the matching elements

class MyFluentWebElementMap<String,String> implements FluentWebElementMap<String,String> {
  public void map(FluentWebElement webElement, int ix) {
    // note: <String,String> is only an example
    String key == webElement. // something
    String value == webElement. // something
    put(key,value);
  }
}

MyFluentWebElementMap m = new MyFluentWebElementMap();
Map<String,String> myMap = fwd.inputs(className("bar").map(m);
// map() effectively stops fluency, here.

Exceptions

Obviously you want tests using FluentSelenium to pass. Getting tests to be stable has also been a historical challenge for the Selenium world, but a real failure of previously working test, is worth debugging (before or after a developer commit that may have broken the build).

Fluent-Selenium throws 'FluentExecutionStopped' like so:

"WebDriver exception during invocation of : ?.div(By.className: item-treasury-info-box')).h3()"

That exception's getCause() will be the WebDriverException derivative that happened during the h3() invocation - implicitly before any subsequent operation like click(). That could well be 'NoSuchElementException' for when an element was not found.

Alternate boolean handling of missing elements.

Normal operation is for FluentSelenium to throw 'FluentExecutionStopped' wrapping WebDriver's 'NoSuchElementException' for the root cause.

With 'has()' and 'hasMissing()' you can receive true/false instead of getting exceptions like so:

boolean isMissing = fwd.hasMissing().div(id("foo"))
boolean isPresent = fwd.has().div(id("foo"))

As mentioned before, Selenium 1.0 had an API function called 'isElementPresent'. With FluentSelenium we're getting close to that again, as 'has' and 'hasMissing' preceding a thing that should or should not be there, are functionally equivalent.

Monitoring

Fluent Selenium can generate monitors failing interactions with the browser. It can also see what fluent operation were started/ended. Refer the Monitor interface.

You specify a monitor choice by using the right constructor for FluentWebDriver (and pass in a Monitor instance). There's a default monitor that does nothing, so you don't have to choose a constructor that uses a monitor.

We have three implementations presently, and if you want to use more than one, wrap them in a CompositeMonitor:

new FluentWebDriver(new FirefoxDriver(), new CompositeMonitor(one, two, three));

Take a Screenshot on error

When a 'FluentExecutionStopped' failure happens, you can get automatic screenshots. In the case of running from JUnit or TestNG under Maven control do the following, to get automatic Test-Class name & Method name in the file-name of the PNG:

ffd = new FirefoxDriver();
myScreenShotOnError = new ScreenShotOnError.WithUnitTestFrameWorkContext(ffd, OneOfYourClasses.class, "test-classes", "surefire-reports/");
fwd = new FluentWebDriver(ffd, myScreenShotOnError);

If you're not wanting that JUnit/TestNG automatic file naming, do this instead:

ffd = new FirefoxDriver();
myScreenShotOnError = new ScreenShotOnError(ffd, OneOfYourClasses.class, "test-classes", "surefire-reports/");
fwd = new FluentWebDriver(ffd, myScreenShotOnError);

myScreenShotOnError.setContext("something_that_has_meaning_in_a_file_name")
div(id("foo")).click();
myScreenShotOnError.setContext("something_else_that_has_meaning_in_a_file_name")
input(id("bar")).sendKeys("abc");

Highlights on error

This draws a red dotted two-pixel line around the relevant part of the page, when an FluentExecutionStopped is thrown. You'd use it in conjunction with ScreenShotOnError above:

ffd = new FirefoxDriver();
myScreenShotOnError = ...
fwd = new FluentWebDriver(ffd, new CompositeMonitor(new HighlightOnError(ffd), myScreenShotOnError));

If you don't want a red dashed two-pixel line, subclass HighlightOnError and override one of executeScript(), highlightOperation() or highlightValue().

Coda Hale's Metrics library

Also shown here is how to hook that up to a JUnit4 suite running under Maven.

The separate listener class:

public class MyRunListener extends RunListener {
    public static final CodaHaleMetricsMonitor codahaleMetricsMonitor = new CodaHaleMetricsMonitor("com.paulhammant.fluentSeleniumExamples.");
    @Override
    public void testRunFinished(Result result) throws Exception {
        super.testRunFinished(result);
        final ConsoleReporter reporter = ConsoleReporter.forRegistry(codahaleMetricsMonitor.getMetrics())
                .convertRatesTo(TimeUnit.MILLISECONDS)
                .convertDurationsTo(TimeUnit.MILLISECONDS)
                .outputTo(System.out)
                .build();
        reporter.report();
    }
	// More likely, you'd send stats to Graphite (etc).
}

Hooking that into each/all FluentWebDriver usages:

public class Home extends FluentWebDriver {
    public Home(WebDriver delegate) {
        super(delegate, MyRunListener.codahaleMetricsMonitor);
    }
	// etc
}

// or the more conventional non inner-class style:

fwd = new FluentWebDriver(webDriver, MyRunListener.codahaleMetricsMonitor);

And in Maven's pom.xml:

<build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <configuration>
          <properties>
            <property>
              <name>listener</name>
              <value>com.example.MyRunListener</value>
            </property>
          </properties>
        </configuration>
      </plugin>
    </plugins>
  </build>

This will spit our stats in the log like so, that require some interpretation:

package.MyClass.aMethod:div(By.className: aClassName)
             count = 2
         mean rate = 0.00 calls/millisecond
     1-minute rate = 0.00 calls/millisecond
     5-minute rate = 0.00 calls/millisecond
    15-minute rate = 0.00 calls/millisecond
               min = 31.95 milliseconds
               max = 36.66 milliseconds
              mean = 34.31 milliseconds
            stddev = 3.33 milliseconds
            median = 34.31 milliseconds
              75% <= 36.66 milliseconds
              95% <= 36.66 milliseconds
              98% <= 36.66 milliseconds
              99% <= 36.66 milliseconds
            99.9% <= 36.66 milliseconds

There's a fuller example of stats in the 'Fluent Selenium Examples' project

Coda Hale's Metrics library has other reporters you could attach.

Java 8 (and onwards) - more fluency

Since both FluentMatcher and FluentWebElementVistor are single function interfaces, they can be used with Java 8 lambda functions.

Example:

listofMatching elements = fwd.inputs(className("bar").filter(
    (FluentWebElement el, int ix) -> true
);
// Replace "true" wit a statement that uses "el" and "ix"

And similarly for FluentWebElementVisitor.

Including it in your project

Maven

<dependency>
   <groupId>org.seleniumhq.selenium.fluent</groupId>
   <artifactId>fluent-selenium</artifactId>
   <version>1.17</version>
   <scope>test</scope>
</dependency>

<!-- you need to choose a hamcrest version that works for you too -->
<dependency>
   <groupId>org.hamcrest</groupId>
   <artifactId>hamcrest-all</artifactId>
   <version>1.3</version>
   <scope>test</scope>
</dependency>

<!-- If you're needing Coda Hale's Metrics integration (optional) -->
<dependency>
   <groupId>com.codahale.metrics</groupId>
   <artifactId>metrics-core</artifactId>
   <version>3.0.0</version>
</dependency>

Bear in mind that the FluentSelenium maven module has a transitive dependency on Selenium 4.x. You may want to override the version for your project. You'll need an exclusion for FluentSelenium, and an explicit dependency for Selenium 4.x.x 9 (see optional below):

<dependency>
  <groupId>org.seleniumhq.selenium.fluent</groupId>
  <artifactId>fluent-selenium</artifactId>
  <version>1.3.x</version>
  <scope>test</scope>
  <!-- optional -->
  <exclusions>
    <exclusion>
      <groupId>org.seleniumhq.selenium</groupId>
      <artifactId>selenium-java</artifactId>
    </exclusion>
  </exclusions>
</dependency>
<!-- optional -->
<dependency>
  <groupId>org.seleniumhq.selenium</groupId>
  <artifactId>selenium-java</artifactId>
  <version>4.x.x</version>
  <scope>test</scope>
</dependency>

Non-Maven

For non-Maven build systems, download it yourself.

Here's what else you might need in your classpath, depending on your needs:

$ mvn dependency:tree
[INFO] Scanning for projects...
[INFO] 
[INFO] -----------< org.seleniumhq.selenium.fluent:fluent-selenium >-----------
[INFO] Building fluent-selenium 1.3
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] 
[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ fluent-selenium ---
[INFO] org.seleniumhq.selenium.fluent:fluent-selenium:jar:1.3
[INFO] +- junit:junit:jar:4.13.1:test
[INFO] +- org.hamcrest:hamcrest-all:jar:1.3:compile
[INFO] +- org.mockito:mockito-core:jar:1.10.19:test
[INFO] |  +- org.hamcrest:hamcrest-core:jar:1.1:test
[INFO] |  \- org.objenesis:objenesis:jar:2.1:test
[INFO] +- org.seleniumhq.selenium:selenium-java:jar:4.4.0:compile
[INFO] |  +- org.seleniumhq.selenium:selenium-api:jar:4.4.0:compile
[INFO] |  +- org.seleniumhq.selenium:selenium-chrome-driver:jar:4.4.0:compile
[INFO] |  |  +- com.google.auto.service:auto-service-annotations:jar:1.0.1:compile
[INFO] |  |  +- com.google.auto.service:auto-service:jar:1.0.1:compile
[INFO] |  |  |  \- com.google.auto:auto-common:jar:1.2:compile
[INFO] |  |  +- com.google.guava:guava:jar:31.1-jre:compile
[INFO] |  |  |  +- com.google.guava:failureaccess:jar:1.0.1:compile
[INFO] |  |  |  +- com.google.guava:listenablefuture:jar:9999.0-empty-to-avoid-conflict-with-guava:compile
[INFO] |  |  |  +- com.google.code.findbugs:jsr305:jar:3.0.2:compile
[INFO] |  |  |  +- org.checkerframework:checker-qual:jar:3.12.0:compile
[INFO] |  |  |  +- com.google.errorprone:error_prone_annotations:jar:2.11.0:compile
[INFO] |  |  |  \- com.google.j2objc:j2objc-annotations:jar:1.3:compile
[INFO] |  |  +- org.seleniumhq.selenium:selenium-chromium-driver:jar:4.4.0:compile
[INFO] |  |  \- org.seleniumhq.selenium:selenium-json:jar:4.4.0:compile
[INFO] |  +- org.seleniumhq.selenium:selenium-devtools-v102:jar:4.4.0:compile
[INFO] |  +- org.seleniumhq.selenium:selenium-devtools-v103:jar:4.4.0:compile
[INFO] |  +- org.seleniumhq.selenium:selenium-devtools-v104:jar:4.4.0:compile
[INFO] |  +- org.seleniumhq.selenium:selenium-devtools-v85:jar:4.4.0:compile
[INFO] |  +- org.seleniumhq.selenium:selenium-edge-driver:jar:4.4.0:compile
[INFO] |  +- org.seleniumhq.selenium:selenium-firefox-driver:jar:4.4.0:compile
[INFO] |  +- org.seleniumhq.selenium:selenium-ie-driver:jar:4.4.0:compile
[INFO] |  +- org.seleniumhq.selenium:selenium-opera-driver:jar:4.4.0:compile
[INFO] |  +- org.seleniumhq.selenium:selenium-remote-driver:jar:4.4.0:compile
[INFO] |  |  +- com.beust:jcommander:jar:1.82:compile
[INFO] |  |  +- io.netty:netty-buffer:jar:4.1.78.Final:compile
[INFO] |  |  +- io.netty:netty-codec-http:jar:4.1.78.Final:compile
[INFO] |  |  |  +- io.netty:netty-codec:jar:4.1.78.Final:compile
[INFO] |  |  |  \- io.netty:netty-handler:jar:4.1.78.Final:compile
[INFO] |  |  +- io.netty:netty-common:jar:4.1.78.Final:compile
[INFO] |  |  +- io.netty:netty-transport-classes-epoll:jar:4.1.78.Final:compile
[INFO] |  |  +- io.netty:netty-transport-classes-kqueue:jar:4.1.78.Final:compile
[INFO] |  |  +- io.netty:netty-transport-native-epoll:jar:4.1.78.Final:compile
[INFO] |  |  +- io.netty:netty-transport-native-kqueue:jar:4.1.78.Final:compile
[INFO] |  |  +- io.netty:netty-transport-native-unix-common:jar:4.1.78.Final:compile
[INFO] |  |  +- io.netty:netty-transport:jar:4.1.78.Final:compile
[INFO] |  |  |  \- io.netty:netty-resolver:jar:4.1.78.Final:compile
[INFO] |  |  +- io.opentelemetry:opentelemetry-api:jar:1.16.0:compile
[INFO] |  |  +- io.opentelemetry:opentelemetry-context:jar:1.16.0:compile
[INFO] |  |  +- io.opentelemetry:opentelemetry-exporter-logging:jar:1.16.0:compile
[INFO] |  |  |  +- io.opentelemetry:opentelemetry-sdk-metrics:jar:1.16.0:compile
[INFO] |  |  |  \- io.opentelemetry:opentelemetry-sdk-logs:jar:1.16.0-alpha:compile
[INFO] |  |  +- io.opentelemetry:opentelemetry-sdk-common:jar:1.16.0:compile
[INFO] |  |  +- io.opentelemetry:opentelemetry-sdk-extension-autoconfigure-spi:jar:1.16.0:compile
[INFO] |  |  +- io.opentelemetry:opentelemetry-sdk-extension-autoconfigure:jar:1.16.0-alpha:compile
[INFO] |  |  +- io.opentelemetry:opentelemetry-sdk-trace:jar:1.16.0:compile
[INFO] |  |  +- io.opentelemetry:opentelemetry-sdk:jar:1.16.0:compile
[INFO] |  |  +- io.opentelemetry:opentelemetry-semconv:jar:1.16.0-alpha:compile
[INFO] |  |  +- io.ous:jtoml:jar:2.0.0:compile
[INFO] |  |  +- net.bytebuddy:byte-buddy:jar:1.12.10:compile
[INFO] |  |  +- org.apache.commons:commons-exec:jar:1.3:compile
[INFO] |  |  +- org.asynchttpclient:async-http-client:jar:2.12.3:compile
[INFO] |  |  |  +- org.asynchttpclient:async-http-client-netty-utils:jar:2.12.3:compile
[INFO] |  |  |  +- io.netty:netty-codec-socks:jar:4.1.60.Final:compile
[INFO] |  |  |  +- io.netty:netty-handler-proxy:jar:4.1.60.Final:compile
[INFO] |  |  |  +- io.netty:netty-transport-native-epoll:jar:linux-x86_64:4.1.60.Final:compile
[INFO] |  |  |  +- io.netty:netty-transport-native-kqueue:jar:osx-x86_64:4.1.60.Final:compile
[INFO] |  |  |  +- org.reactivestreams:reactive-streams:jar:1.0.3:compile
[INFO] |  |  |  +- com.typesafe.netty:netty-reactive-streams:jar:2.0.4:compile
[INFO] |  |  |  \- com.sun.activation:jakarta.activation:jar:1.2.2:compile
[INFO] |  |  \- org.seleniumhq.selenium:selenium-http:jar:4.4.0:compile
[INFO] |  |     \- dev.failsafe:failsafe:jar:3.2.4:compile
[INFO] |  +- org.seleniumhq.selenium:selenium-safari-driver:jar:4.4.0:compile
[INFO] |  \- org.seleniumhq.selenium:selenium-support:jar:4.4.0:compile
[INFO] \- io.dropwizard.metrics:metrics-core:jar:3.2.6:compile
[INFO]    \- org.slf4j:slf4j-api:jar:1.7.22:compile

Changes

1.3 (Aug ?, 2022)

• upgrade to Selenium 4.4.0
• Minimum Java Version is now 8

1.23 (Nov 23, 2020)

• fluentize() added

Compared to last release on GitHub

1.22 (Nov 22, 2020)

• Add upperCase() and lowerCase() text changer

Compared to last release on GitHub

1.21 (Feb 22, 2020)

• Upgrade Selenium to 3.141.59 from 3.8.x

1.20 (Apr 28, 2018)

• Coda Hale's Metrics library updated to 3.2.6 (maven group:artifact change with that)
• This release is tested as compatible with Selenium 3.12 and 3.13

1.19 (Dec 31, 2017)

• Selenium upgrade to v3.8.0
• TestableString opened up a little
• New TestableString.multiCREliminator() added to change \n\n sequences in getText() to \n
• Transitive use of FileUtils from Apache-Commons eliminated.
• Java 7 is a requirement now (facilitated the above)

1.18 (Jun 18, 2017)

• Selenium upgrade to v3.4.0
• Fluent menthod .element(name) exapanded a little

1.17 (Dec 20, 2016)

• Selenium upgrade to v3.0.1
• Support for 'body' element
• New TestableString method shouldMatch(hamcrestMatcher) in addition to the same method that took a regex previously.
• FluentWebElement getText() can take a varargs of 'TextChanger' now
• FluentWebElements getText() can too, but also a means to control the between elements chars (CR by default)

1.16.1 (May 22, 2016)

• Selenium upgrade to v2.53.0 - incl. the new getRect() from WebElement
• Support for h5 and h6

1.16 (Nov 29, 2015)

• map function and visitor added

1.15 (Nov 21, 2015)

• Selenium upgrade to v2.48.2
• Support for unordered lists (ul elements)
• FluentWebDriver.element(..) method for finding generic elements (or ones outside the HTML spec)

More Reading

Refer Paul Hammant's Fluent Selenium Examples Blog Entry about this, or the project that showcases Fluent Selenium - Fluent Selenium Examples.