Boosting Your Testing Productivity with Groovy
Upcoming SlideShare
Loading in...5
×
 

Boosting Your Testing Productivity with Groovy

on

  • 3,829 views

 

Statistics

Views

Total Views
3,829
Views on SlideShare
3,821
Embed Views
8

Actions

Likes
3
Downloads
55
Comments
1

2 Embeds 8

http://www.slideshare.net 6
https://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • thanks
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Boosting Your Testing Productivity with Groovy Boosting Your Testing Productivity with Groovy Presentation Transcript

    • Boosting your testing productivity with Groovy James Williams, Spatial Networks Andres Almiray, Oracle BOF-5101
        • Have fun while programming tests
    • Agenda
      • What is Groovy
      • Groovy + Testing Frameworks
      • Mocking with Groovy
      • Grails Testing
      • Testing Databases
      • Functional Testing
      • Resources
    • What is Groovy?
      • Groovy is an agile and dynamic language for the Java Virtual Machine
      • Builds upon the strengths of Java but has additional power features inspired by languages like Python, Ruby & Smalltalk
      • Makes modern programming features available to Java developers with almost-zero learning curve
      • Supports Domain Specific Languages and other compact syntax so your code becomes easy to read and maintain
    • What is Groovy?
      • Increases developer productivity by reducing scaffolding code when developing web, GUI, database or console applications
      • Simplifies testing by supporting unit testing and mocking out-of-the-box
      • Seamlessly integrates with all existing Java objects and libraries
      • Compiles straight to Java byte code so you can use it anywhere you can use Java
    • HelloWorld.java
      • public class HelloWorld {
      • String name;
      • public void setName(String name)
      • { this.name = name; }
      • public String getName(){ return name; }
      • public String greet()
      • { return “Hello “ + name; }
      • public static void main(String args[]){
      • HelloWorld helloWorld = new HelloWorld()
      • helloWorld.setName( “Groovy” )
      • System.err.println( helloWorld.greet() )
      • }
      • }
    • HelloWorld.groovy
      • public class HelloWorld {
      • String name;
      • public void setName(String name)
      • { this.name = name; }
      • public String getName(){ return name; }
      • public String greet()
      • { return “Hello “ + name; }
      • public static void main(String args[]){
      • HelloWorld helloWorld = new HelloWorld()
      • helloWorld.setName( “Groovy” )
      • System.err.println( helloWorld.greet() )
      • }
      • }
    • Equivalent HelloWorld 100% Groovy
      • class HelloWorld {
      • String name
      • def greet() { "Hello $name" }
      • }
      • def helloWorld = new HelloWorld(name : " Groovy" )
      • println helloWorld.greet()
    • Groovy + Testing Frameworks
      • Any Groovy script may become a testcase
        • assert keyword enabled by default
      • Groovy provides a GroovyTestCase base class
        • Easier to test exception throwing code
      • Junit 4.x and TestNG ready, Groovy suports JDK5+ features
        • Annotations
        • Static imports
        • Enums
    • Testing exceptions in Java
      • public class JavaExceptionTestCase extends TestCase {
      • public void testExceptionThrowingCode() {
      • try {
      • new MyService().doSomething();
      • fail("MyService.doSomething has been implemented");
      • }catch( UnsupportedOperationException expected ){
      • // everything is ok if we reach this block
      • }
      • }
      • }
    • Testing exceptions in Groovy
      • class GroovyExceptionTestCase extends GroovyTestCase {
      • void testExceptionThrowingCode() {
      • shouldFail( UnsupportedOperationException ){
      • new MyService().doSomething()
      • }
      • }
      • }
    • Alright, but how do I run Groovy tests?
      • Pick your favorite IDE!
        • IDEA
        • Eclipse
        • NetBeans
      • Command line tools
        • Ant
        • Gant
        • Maven
        • Good ol’ Groovy shell/console
    • Mocking with Groovy
      • Known mocking libraries
        • EasyMock – record/replay
        • Jmock – write expectations as you go
      • Use dynamic proxies as stubs
      • Use StubFor/MockFor
        • Groovy mocks rely on MetaClasses to do their magic
        • Caveat: use them only for Groovy classes
    • Groovy Mocks
    • Grails testing
      • Fairly similar to testing in core Groovy
      • Plugins a plenty
        • easyb
        • Canoo WebTest
        • Selenium
        • DBUnit
        • jsUnit
        • Cobertura
        • JUnit is built in
    • Testing Taglibs
      • Can be tested with Junit
      • Need to extend several metaClasses that are not in testing scope
        • out
        • Encoders/Decoders
      • General format:
        • className.tagName( [ attrs as Map], body)
    • Grails Taglibs
    • Testing Databases
      • DbUnit: a Junit extension for testing databases
      • Several options at your disposal
        • Old school – extend DatabaseTestCase
        • Flexible – use an IDataBaseTester implementation
        • Roll your own Database testcase
    • Inline XML dataset
      • import org.dbunit.*
      • import org.junit.*
      • class MyDBTestCase {
      • IDatabaseTester db
      • @BeforeClass void init(){
      • db = new JdbcDatabaseTester("org.hsqldb.jdbcDriver",
      • "jdbc:hsqldb:sample", "sa", "" )
      • def dataset = """
      • <dataset>
      • <company name=&quot;Acme&quot;/>
      • <employee name=&quot;Duke&quot; company_id=&quot;1&quot;>
      • </dataset>
      • &quot;&quot;&quot;
      • db.dataset = new FlatXmlDataSet( new StringReader(dataset) )
      • db.onSetUp()
      • }
      • @AfterClass void exit() { db.onTearDown() }
      • }
    • Compile-checked dataset
      • import org.dbunit.*
      • import org.junit.*
      • Import groovy.xml.MarkupBuilder
      • class MyDBTestCase {
      • IDatabaseTester db
      • @BeforeClass void init(){
      • db = new JdbcDatabaseTester(&quot;org.hsqldb.jdbcDriver&quot;,
      • &quot;jdbc:hsqldb:sample&quot;, &quot;sa&quot;, &quot;&quot; )
      • def dataset = new MarkupBuilder().dataset {
      • company( name: Acme )
      • employee( name: &quot;Duke&quot;, company_id: 1 )
      • }
      • db.dataset = new FlatXmlDataSet( new StringReader(dataset) )
      • db.onSetUp()
      • }
      • @AfterClass void exit() { db.onTearDown() }
      • }
    • Functional Testing
      • These tests usually require more setup
      • Non-developers usually like to drive these tests
      • Developers usually don’t like to code these tests
      • No Functional Testing => unhappy customer => unhappy developer
    • Groovy to the rescue!
      • [Any of the following] + Groovy = success!
      • Web testing -> Canoo WebTest
      • Swing testing -> FEST
      • BDD testing -> Easyb
    • FEST + Easyb
    • For More Information
      • http://groovy.codehaus.org
      • http://grails.org
      • http://junit.org
      • http://testng.org
      • http:// www.dbunit.org
      • http:// webtest.canoo.com
      • http://easyb.org
      • http:// easytesting.org
      • http :// jameswilliams.be
      • http:// jroller.com/aalmiray
    • James Williams, Spatial Networks Andres Almiray, Oracle BOF-5101