You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Adrian Cole (JIRA)" <ji...@apache.org> on 2014/11/05 21:45:34 UTC

[jira] [Commented] (JCLOUDS-771) Deprecate and destroy Expect tests; use MockWebServer instead

    [ https://issues.apache.org/jira/browse/JCLOUDS-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199055#comment-14199055 ] 

Adrian Cole commented on JCLOUDS-771:
-------------------------------------

ps expect tests are already beta, so we can nuke them as soon as we migrate off.

> Deprecate and destroy Expect tests; use MockWebServer instead
> -------------------------------------------------------------
>
>                 Key: JCLOUDS-771
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-771
>             Project: jclouds
>          Issue Type: Task
>          Components: jclouds-core
>            Reporter: Adrian Cole
>              Labels: technical_debt
>
> As I'm sure questions will arise.. why MockWebServer? Reason is that tests based on MWS are resilient to design changes.  Ex. we can completely replace how annotations are processed without rewriting the test. Moreover, unlike ExpectTest, MWS has no dependency on how jclouds represents http requests. That means that even changes to our class structure around http requests can be made without rewriting tests!
> Once we decouple our tests from jclouds internals, we can change them.
> Also, we divorce ourselves from having to maintain our own test framework which has caused problems in flakey tests as well difficulty in troubleshooting. Expect test was a nice idea but it was only partially realistic, yet took as much or more work to write classes for than MWS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)