Did you ever want to use builders in your grails taglib and wondered why the approach mentioned in the grails documentation doesn’t work at all? Here is what I found out after a lot of trial and error and digging in the MarkupBuilder, BuilderSupport and GroovyPagTagBody sources. Let’s stick with the example from the documentation and correct it until it works (the impatient can scroll down):
-
def dialog =
{ attrs, body ->
-
def markup =
new groovy.
xml.
MarkupBuilder(out
)
-
markup {
-
div(‘class’: ‘dialog’) {
-
body()
-
} } }
>> more…
To achieve full test coverage for our new product sixbee, we chose to try out Selenium. It works perfectly fine for simple stuff like clicking on static links with static texts or IDs:
-
selenium.clickAndWait("link=Click") // click on a element labeled "Click"
-
selenium.clickAndWait("btn") // click on element with id "btn"
When it comes to testing components using Ajax, it’s getting trickier, as not all generated elements have an ID to reference it. Fortunately, Selenium offers some more possibilities for locating elements, such as XPath or CSS-selectors: >> more…
