Over a million developers have joined DZone.

A Different Style of Fluent Selenium Tests

· DevOps Zone

The DevOps zone is brought to you in partnership with Sonatype Nexus. The Nexus suite helps scale your DevOps delivery with continuous component intelligence integrated into development tools, including Eclipse, IntelliJ, Jenkins, Bamboo, SonarQube and more. Schedule a demo today

Kevin Dishman is ThoughWorks’ QA lead for a client I “rolled off” a few days ago. He prefers a different style of Java and Page-Objects for Selenium2 / WebDriver codebases. Thus, he switched the foundational tests I’d written before his arrival to be more like the style he prefers. I’ve paralleled that change in the public Fluent-Selenium examples project: github.com/paul-hammant/fluent-selenium-examples.

A Second Branch

The second branch, for better or for worse, is called “more_typesafe”.

GitHub’s visualization of the different branches at the time of the original commit (August 8th): github.com/paul-hammant/fluent-selenium-examples/compare/d7e55dd1fd41f86…151e589cd86b378e3a6c33

The gist of that is:

There are pros and cons to both, I think.

The DevOps zone is brought to you in partnership with Sonatype Nexus. Use the Nexus Suite to automate your software supply chain and ensure you're using the highest quality open source components at every step of the development lifecycle. Get Nexus today

Topics:

Published at DZone with permission of Paul Hammant, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}