Spock - The Logical Enterprise Testing Tool

Transcription

1 NFJS Software Symposium Series 2013 Spock - The Logical Enterprise Testing Tool Ken Sipe

2 About Speaker Developer: Embedded, C++, Java, Groovy, Grails, C#, Objective C Speaker: JavaOne 2009 Rock Star, NFJS, JAX Microsoft MCP Sun Certified Java 2 Architect Master of Scrums Agile Coach Instructor: VisiBroker CORBA Rational Rose, OOAD

3 Agenda n Testing n Introduction to Spock n Mocking

4 Spock Intro 4

5 Spock is... n testing framework... n based on Groovy n fully compatible with JUnit n result of learnings from RSpec, BDD, JUnit 5

6 Spock Can... n Reduces lines of code n Make tests more readable n Be extended 6

7 JUnit 7

8 Taxonomy of JUnit

9 JUnit Pain Points? 9

10 Unit testing needs n Concise, Clear and Readable n Promote user thinking context stimulus expectations n Productivity 10

11 Groovy 11

12 Taxonomy of GroovyTestCase

13 Groovy and Testing

14 Groovy Power Assert Condition not satisfied: interest == calc.calculate(amt, year) com.math.simpleinterestcalculator@606e1dec false

15 Groovy Improvements n Concise, Clear and Readable n Promote user thinking context stimulus expectations n Productivity 15

16 Spock 16

17 Spock n Programmers Environment Groovy n Promotes Clarity structural blocks removes noise 17

18 Why use Spock? n Expressive testing language n Easy to learn n Usable from unit to end-to-end n Leverages Groovy n Runs with JUnit Runner IDE CI 18

19 Taxonomy of a Spec 19

20 First Spec

21 Terms n Specification compare to TestCase or GroovyTestCase Instructs JUnit to run with Sputnik (JUnit runner) n Fields initialized for each test think setup not shared between feature methods 21

22 More Fields n Shared Setup once think setupspec() n statics only use for constants 22

23 Fixture Methods n before / after a feature n before / after a spec n optional 23

24 Feature Methods n heart of spec n four phases setup the features fixture provide stimulus to system describes the response clean up 24

25 Blocks given: when: then: expect: where: and: setup: preconditions, data fixtures actions that trigger some outcome makes assertions about outcome short alt to when & then applies varied inputs sub-divides other blocks alias for given cleanup: post-conditions, housekeeping 25

26 Common Blocks n When / Then / Where n Given / When / Then 26

27 Blocks n setup must be first must be the only no special semantics label is optional label given: is an alias 27

28 When / Then Blocks n used together possible to have many per feature n then restrictions conditions exception conditions automatic asserts interactions variable defs 28

29 Conditions n checking for exceptions 29

30 Throwing an Exception NOT! 30

31 Mocks and Expectations 31

32 Cleanup on Feature X n cleanup block only followed by a where block no repeats 32

33 Where Blocks last in a method no repeats used for data-driven features 33

34 Helper Methods either return a boolean n or assert 34

35 Specification Functions and Spock.lang.* 35

36 n old() n thrown() / notthrown n with {} 36

37 @Subject 37

38 Spock.lang.* 38

39 39

40 Built-in dispose 40

41 Built-in @Timeout(value=10, unit=timeunit.milliseconds) 41

42 Built-in Extensions: 42

43 Hamcrest 43

44 JUnit Rules 44

45 SpockConfig 45

46 References n Getting Spock n Source from Presentation 46

47 Summary n Closing and Q&A Please fill out the session evaluation Ken Sipe n ken.sipe@gmail.com n kensipe.blogspot.com n