I have a question: How do you work with selenium-ruby?
I was planning on working towards what Dave Haeffner has in ElementalSelenium.com creating a library of:
It looks like Gauge strongly advocates against page objects calling them an Anti-Pattern. Er... Um... burying a page's locators in code, as they do in the blog makes me worried. I am looking for other solutions.
I was planning on working towards what Dave Haeffner has in ElementalSelenium.com creating a library of:
- Using Base Page Objects to wrap Selenium Ruby calls with proper waits.
- Using Page Objects, so that when locators inevitably change, I know where exactly to fix them.
- Making the tests data-driven
- Adding Rescue exceptions to avoid weeding through Stack traces.
- Maybe JQuery Growl for better logging, and Wrapped Selenium Tests
It looks like Gauge strongly advocates against page objects calling them an Anti-Pattern. Er... Um... burying a page's locators in code, as they do in the blog makes me worried. I am looking for other solutions.