Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

A Different Style of Fluent Selenium Tests

DZone's Guide to

A Different Style of Fluent Selenium Tests

· DevOps Zone
Free Resource

The Nexus Suite is uniquely architected for a DevOps native world and creates value early in the development pipeline, provides precise contextual controls at every phase, and accelerates DevOps innovation with automation you can trust. Read how in this ebook.

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.  See how the Nexus platform infuses precise open source component intelligence into the DevOps pipeline early, everywhere, and at scale. Read how in this ebook

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 DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

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

X

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

{{ parent.tldr }}

{{ parent.urlSource.name }}