[
https://issues.apache.org/jira/browse/JCLOUDS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-359:
--------------------------------
Fix Version/s: (was: 2.1.0)
> Modify jclouds-chef unit tests to use mockwebserver
> ---------------------------------------------------
>
> Key: JCLOUDS-359
> URL: https://issues.apache.org/jira/browse/JCLOUDS-359
> Project: jclouds
> Issue Type: Test
> Components: jclouds-chef
> Affects Versions: 1.7.1
> Reporter: Noorul Islam K M
> Priority: Minor
> Labels: test
>
> From nacx in one of the pull requests
> I'll merge this PR, but after some discussions in the mailing list, we are
> improving the way we implement unit tests. We are switching to use
> [mockwebserver](http://code.google.com/p/mockwebserver/) instead of our
> custom mock (generated by the `requestSendsResponse` methods). The main
> difference when using mockwebserver is that the request is actually sent over
> the backing http connection, so the tests are more complete and give us more
> confidence that our apis work as expected.
> It would be great to use that in upcoming pull requests. There are still no
> tests in jclouds-chef that use it, but if you are willing to start with a
> test base class we can reuse (and perhaps start changing some existing
> ExpectTest to the new MockTest), you can take a look at the MockTests classes
> in the
> [openstack-swift](https://github.com/jclouds/jclouds-labs-openstack/tree/master/openstack-swift/src/test/java/org/jclouds/openstack/swift/v1/features)
> api to see an example of how they work (they are pretty similar to our
> Expect tests, though).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
