[
https://jira.codehaus.org/browse/SUREFIRE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287248#comment-287248
]
Henning Gross commented on SUREFIRE-811:
----------------------------------------
Well. In our case we have an onboard-unit. The target system has a variety of
diffs to the build server. Jenkins is running on a 64 bit machine, the target
system is 32 bit. This can be solved via maven but then again... the binary
under test is not the one which gets released.
Also we would need jenkins support firing some x as we want to test out SWT -
Gui. Finally we interoperate with a lot of low-level stuff as dbus which
requires native/system libs. Or even GPS, Cameras, devices connected via
LIN-Bus. We could mock most of it but some automated real-life-tests would be
good. Also some requirements to the build server would remain and this system
is building a lot of projects which are supposed to be portable as our admins
do not know about the specific per-project-requirements. We tend to rather make
our projects build whereever and i do not see a better fit for
integration-system-tests as the one suggested. Do you? I would appreciate your
ideas...
> 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
