[
https://jira.codehaus.org/browse/SUREFIRE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297755#comment-297755
]
Tuomas Kiviaho commented on SUREFIRE-811:
-----------------------------------------
I've got quite similar requirements and for me it was sufficient to replace
ForkedBooter with one that uses stub/skeleton pattern. Luckily I could use the
local filesystem so it was only matter of using aspectj's weaver as java agent
to avoid recompilation of surefire. I guess that this approach would have been
sufficient because - if I understood the code correctly - there is an internal
communication protocol that surefire uses to pass along test results and
logging information.
I guess it would be enough if ForkedBooter could be re-configured with a plugin
dependency so that knowledge of runtime weaving would not be required.
> remote-testing
> --------------
>
> Key: SUREFIRE-811
> URL: https://jira.codehaus.org/browse/SUREFIRE-811
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Failsafe Plugin
> Reporter: Henning Gross
>
> Add the possibility to copy the target folder to remote machine and run
> integration-tests there. Copy back the results and handle them as if they
> would have been ran locally.
> I would volounteer to submit a patch for this feature if theres a chance it
> would be accepted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
