anchor.diff:  	 bookWasDeleted()
   ----
   
  -As the implementation of the functionalities described by the contracts is not  yet present,
  - the tests will fail.
  -
  -To make them pass, the correct implementation of handling either HTTP requests or messages
  -will have to be added. Also, a correct base test class for auto-generated tests needs to be added to the project.
  -This class will be extended by all the auto-generated tests and it should contain all the setup
  -necessary to run them (for example `RestAssuredMockMvc` controller setup or messaging test setup).
  -
  -Once the implementation and the test base class are in place, the tests will pass, and both the application
  - and the stub artifacts will be built and installed in the local Maven repository. Information about
  - installing the stubs jar to the local repository will appear in the logs:
  +As the implementation of the functionalities described by the contracts is not yet
  +present, the tests fail.
  +
  +To make them pass, you must add the correct implementation of handling either HTTP
  +requests or messages. Also, you must add a correct base test class for auto-generated
  +tests to the project. This class is extended by all the auto-generated tests and should
  +contain all the setup necessary to run them (for example, `RestAssuredMockMvc` controller
  +setup or messaging test setup).
  +
  +Once the implementation and the test base class are in place, the tests pass, and both the
  +application and the stub artifacts are built and installed in the local Maven repository.
  +Information about installing the stubs jar to the local repository appears in the logs, as
  +shown in the following example:
   
   [source,bash,indent=0]
   ----
  
positive.code: public class LoanApplicationServiceTests {
  ----
  
  Now in your integration test, you will be able to receive stubbed versions of HTTP responses or messages that are
  expected to be emitted by the collaborator service. You will see entries similar to theses in the build logs:
  
  [source,bash,indent=0]
  ----
  
negative.code: }
  ----
  
  The preceding example uses Spring's `MockMvc` to run the tests. This is the default test
  mode for HTTP contracts. However, JAX-RX client and explicit HTTP invocations can also be
  used. (To do so, change the `testMode` property of the plugin to `JAX-RS` or `EXPLICIT`,
  respectively.)
  
  Apart from the default JUnit, you can instead use Spock tests, by setting the plugin
  `testFramework` property to `Spock`.
  
  TIP: You can now also generate WireMock scenarios based on the contracts, by including an
  order number followed by an underscore at the beginning of the contract file names.
  
  The following example shows an auto-generated test in Spock for a messaging stub contract:
  
   [source,groovy,indent=0]
  ----
  