Boosting Your Testing Productivity with Groovy

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

1 comments

Comments 1 - 1 of 1 previous next Post a comment

Post a comment
Embed Video
Edit your comment Cancel

2 Favorites

Boosting Your Testing Productivity with Groovy - Presentation Transcript

  1. Boosting your testing productivity with Groovy James Williams, Spatial Networks Andres Almiray, Oracle BOF-5101
      • Have fun while programming tests
  2. Agenda
    • What is Groovy
    • Groovy + Testing Frameworks
    • Mocking with Groovy
    • Grails Testing
    • Testing Databases
    • Functional Testing
    • Resources
  3. 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
  4. 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
  5. 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() )
    • }
    • }
  6. 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() )
    • }
    • }
  7. Equivalent HelloWorld 100% Groovy
    • class HelloWorld {
    • String name
    • def greet() { "Hello $name" }
    • }
    • def helloWorld = new HelloWorld(name : " Groovy" )
    • println helloWorld.greet()
  8. 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
  9. 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
    • }
    • }
    • }
  10. Testing exceptions in Groovy
    • class GroovyExceptionTestCase extends GroovyTestCase {
    • void testExceptionThrowingCode() {
    • shouldFail( UnsupportedOperationException ){
    • new MyService().doSomething()
    • }
    • }
    • }
  11. 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
  12. 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
  13. Groovy Mocks
  14. Grails testing
    • Fairly similar to testing in core Groovy
    • Plugins a plenty
      • easyb
      • Canoo WebTest
      • Selenium
      • DBUnit
      • jsUnit
      • Cobertura
      • JUnit is built in
  15. 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)
  16. Grails Taglibs
  17. 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
  18. 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() }
    • }
  19. 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() }
    • }
  20. 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
  21. Groovy to the rescue!
    • [Any of the following] + Groovy = success!
    • Web testing -> Canoo WebTest
    • Swing testing -> FEST
    • BDD testing -> Easyb
  22. FEST + Easyb
  23. 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
  24. James Williams, Spatial Networks Andres Almiray, Oracle BOF-5101

+ James WilliamsJames Williams, 10 months ago

custom

590 views, 2 favs, 0 embeds more stats

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 590
    • 590 on SlideShare
    • 0 from embeds
  • Comments 1
  • Favorites 2
  • Downloads 24
Most viewed embeds

more

All embeds

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories