anchor.diff:  ----
   
   [[GroovyMocks]]
  -== Groovy Mocks (New in 0.7)
  +== Groovy Mocks
   
   So far, all the mocking features we have seen work the same no matter if the calling code is written in Java or Groovy.
   By leveraging Groovy's dynamic capabilities, Groovy mocks offer some additional features specifically for testing Groovy code.
  
positive.code: ****
  
  [[declaring-interactions-at-creation-time]]
  === Declaring Interactions at Mock Creation Time (New in 0.7)
  
  If a mock has a set of "base" interactions that don't vary, they can be declared right at mock creation time:
  
  
negative.code: }
  ----
  
  === Grouping Interactions with Same Target
  
  Interactions sharing the same target can be grouped in a `Specification.with` block. Similar to
  <<declaring-interactions-at-creation-time,Declaring Interactions at Mock Creation Time>>, this makes it unnecessary
  