Groovy, Grails, & Gr8Ladies Women Techmakers: Minneapolis

Women Techmakers: Minneapolis Minneapolis, MN March 22, 2014

 Prerequisites  Java jdk  try ‘java –version’ to
see if it’s already installed  http://www.grails.org/Installation  To Install Groovy and Grails:  Gvmtool.net  curl –s get.gvmtool.net | bash  gvm install groovy  gvm install grails  gvm use grails 2.3.4

 An organization for the support of women in the
Gr8 stack community  Goals:  Education  Networking  Professional Development  Contact Us  @Gr8Ladies on twitter  Gr8Ladies.org  LinkedIn, Facebook search Gr8Ladies  Contribute to our website via GitHub

 Groovy – the language  Grails – MVC framework
 Gradle –build automation tool  Used to build Android Apps  Griffon – desktop app framework  Spock – testing framework  Many other minor frameworks and development tools

Image via: http://blogs.vitoria-gasteiz.org/ti/2010/05/31/full-stack/

 Dynamic compiled language  Flexible  optional typing 
default scope  optional getters/setters  Rapid Development  Integrates with existing JAVA libraries and infrastructure  #groovylang

 In Java,  In Groovy,

 Elvis Operator ?:  In PHP:  In Groovy:

 Ranges  A collection of numbers defined by boundaries
 Spread dot  Applies a function to every element of a collection and returns the result

 Null safe  user?.chapter?.name?.toUpperCase()  will return null if
user or chapter is null and will not return an error

 Groovy Truth  Null, empty string, empty set, and
0 are all false!

Image via: http://blogs.vitoria-gasteiz.org/ti/2010/05/31/full-stack/

 MVC framework  similar to Symphony in PHP, Django
in Python, or Ruby on Rails  Convention over configuration  #grailsfw

image from: http://www.mathiasbosman.be/wp- content/uploads/2014/02/mvc_role_diagram.png

 Domain Classes  Grails Object Relationship Mapping(GORM)  Uses
Hibernate  Class names map to tables  Field names map to columns  Dynamic finders  User.findAllByGenderAnd ChapterIsNotNull(‘F’)  Events  beforeInsert, afterUpdate, beforeDelete  Alternatives  Mongo and Redis

 Mapped to urls by name  /user/list UserController.list() 
Url Parameters map to controller  /user/show/id UserController.sho w(id)

 GSP (Groovy Server Page)  Directory structure by convention
 UserController.list() renders /views/user/list.gsp  Special tags for forms, links, looping and other tasks  Reference model data by ${model.attribute}

 Lots of Options for writing tests  Spock (default)
 JUnit  Geb

• www.gebish.org • http://docs.spockframework.org/en/spock-0.7-groovy- 2.0/ • For Grails, in BuildConfig.groovy:
dependencies { test "org.seleniumhq.selenium:selenium-support:2.40.0" test "org.seleniumhq.selenium:selenium-firefox-driver:2.40.0" test "org.gebish:geb-spock:0.9.2” } plugins { test ":geb:0.9.2" compile ":remote-control:1.4“ // For accessing the context of the // grails app from tests // Spock is already included in Grails 2.3.6 }

package com.allison.pages import geb.Page class EmployeeListPage extends Page { //
the link that is navigated to // on the 'to' call static url = "employee/list" // the closure that is verified on // the 'at' call static at = { pageTitle.text() == 'Employee List Page' } // The navigator objects static content = { pageTitle(wait: true) { $('h2.title') } employeeLink(wait: true, to: EmployeeShowPage) { id -> $('a.employeeLink', 'id': "${id}") } } // It is good practice to wrap all the // navigator objects in methods boolean employeeLinkIsPresent(Long id) { employeeLink(id).isDisplayed() } EmployeeShowPage clickEmployeeLink(Long id) { employeeLink(id).click() return browser.page } } <html> <head> <title>Employee</title> </head> <body> <h2 class="title">Employee List Page</h2> <ul> <li> <a href="/gebDemo/employee/show/1" id="1” class="employeeLink"> Alice LastName </a> </li> <li> <a href="/gebDemo/employee/show/2" id="2” class="employeeLink"> Bob LastName2 </a> </li> <li> <a href="/gebDemo/employee/show/3" id="3” class="employeeLink"> Charles LastName3 </a> </li> </ul> </body> </html>

package com.allison.functional import com.allison.pages.EmployeeListPage import com.allison.remote.EmployeeRemoteControl import geb.spock.GebReportingSpec class firstSpec
extends GebReportingSpec { EmployeeRemoteControl remote = new EmployeeRemoteControl() Long employeeId_1 Long employeeId_2 Long employeeId_3 def setup() { EmployeeRemoteControl remote = new EmployeeRemoteControl() employeeId_1 = remote.createEmployee('Alice', 'LastName') employeeId_2 = remote.createEmployee('Bob', 'LastName2') employeeId_3 = remote.createEmployee('Charles', 'LastName3') } CONTINUED  def 'A descriptive name for the feature'() { given: 'Setup stuff' // Can be blank when: 'The employee list page is navigated to' EmployeeListPage employeeListPage = to EmployeeListPage then: 'The employee list page header is displayed' assert at(EmployeeListPage) // All statements in a // then-block are implicitly // asserted and: 'The employee is listed' assert employeeListPage.employeeLinkIsPresent( employeeId_1) when: 'The employee is clicked' employeeListPage.clickEmployeeLink(employeeId_1) then: 'At the show employee page' assert at(EmployeeShowPage) } def cleanup() { remote.deleteEmployee(employeeId_1) remote.deleteEmployee(employeeId_2) remote.deleteEmployee(employeeId_3) } }

 GVM!  Groovy enVironment Manager  curl –s get.gvmtool.net
| bash  gvm install groovy  gvm install grails  Use grails 2.3.4  Choose an IDE  IntelliJ  Eclipse  Netbeans

 grails create-app appName  auto generates app structure 
grails create-domain-class User  Creates domain class and test file  grails generate-all appName.User  Auto generates views and controllers based on the properties of the domain class

 Grails war  Defaults to target/appName-0.1.war  Deploy to
JVM  Example via Amazon ElasticBeanstalk

 Making Java Groovy – Ken Kousen  Email [email protected]
for coupon code  Programming Grails – Bert Beckwith (O’reilly animal book)  Groovy In Action - Dierk Koenig with Andrew Glover, Paul King, Guillaume Laforge and Jon Skeet  Many Tutorials available on grails.org

 Come to Groovy Users of Minnesota(GUM) every second Tuesday
of the month at Smart Things  Join Gr8Ladies for hack sessions and contribute to the gr8ladies website on github  Gr8Ladies.org or @Gr8Ladies on twitter

Groovy, Grails, & Gr8Ladies Women Techmakers: M...

Groovy, Grails, & Gr8Ladies Women Techmakers: Minneapolis

jlstrater

More Decks by jlstrater

Other Decks in Technology

Featured

Transcript

Women Techmakers: Minneapolis Minneapolis, MN March 22, 2014

 Prerequisites  Java jdk  try ‘java –version’ to

 An organization for the support of women in the

 Groovy – the language  Grails – MVC framework

Image via: http://blogs.vitoria-gasteiz.org/ti/2010/05/31/full-stack/

 Dynamic compiled language  Flexible  optional typing 

 In Java,  In Groovy,

 Elvis Operator ?:  In PHP:  In Groovy:

 Ranges  A collection of numbers defined by boundaries

 Null safe  user?.chapter?.name?.toUpperCase()  will return null if

 Groovy Truth  Null, empty string, empty set, and

Image via: http://blogs.vitoria-gasteiz.org/ti/2010/05/31/full-stack/

 MVC framework  similar to Symphony in PHP, Django

image from: http://www.mathiasbosman.be/wp- content/uploads/2014/02/mvc_role_diagram.png

 Domain Classes  Grails Object Relationship Mapping(GORM)  Uses

 Mapped to urls by name  /user/list UserController.list() 

 GSP (Groovy Server Page)  Directory structure by convention

 Lots of Options for writing tests  Spock (default)

• www.gebish.org • http://docs.spockframework.org/en/spock-0.7-groovy- 2.0/ • For Grails, in BuildConfig.groovy:

package com.allison.pages import geb.Page class EmployeeListPage extends Page { //

package com.allison.functional import com.allison.pages.EmployeeListPage import com.allison.remote.EmployeeRemoteControl import geb.spock.GebReportingSpec class firstSpec

 GVM!  Groovy enVironment Manager  curl –s get.gvmtool.net

 grails create-app appName  auto generates app structure 

 Grails war  Defaults to target/appName-0.1.war  Deploy to

 Making Java Groovy – Ken Kousen  Email [email protected]

 Come to Groovy Users of Minnesota(GUM) every second Tuesday