whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Savu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (WHIRR-243) Allow to run component tests in memory
Date Wed, 06 Jul 2011 03:48:16 GMT

     [ https://issues.apache.org/jira/browse/WHIRR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andrei Savu updated WHIRR-243:

    Attachment: WHIRR-243.patch

Updated patch for the current trunk.

> Allow to run component tests in memory
> --------------------------------------
>                 Key: WHIRR-243
>                 URL: https://issues.apache.org/jira/browse/WHIRR-243
>             Project: Whirr
>          Issue Type: Improvement
>          Components: core
>            Reporter: David Alves
>            Assignee: Adrian Cole
>            Priority: Minor
>         Attachments: WHIRR-243-only-LogDryRunModule.patch, WHIRR-243.patch, WHIRR-243.patch,
WHIRR-243.patch, WHIRR-243.patch, WHIRR-243.patch, WHIRR-243.patch, WHIRR-243.patch
> 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


View raw message