Groovy is no good for functional test automation. I have seen at least 3 projects using Groovy failed badly (100% failure). Reasons: 1. It is not an official Selenium language. 2. Complex, will introduce more layers and frameworks. 3. One architect who designed the failed ‘groovy based framework’, explained: “he thought Groovy is like Ruby”, My answer: “Why not just learn Ruby?”. The problem is that Java programmers who lack learning altitude and open mindset, will certainly fail UI test automation (which is regarded as much harder than development, checkout out the references in my other articles) He agreed, after seeing manual testers learned (and loved), including himself, after my one-day training. Just One Day!