|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
<quote>This exchange seems to be no longer useful.</quote>
Full ACK - This exchange really seems to be no longer useful.
----------
BTW - About running Selenium Tests: The typical way is to deploy the built software package to a (mostly remote) testing environment (along with the Selenium scripts), then trigger the script execution on this environment, collect the test result data and display it in the report on Jenkins.
We have done lot's of this, and all work without trouble and don't require any desktop/user-interface interaction at all.