I have written acceptance test suites using Selenium WebDriver in Java, along with JUnit tests for internally used logic, so I am familiar with the Webdriver API and have been able to successfully leverage existing page object code for multiple tests. I have also written sequence code designed to maximize code reuse and test readability.
The test suite I wrote (as part of a larger team effort) included login/registration testing, as well as testing features that submit/update data, where much of the functionality was accessed via an iframe to a second domain (which can present challenges when using WebDriver).
In the spirit of full disclosure, I have no experience with Cucumber, but I believe that a JUnit Test suite can be used to ensure all tests are executed while I learn the syntax for it and document it.
My process will be as follows:
1. First walkthrough the site (as much as possible) to get a feel for the test requirements,
2. Analyze where I believe webdriver automation may prove challenging (radio buttons, dynamically generated content, etc).
3. Begin writing tests of the easier portions while analyzing the more difficult pieces.
4. Check in source code to a repository of the employer's choice when code is functional, or at a specified interval.
5. My Webdriver tests will be organized into JUnit test classes unless otherwise specified by the employer.
Please contact me if there are any questions.
Thanks