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 need for DevOps innovation has never been greater. Get the results from over 100 business value assessments in this whitepaper, Digital Darwinism: Driving Digital Transformation, to see the positive impact of DevOps first hand.

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.

Interested in Kubernetes but unsure where to start? Check out this whitepaper, A Roundup of Managed Kubernetes Platforms from Codeship by Cloudbees, for an overview and comparison of Kubernetes platforms. 

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}