Note that there are some explanatory texts on larger screens.

plurals
  1. POSelenium testing machine
    text
    copied!<p>--- <strong>TL;DR</strong></p> <p>At this point I suggest everyone to tied their Continuous Integration server/service to <a href="https://ghostinspector.com/" rel="nofollow noreferrer">https://ghostinspector.com/</a></p> <p><strong>OLD QUESTION</strong></p> <p>after three days googling and testing I gave up, and I need help.</p> <p>My objective is allow my co-workers to record one or more tests with Selenium IDE. Export them, upload them into a server, and get this server running these tests using the webdriver with htmlunit. As we build or fix the app, we will upload the tests to make out test library.</p> <p>Record a test with Selenium IDE is okay. But getting it running is the problem. The machine we intend to let the tests is an linux amazon server. No front-end stuff, no kde, gtk, so no firefox, chrome, etc... This is why I've specified the htmlunit driver.</p> <p>So far I wasn't able to get this task running even into my machine - Ubuntu 12.04 x86_64.</p> <p>I downloaded the selenium-server tarball, and tried running:</p> <pre><code>java -jar selenium-server.jar -htmlSuite "*webdriver" "our.site.org" "/path/to/testsuite1.html" "/path/to/report1.html" </code></pre> <p>No success. Even changing the "*webdriver" (using other pops-up a browser screen).</p> <p>I've tried running the server and the standalone server and connecting via browser.</p> <p>I've tried PHP bindings by facebook.</p> <p>I've tried PHPUnit and Testing Selenium classes - along with their respectives exported scripts from Selenium Formatters.</p> <p>I really do not know where I'm slipping. Can anyone give me a safe direction, tutorial, etc, to follow with?</p> <p>--- <strong>EDIT</strong></p> <p>Okay, my question may be resumed to:</p> <p>What si the command line that would allow me to run selenese scripts with selenium-server, using the HtmlUnit driver?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload