Svcc Groovy Testing

Boosting your testing productivity with G r oo v y

Andres Almiray

Have fun while programming tests

G o a l

Agenda

What is G r oo v y

G r oo v y + Testing Frameworks

Mocking with G r oo v y

Testing Databases

Building Test Data

Functional UI Testing

Resources

W hat is G r oo v y ?

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% G r oo v y

class HelloWorld {

String name

def greet() { "Hello $name" }

}

def helloWorld = new HelloWorld(name : " Groovy" )‏

println helloWorld.greet()‏

1 st Mantra

Java is G r oo v y , G r oo v y is Java

Every single Java class is a G r oo v y class, the inverse is also true. This means your Java can call my G r oo v y in vice versa, without any clutter nor artificial bridge.

G r oo v y has the same memory and security models as Java.

Almost 98% Java code is G r oo v y code, meaning you can in most cases rename *.java to *.groovy and it will work.

Common Gotchas

Java Array initializers are not supported, but lists can be coerced into arrays.

Inner class definitions are not supported (yet!!).

2 nd Mantra

Groovy is Java and G r oo v y is not Java

Flat learning curve for Java developers, start with straight Java syntax then move on to a groovier syntax as you feel comfortable.

G r oo v y delivers closures, meta-programming, new operators, operator overloading, enhanced POJOs, properties, native syntax for Maps and Lists, regular expressions, enhanced class casting, optional typing, and more!

G r oo v y + Testing Frameworks

Any G r oo v y script may become a testcase

assert keyword enabled by default

G r oo v y provides a GroovyTestCase base class

Easier to test exception throwing code

Junit 4.x and TestNG ready, G r oo v y supports 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()‏

}

}

}

But how do I run G r oo v y tests?

Pick your favourite IDE!

IDEA

Eclipse

NetBeans

Command line tools

Ant

Gant

Maven

Good ol’ G r oo v y shell/console

Mocking with G r oo v y

Known mocking libraries

EasyMock – record/replay

JMock – write expectations as you go

Use dynamic proxies as stubs

built-in proxy support

extended proxies with Proxy-o-Matic

Use StubFor/MockFor

inspired by EasyMock

no external libraries required (other than G r oo v y )‏

Dynamic Proxies

This feature allows you to define a java.lang.reflect.Proxy using either a Closure or Map + G r oo v y casting

You can proxy interfaces, abstract and concrete classes this way

The syntax for proxying a Map looks like JSON

No need to supply implementations for all methods, just proxy the ones you need

CAVEAT: map proxying does not allow overloaded methods

Dynamic Proxies with Proxy-o-Matic

Proxy-o-Matic extends G r oo v y 's built-in proxy support by allowing the following

define overloaded methods

call its own methods from within

proxy more than 1 interface at a time

proxy from Expandos as well

CAVEAT: it can only proxy interfaces for the time being

http://groovy.codehaus.org/Proxy-o-Matic

Dynamic Proxies

Demo

StubFor/MockFor

caller – collaborator

mocks/stubs define expectations on collaborators

mocks are strict, expectation must be fulfilled both in order of invocation and cardinality.

stubs are loose, expectations must fulfil cardinality but may be invoked in any order.

CAVEAT: can be used to mock both G r oo v y and Java collaborators, caller must be G r oo v y though.

G r oo v y Mocks

Demo

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", "" )‏

// insert table schema

def dataset = """

<dataset>

<company name="Acme"/>

<employee name="Duke" company_id="1">

</dataset>

"""

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("org.hsqldb.jdbcDriver",

"jdbc:hsqldb:sample", "sa", "" )‏

// insert table schema

def dataset = new MarkupBuilder().dataset {

company( name: Acme )‏

employee( name: "Duke", company_id: 1 )‏

}

db.dataset = new FlatXmlDataSet( new StringReader(dataset) )‏

db.onSetUp()‏

}

@AfterClass void exit() { db.onTearDown() }

}

Building Test Data

Builders are a great option for creating hierarchical data

MarkupBuilder -> HTML/XML

ObjectGraphBuilder -> bean graph

ObjectGraphBuilder

Demo

Functional UI 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

G r oo v y to the rescue!

[Any of the following] + G r oo v y = success!

Web testing -> Canoo WebTest

Swing testing -> FEST

BDD testing -> Easyb

FEST + Easyb

Demo

For More Information

h tt p : // groovy.codehaus.org

h tt p : // junit.org

h tt p : // testng.org

h tt p : // dbunit.org

h tt p : // easytesting.org (FEST)‏

h tt p : // easyb.org

h tt p : // groovy.codehaus.org / Proxy-o-Matic

h tt p : // groovy.codehaus.org / ObjectGraphBuilder

h tt p : // jroller.com / aalmiray

h tt p : // twitter.com / aalmiray

Q & A

Thank You!

Svcc Groovy Testing

0 comments

Notes on slide 1

Favorites, Groups & Events