StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>1. <a href="http://rob.coup.net.nz/2008/01/automated-dojo-testing-doh-selenium-rc.html" rel="nofollow">Automated Dojo testing - DOH & Selenium-RC</a> (Rob Coup - 2008/01/03)</p> <blockquote> <p>Plan:</p> <ul> <li>Have a config file defining which browsers to launch, which machines they're on, and what tests to run. </li> <li>Launch each browser via Selenium-RC</li> <li>Run the tests via the normal DOH browser runner. </li> <li>Use Selenium to extract the results from DOH.</li> <li>Collate the results from the various browsers and produce something useful.</li> </ul> <p>Solution:</p> <ul> <li>Drop <code>seleniumRunner.js, seleniumRunner.config.js, seleniumRunner.sh</code> (or the <code>.bat</code> if you're on Windows), and <code>selenium-java-client-driver.jar</code> into <em>util/doh/</em> in your Dojo install.</li> <li>Put <code>selenium-server.jar</code> on each test machine, then run <code>java -jar selenium-server.jar -multiWindow</code> so it listens for the browser-control messages.</li> <li>Edit <code>seleniumRunner.config.js</code> and change <code>browsers</code> and <code>rootUrl</code> to match your setup. The <code>rootUrl</code> needs to be reachable from each test machine.</li> <li>run <code>./seleniumRunner.sh seleniumRunner.config.js</code> from <em>util/doh/</em> on your workstation</li> <li>It'll load the config, fire up the browsers on each machine, run the unit tests from Dojo core, and print the pass/fail/error stats for each.</li> <li>Each browser is kicked off and monitored in a separate thread (not strictly necessary but too cool to resist doing).</li> </ul> <p>Issues:</p> <ul> <li>unless I ran the selenium server in multiWindow mode Safari and Firefox would pop up Print dialogs (!?!) whenever the test page was loaded. But Safari never initialised the test page if it was in multiWindow mode. On OSX and Windows. gah.</li> <li>Opera on OSX didn't set up the Selenium proxy properly (<code>localhost:4444</code> for reference).</li> <li>IE didn't like doing a <code>dojo.connect()</code> via the selenium javascript commands for some reason.</li> </ul> </blockquote> <p>2. Seems reasonable to me.</p> <p>3. <a href="https://wiki.jenkins-ci.org/display/JENKINS/Selenium+Plugin" rel="nofollow">Jenkins Selenium plugin</a></p> <blockquote> <p>This plugin turns your Jenkins cluster into a Selenium2 Grid cluster, so that you can utilize your heterogeneous Jenkins clusters to carry out Selenium tests. This plugin is a turn-key solution — no additional installation nor configuration is necessary to make it work. The plugin installs Selenium Grid on all the slaves automatically and set up a grid on its own.</p> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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