This document introduces the Spock testing framework as an alternative to JUnit for Java applications. Some key points: - Spock uses Groovy's more succinct syntax to write tests, making them easier to write and read compared to JUnit. It supports features like state-driven testing, data-driven testing, mocking, and stubbing out of the box. - Spock tests are fully compatible with JUnit so they can be run with existing tools. The framework also has many extensions for additional functionality and integrations. - Benefits of Spock include easier testing, better test structure, easier understanding of failures, and support for non-technical stakeholders. While there is a learning curve, its

1. Spock Testing
Framework
Amir Langer
langera@gmail.com
1

2. What did a test ever do for
us?
2

3. A Test is code that uses your
production code
3

4. A Test is code that uses your
production code
• Correctness Find problems, Facilitates change
4

5. A Test is code that uses your
production code
• Correctness Find problems, Facilitates change
• Design
5

6. A Test is code that uses your
production code
• Correctness Find problems, Facilitates change
• Design
• Documentation
6

7. It does not matter how intelligent you
are, if you guess and that guess
cannot be backed up by experimental
evidence, then it is still a guess.
Richard Feynman (1964)
Correctness
7

8. A Software system can be best designed if
the testing is interlaced with the design
instead of being used after the design
Alan J. Perlis (1968)
Design
8

9. Documentation
9

10. If JUnit was good enough for my
grandparents then why not for me?
• Written in Java: Statically typed, Rigid syntax, Hard
for DSLs
• Limited in its features, Requires “add-ons”:
Hamcrest, JAssert, JMock, Mockito, EasyMock,
PowerMock, JMockit, Cucumber, JBehave…
10

11. What is Spock?
• A Developer testing framework for the JVM (since 2008)
• Based on Groovy
• Succinct syntax and DSL built for tests
• Mocking/stubbing is already included
• BDD friendly
• Fully compatible with JUnit
11

12. Who uses Spock?
12

13. JUnit V Spock

14. Simple Assertion
Does (2+2)*3+5 = 16?
14

15. Assertion Failed
15

16. Assertion Failed
16

17. State Driven Tests
17

18. State Driven Tests
18

19. State Driven Tests
19

20. State Driven Tests
20

21. State Driven Tests
21

22. State Driven Tests
22

23. State Driven Tests
23

24. State Driven Tests
24

25. State Driven Tests
25

26. State Driven Tests
26
B
D
D

27. State Driven Tests
27

28. State Driven Tests
28

29. State Driven Tests
29 D
SL
B
uiltforTests

30. Data Driven Tests
30

31. Data Driven Tests
31

32. Data Driven Tests
32
Succinctsyntax

33. Data Driven Test Results
33

34. Interaction Based Tests
34

35. Mock
35

36. Stub
36

37. Stub
37

38. Mock & Stub
38

39. Mock & Stub
39

40. Order
40

41. Order
41

42. and more…
42

43. you can even amaze your
colleagues with this:
(_.._) * _._(*_) >> _
43

44. Control
44

45. Extensions (Built-in)
• @Ignore
• @IgnoreIf
• @IgnoreRest
• @Requires
• @Timeout
• @Unroll
• @Stepwise
• @Rule
• @FailsWith
• @AutoCleanup
• @ConfineMetaClass
• @Use
• @Issue
• @Title
• @Subject
• @Narrative
45

46. Extensions (External)
• spock-spring
• spock-guice
• spock-grails
• spock-tapestry
• …
46

47. Control
47

48. Control
48

49. Extensions (Spring)
49

50. Extensions (DIY)
50

51. Extensions (DIY)
51

52. Extensions (DIY)
52

53. Extensions (DIY)
Demo
53
extension idea borrowed from kenspie spock presentation
@ JavaOne 2014

54. Under the hood
• It’s Groovy!
• It uses Groovy AST Transformations
• It’s a JUnitRunner -> IDE Support, Build Tools
Support… anything that supports JUnit also
supports Spock
54

55. Wow!
• Cost of context switch - Legacy tests
• Cost of learning new DSL - “Legacy” developers
So, is there any reason why NOT to start using
Spock?
55

56. Use Spock
• Easier to write
• Easier to read
• Easier understanding of failures
• Promotes good structured tests
• Allows non technical people to be involved
• Easy to extend
56

57. http://spockframework.org/
http://docs.spockframework.org/
https://github.com/spockframework/spock
My code examples:
https://github.com/langera/spock_presentation
Alert Extension:
https://github.com/langera/AlertSpockExtension
Thank you
57