✅ Authorized request can be made
✅ Authorized request can be made and configured by function
✅ DELETE request can be made to a test server
✅ GET request can be made to a real server
✅ GET request can be made to a real server, with mixed data
✅ GET request can be made to a test server
✅ GET request can be made to a test server, with a named test
✅ GET request can be made to a test server, with mixed data
✅ GET request can be made with mixed data
✅ HEAD request can be made to a test server
✅ OPTION request can be made to a test server
✅ PATCH request can be made to a test server
✅ POST request can be made to a real server
✅ POST request can be made to a test server
✅ PUT request can be made to a test server
✅ Repeated GET requests can be made to a real server
✅ Repeated GET requests can be made to a real server with extra data
✅ Repeated GET requests can fail after the schedule completes
✅ TRACE request can be made to a test server

✅ An authorized endpoint can be called with a test token
✅ An authorized endpoint can be called without a token and is unauthorized

✅ DELETE request can be made to a test server
✅ GET request can be made to a real server
✅ GET request can be made to a real server, with mixed data
✅ GET request can be made to a test server
✅ GET request can be made to a test server, with a named test
✅ GET request can be made to a test server, with mixed data
✅ GET request can be made with mixed data
✅ HEAD request can be made to a test server
✅ OPTION request can be made to a test server
✅ PATCH request can be made to a test server
✅ POST request can be made to a test server
✅ PUT request can be made to a test server
✅ Repeated GET requests can be made to a real server
✅ Repeated GET requests can be made to a real server with extra data
✅ TRACE request can be made to a test server

✅ A http factory can be called for a client with a fixed number of responses setup
✅ A http factory can be called for a client with a single response setup
✅ A http factory can be called for a client with no matching setups
✅ A http factory can be called for an unknown named client
✅ A http factory can be mocked for a given request, returning a configured response

✅ No validation certificate validator always returns true

✅ And can be used to combine matchers
✅ And can be used to combine matchers, must match all conditions
✅ HasBearer can match on a provided token
✅ HasContent can match on a provided request content
✅ HasJsonContent can match on a provided request content
✅ HasJsonContent can not match on a provided request content
✅ HasJsonContent can not match on a provided request content that is different valid json
✅ HasJsonContent can not match on a provided request content that is not valid json
✅ HasMethod does not match for the incorrect HTTP method
✅ HasMethod matches for the correct HTTP method
✅ HasRequestUri can match on a provided request uri
✅ HasRequestUri can match on a provided request uri including host and port
✅ HasXmlContent can match on a provided request content
✅ HasXmlContent can not match on a provided request content
✅ HasXmlContent can not match on a provided request content that is different valid xml
✅ HasXmlContent can not match on a provided request content that is not valid json
✅ Or can be used to combine matchers
✅ Or can be used to combine matchers, match only second condition
✅ Or can be used to combine matchers, no matches
✅ Or can be used to combine matchers, no matches again

✅ Test sending a body in the request to test server and logging it
✅ Using a startup class in the test service builder works
✅ Using a startup class in the test service builder works with replacements

✅ Tests for the build methods