Zynga, the best social gaming company period, is hiring Software Engineer in Test positions here in San Francisco.
For more details, please go to http://hire.jobvite.com/j/?cj=ojFhWfwV&s=SauceLab

Thanks
Richard

Best,
Santi

As discussed in our email thread, you can run both different as well as the same browser instances in parallel without any limitation other than the ones in your account.
Regarding screenshots and video, I don't think these could be involved in such a considerable slowdown. I'd advise you to just try disabling and see the results, my guess is they shouldn't account for more than 5% of your tests' time. Generally such time differences are related to the latency added by sending every single Selenium command through the internet into our service. I'd recommend you to make sure the computer running tests is on a wired connection and has fast and reliable internet access.

Best,
Santi

We have plenty of users running under most of the CI servers available. These include Jenkins and Bamboo, for which we have plugins that provide some useful features.
Basically, as far as you write your tests in one of the supported programming languages and you have a way for these to be run from a console, you'll be able to make any CI server trigger them pretty easily and therefore run your tests in sauce automatically.

Hope that helps.
Santi

It's easy to upgrade your bundled version, though (and thus get bugfixes, compatibility with recent browser versions, etc.):

• Download the latest version of Selenium Server from http://seleniumhq.org/download/

• Copy that JAR (currently selenium-server-standalone-2.7.0.jar) into your Sauce RC install directory

• Rename it to replace the existing selenium-server.jar

• Restart Sauce RC; that's it!

[26-Sep-2011 17:39:07] PHP Fatal error:  Class 'PHPUnit_Extensions_SeleniumTestCase_SauceOnDemandTestCase_Driver' not found in /Applications/MAMP/bin/php/php5.2.17/lib/php/PHPUnit/Extensions/SeleniumTestCase/SauceOnDemandTestCase.php on line 139

Any ideas?

I have the following code in the Watir:
allMandatoryFields = $b.elements_by_xpath("//div//span[@class='required']/../../input")

I'm using the following code within RSpec:
allMandatoryFields = page.find_elements(:xpath, "//div//span[@class='required']/../../input")
I have to translate that into RSpec to be able to run that in the cloud. However I get:

undefined method `find_elements' for #<Sauce::Selenium:0x14fadb88>

Can you point me how do I retrive all elements of a page by a specific xpath?

Thanks,
Vlad

There's no near term plans to write a blog post about this topic, mostly due to the cost of writing parallel ruby runners in windows.
My advice would be to give it a shot using cygwin under windows (which is aimed to reproduce a linux environment without resorting to virtual machines or dual boot).

Hope that helps
Santi

C:\path-to-ruby\ruby script\generate sauce username apikey

Hope that works.

Best,
Santi

The main reason for which Sauce OnDemand can't tell when a test failed or passed in your end, is because of the way Selenium's client-server architecture works. As you can see in your jobs result pages, Sauce OnDemand only gets plain browser commands any time your test needs to do something in the browser. Nothing except for that gets to our end.

This means that when your test runs something like:

self.assert(selenium.isElementPresent("bleh"))

In our end, we only get the isElementPresent request and we don't actually know if this element was expected to be present or missing for the test to pass or fail in your end.

This is why we've built an additional layer, in which tests provide us extra information about things, to help us display the jobs appropriately later.

Here's our pass/fail status documentation:
http://saucelabs.com/docs/sauce-ondemand#passed

We've also built these inside some of the libraries that we provide to our users, so if you are using PHP or Ruby to run your tests, the test framework should be handling this for you automatically. Please let me know if that's the case.

Regarding re-running failed cases for certain number of times. This is something that has to be done in the client side. As your script is the one executing the real test, it has to be the one with the logic to detect failures and re-run using Sauce.

Best,
Santi

Let us know how it goes.

Best,
Santi

You should check out the following forum thread on that matter:
http://support.saucelabs.com/entries/20 … slow-tests

Best,
Santi