anchor.diff:          // Send a test HTTP request to the service (resulting in executing the policy).
           PolicyTestResponse response = send(PolicyTestRequest.build(PolicyTestRequestType.GET, "/some/resource")
                   .header("X-Test-Name", "testGet"));
  -                
  +
           // Now do some assertions on the result!
           Assert.assertEquals(200, response.code());
           EchoResponse entity = response.entity(EchoResponse.class);
  
positive.code: ```
  
  In this example everything works as it did before, but instead of responding with an Echo Response
  the send() method will return with a custom response (as created and returned by the provided custom 
  back-end service implementation).
  
negative.code: The @TestingPolicy annotation is always placed at the class level, but the @Configuration annotation can
  either be global or specified at the test method level.
  
  These annotations tell the apiman Policy Testing framework *what* policy you want to test and the
  policy configuration you want to use when testsing, but you still need to actually send requests to a
  "service".  This is done using the "send(PolicyTestReqest)" method defined by the base class.  The
  send() method allows you to send a request (that you build) to the mock back-end service governed by
  your policy.  By default the mock back-end service is a simple "echo" service that responds to all
  requests with a JSON payload describing the request it received (more on how to override this default
  