You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "David Alves (JIRA)" <ji...@apache.org> on 2011/02/28 22:05:36 UTC
[jira] Updated: (WHIRR-243) Allow to run component tests in
isolation from JClouds
[ https://issues.apache.org/jira/browse/WHIRR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Alves updated WHIRR-243:
------------------------------
Status: Patch Available (was: Open)
Adds the option of building a "test" (assigned statically) provider to the ComputeServiceContextBuilder as well as the StubComputeServiceContext/StubComputeService itself.
The Stubs are not complete, i.e. they just have the features I needed so far.
> Allow to run component tests in isolation from JClouds
> ------------------------------------------------------
>
> Key: WHIRR-243
> URL: https://issues.apache.org/jira/browse/WHIRR-243
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: David Alves
> Priority: Minor
>
> While jclouds now features the awesome BYON mode it might be useful to be able to run compoenent and systems tests without jclouds.
> I tried jclouds stub features but unless I'm missing something (I might) there is no way of stubbing a compute service that allows to call runOnNodesMatching.
> So my idea is to alter ComputeServiceContextBuilder a bit to account for a new provider ("test") in which case an instance of a StubComputeServiceContext is returned (which features a StubComputeService internal class). This allows to make assertion regarding which nodes were started or not and on which order, which I think is useful.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira