Daniel Gregoire edited this page Aug 6, 2015 · 11 revisions

There would be nothing wrong with using the Java API directly from Clojure in Selenium-WebDriver tests. From that perspective, clj-webdriver just makes it easier to treat Selenium-WebDriver methods as functions, avoiding having to wrap interop calls with anonymous functions throughout your code.

That's not really a stellar reason to create--or maintain--a library.

Instead of claiming a path to a final 1.0 for this library, I'd like to leave it open-ended. First, I'm going to triage the existing code base and clean up what survives. Then I'm going to experiment with new ways to author Selenium-WebDriver tests, with Clojure as the medium.

Along the way I hope I stumble across things that leverage Clojure's strengths and idioms, but more importantly I hope in the end the library has something to offer beyond superficial convenience.