[
https://issues.apache.org/jira/browse/WHIRR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Alves updated WHIRR-243:
------------------------------
Attachment: WHIRR-243.patch
I made the final changes against the latest trunk, maven is build is fine.
Here's what I changed:
- I renamed LogDryRunModule to DryRunModule (it does more that logging since it
captures script execution in order)
- I moved it to src/main. This might be a bit controversial but Noop is already
there and this way there is no need to build a test jar to use DryRun in other
modules.
- Finished the a test that makes sure that no setup scripts are executed after
the first configure script.
That should be all.
PS: I'm new to git diff I hope all is well please notify me if that is not the
case.
> 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:
> 0001-WHIRR-243-Corrected-chkstyle-and-rat-problems.patch,
> WHIRR-243-LogOutput.txt, WHIRR-243-Mod-Delay-Init-Script-Return.log,
> WHIRR-243-Mod-Delay-Init-Script-Return.patch,
> 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, 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
