[
https://issues.apache.org/jira/browse/WHIRR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129567#comment-13129567
]
David Alves commented on WHIRR-243:
-----------------------------------
I know creating a test jar is easy (I use it all the time). The thing is that
it then must be published along with the regular jar wherever (repo1 someday?)
so creating a new deployment artifact for a public project and for a single
class is something we might want to avoid.
Then there is the design aspect of whether DryRunModule is really a test class.
That, I think, is debatable and could go either way. For instance StubProviders
in jclouds lives in the jclouds-compute jar not on a test jar.
All this being said, all I would really like was for the class to be packaged
so that it could be used outside whirr-core. I personally would choose the main
jar (less hassle, less artifacts) but I will follow the majority :)
> 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
