> + HttpRequest delete = HttpRequest.builder().method(DELETE)
> +
> .endpoint("https://api2.dynect.net/REST/HTTPRedirect/redirect.adriancole.zone.dynecttest.jclouds.org/redirect.adriancole.zone.dynecttest.jclouds.org/";)
> + .addHeader("API-Version", "3.3.8")
> + .addHeader(ACCEPT, APPLICATION_JSON)
> + .addHeader(CONTENT_TYPE, APPLICATION_JSON)
> + .addHeader("Auth-Token",
> authToken).build();
> +
> + HttpResponse deleteResponse =
> HttpResponse.builder().statusCode(OK.getStatusCode())
> +
> .payload(payloadFromResourceWithContentType("/delete_redirect.json",
> APPLICATION_JSON)).build();
> +
> + public void testDeleteWhenResponseIs2xx() {
> + DynECTApi success = requestsSendResponses(createSession,
> createSessionResponse, delete, deleteResponse);
> +
> assertEquals(success.getHttpRedirectApiForZone("redirect.adriancole.zone.dynecttest.jclouds.org").scheduleDelete("redirect.adriancole.zone.dynecttest.jclouds.org").toString(),
> + Job.success(387955406l).toString());
> + }
> +}
There are several methods that throw a `JobStillRunningException` or return
`null` when the response code is 404. Could you add the corresponding expect
tests for those cases?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/37/files#r4773248
