Posts Tagged ‘Sauce Labs’

Updates Coming to Default Selenium and Chrome Versions on Sauce (August 2)

July 28th, 2014 by Santiago Suarez Ordoñez

On Saturday, August 2nd, we will update our Selenium and Chrome default versions to meet current, stable implementations. This update affects users that run automated Selenium tests on Sauce.

Default versions of Selenium and Chrome are used only for tests that don’t have a specified browser version. Users who choose to assign Selenium and Chrome versions to their tests will remain unaffected.

Below you’ll find more details about the updates.

Selenium

Currently the default Selenium version is 2.30.0. Following the update on August 2, the new default Selenium version will be 2.42.2. We advise you to test the new version (2.42.2) in advance using the following desired capability:

"selenium-version": "2.42.2"



If you run into any issues with the new default, note you can continue using the previous version (2.30.0) after Saturday by making the test request the selenium-version desired capability referred to below:

"selenium-version": "2.30.0"


Chrome

Currently the default Chrome versions are Chrome 27 and Chromedriver 1. Following the update on August 2, the new default Chrome versions will be Chrome 35 and Chromedriver 2.10. We advise you to test the new versions (Chrome 35, Chromedriver 2) in advance using the following desired capabilities:

"browserName": "chrome"
"version": "35"



By requesting Chrome 35, Chromedriver 2.10 will be used automatically.


If you run into any issues with the new default, you can continue using the previous versions (Chrome 27, Chromedriver 1) after Saturday by making the test request the “version” desired capabilities referred to below:

"browserName": "chrome"
"version": "27"


Troubleshooting Issues

If you see any issues after moving your tests to these new versions, we suggest checking for known issues on https://code.google.com/p/selenium/issues/list or contacting the Chromedriver and Selenium user groups.

Happy testing!

[Re-Blog] Dev Chat: Vlad Filippov of Mozilla

July 28th, 2014 by Amber Kaplan

Last week Sauce Labs’ Chris Wren took a moment to chat with Vlad Filippov of Mozilla on his blog. Topics covered all things open source and front-end web development, so we thought we’d share. Click the image below to read the full interview, or just click here.

Dev Chat: Vlad Filippov of Mozilla

 

Campus Explorer Reduces Testing Time From 72 Hours to 72 Minutes Using Sauce Labs

July 18th, 2014 by Amber Kaplan

We sat down with Senior QA Manager Sage Rimal to hear how they use Sauce Labs at Campus Explorer.  Sage shared how they’ve automated their tests on Sauce, and have since reduced their testing time from 72 hours to 72 minutes.

Watch the video below to get the latest!

Want to share your story? We want to hear from you! Submit a request here.

Microsoft Launches IE Developer Channel; Win For WebDriver

June 20th, 2014 by Amber Kaplan

In light of the recent news about Microsoft  launching an IE Developer Channel that features WebDriver support, we asked our own VP of Engineering to comment on the story. His post is below – enjoy!

I think all web developers can identify with that fateful moment when you think your front-end project is finished, and then it dawns on you: time to start the painful process of cross browser testing and debugging. You may get up and walk around the office, procrastinate, look for conversations to start — but eventually you sit down and dive in. Historically Firebug was your main crutch; over time Chrome dev tools started to take hold - but eventually you find yourself waiting for your Windows VM to boot, so you can dive into IE’s latest and wait for the fateful popup stating something like, line 66, “Error: Object expected” – let the games begin.

The moment I saw Selenium IDE zooming through functional tests, I was more excited than I had ever been about development tools. The debug loop required to squash JavaScript bugs in IE from a Mac was so painful, and finally there was some automated hope in sight. I think we can all agree that Selenium RC left something to be desired — but trying to drive a browser against its will (and protective security measures) using JS was ultimately a losing battle for anything reliability.

However, reading the recent news from Microsoft announcing the IE developer channel made the DOM hacker inside me from 5 years ago breathe a sigh of relief. I think it’s fair to say that it’s better late than never — and the tools they are starting to ship look pretty cool. But what’s more — the new process and way they are looking at shipping features through a dev channel shows some promising potential for a better future relationship between dev’s and IE. On the Sauce Labs cloud we are still seeing ~19 percent of our jobs running against IE, and we don’t expect that to disappear anytime soon – as the IE market share still makes up for a pretty substantial amount of users, especially in regards to enterprise customers.

What’s even more exciting is the inclusion of the ability to enable built in WebDriver. At this point ~86 percent of Sauce Cloud usage is WebDriver instead of Selenium RC. The browser vendor support of for the WebDriver JSONWireProtocol specification, has driven the continued and significant growth of the community around client libraries and tools. The acknowledgement and delivery of a clean implementation of this spec for IE and inferred ongoing maintenance is a step in the right direction in order to make functional testing for IE straight forward and reliable. The ultimate stated goal of the Selenium project, is to move the entire implementation of the specification into the browsers – and this, in combination with the W3C working draft, are exciting steps in that direction.

At the moment, to take advantage of all this new goodness, you must be running a consumer grade version of Windows (not a server version), but they are aware of that and understandably wanted to get some progress out the door. We are looking forward to deploying this to the Sauce Cloud, so that our users can quickly get access to the latest and greatest.

I think the Selenium and developer communities should see this as a great sign that we are being heard, and supported, and to continue pushing hard to make development and testing tools first class citizens.

-Adam Christian, VP Engineering, Sauce Labs

You can read the announcement and detail breakdown here. Get directions on how to enable and play with the new functionality in their documentation here. Sauce Labs is working to support this upon availability on server windows versions; stay tuned for updates upon release.

Re-Blog: JavaScript Multi Module Project – Continuous Integration

June 11th, 2014 by Amber Kaplan

lubos-krnacOur friend Lubos Krnac describes how to integrate Sauce with Protractor in a quest to implement continuous integration in his JavaScript multi module project with Grunt.

Below is a quote from his most recent blog post along side some code.

Read the rest of his post to get the full how-to here.

An important part of this setup is Protractor integration with Sauce Labs. Sauce Labs provides a Selenium server with WebDiver API for testing. Protractor uses Sauce Labs by default when you specify their credentials. Credentials are the only special configuration in test/protractor/protractorConf.js (bottom of the snippet). The other configuration was taken from the grunt-protractor-coverage example. I am using this Grunt plug-in for running Protractor tests and measuring code coverage.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
// A reference configuration file.
exports.config = {
  // ----- What tests to run -----
  //
  // Spec patterns are relative to the location of this config.
  specs: [
    'test/protractor/*Spec.js'
  ],
  // ----- Capabilities to be passed to the webdriver instance ----
  //
  // For a full list of available capabilities, see
  // and
  capabilities: {
    'browserName': 'chrome'
    //  'browserName': 'firefox'
    //  'browserName': 'phantomjs'
  },
  params: {
  },
  // ----- More information for your tests ----
  //
  // A base URL for your application under test. Calls to protractor.get()
  // with relative paths will be prepended with this.
  baseUrl: 'http://localhost:3000/',
  // Options to be passed to Jasmine-node.
  jasmineNodeOpts: {
    showColors: true, // Use colors in the command line report.
    isVerbose: true, // List all tests in the console
    includeStackTrace: true,
    defaultTimeoutInterval: 90000
  },
  
  sauceUser: process.env.SAUCE_USERNAME,
  sauceKey: process.env.SAUCE_ACCESS_KEY
};

You may ask “how can I use localhost in the configuration, when a remote selenium server is used for testing?” Good question. Sauce Labs provides a very useful feature called Sauce Connect. It is a tunnel that emulates access to your machine from a Selenium server. This is super useful when you need to bypass company firewall. It will be used later in main project CI configuration.

Have an idea for a blog post, webinar, or more? We want to hear from you! Submit topic ideas (or questions!) here.

Win A Gift Package From Sauce Labs (Twitter Contest)

April 17th, 2014 by Amber Kaplan

Have you seen our Test All The Things t-shirts on the twitterverse yet? We get a lot of compliments on them (thanks, we’re blushing) and a lot of requests for them, too. Although they’re not available for purchase on the site, we thought we’d do a fun giveaway for a couple of lucky winners. Plus you never know, you could get a few spicy accoutrements to go with it.

The contest is easy. Rules below:

  • If you’re not already doing so, follow us on Twitter: @saucelabs
  • Then, retweet the embedded tweet below OR any more updates that we post about this contest on Twitter. Bonus points for including our hashtag, #TestAllTheThings, and for using our handle, @saucelabs.
  • A lucky person who’s retweeted one of our contest messages will win a care package.
  • Our 5,000th follower will also win a care package.
  • The more often you retweet us or mention the contest, the better! Hey, we never said we weren’t biased.
  • Both retweets and modified tweets will be counted.
  • Contest will close on May 15 or after we get our 5,000th follower; whichever comes first.
  • We’ll notify winners via direct message on Twitter.

You know you want it! Good luck, Saucers.

Follow us and retweet this message for a chance to win gift package from Sauce Labs!

Ohai, 100 Million Tests on Sauce Labs!

February 27th, 2014 by Amber Kaplan

Today we’re ecstatic to announce we surpassed 100 million test runs on Sauce Labs. Yep, that’s right. 100 MILLION tests have been executed on our cloud of real browsers and platforms. Now that’s a whole lotta testing, don’t ya think?!

It’s been an awesome couple years for Sauce, Selenium and automated testing in general. So we thought we’d use this milestone to look back at the growth both internally and within the testing community at large with a fun infographic below. Some of our favorite highlights include:

  • Support for browsers / OS platforms grew from 41 in 2010 to 270+ in 2014
  • Selenium IDE has been downloaded more than 10 million times
  • 10,000+ ounces of Saucy hot sauce distributed all over the world

It’s been a heck of a ride over the last five years, and we couldn’t be happier to be part of the movement. Onward to 200 Million!

Click to enlarge

Click to enlarge

Announcing iOS 7 support in the Sauce Labs Cloud

October 31st, 2013 by Ashley Wilson

ios7_01

Today we’re excited to let you know that you can now test your hybrid and native apps with iOS 7 on Sauce. With more than 200M downloads since its release, we know that this is an important platform for our users to test on.

To get started, visit our browsers and platforms page for Appium and copy and paste the DesiredCapabilities provided for either version of iOS (or Android) you want to test on. And if you’re new to mobile test automation in general, check out our Getting Started with Appium guide.

If you have any issues, give us a shout. Otherwise, happy (iOS 7) testing!

Come Visit Sauce at Apps World 2013

October 11th, 2013 by Bill McGee

Want a great reason to visit London later this month? Our very own Santiago Suarez Ordoñez, Senior Infrastructure Developer, will be sitting on an Apps World 2013 panel on October 23rd titled “Best practices in managing QA testing for the multi-device nightmare”. Apps World 2013 is Europe’s largest multi-platform app event and takes place at Earls Court 2 in central London on the 23rd and 24th of this month.

The panel will be moderated by Martin Wrigley, Executive Director, App Quality Alliance (AQuA) and Santi will be alongside Matthew Brown (Test Manager, Apptivation), Philipp Benkler (Founder & CEO, Testbirds) Paul Rutter (Test Manager – Mobile Platforms, BBC) and Becky Wetherill (Product Director, Borland) – a royal QA roster!

Topics to be discussed include determining how many devices to test, whether or not emulators can be effective as a substitute to testing on actual devices, the balance  of functional, compatibility & performance testing requirements across devices, issue resolution strategies post launch and more.

Once you’ve tucked the panel under your belt (and all of the juicy take-aways), please be sure to take a quick jaunt to stand 217 and say hello to Saucers! We’ll be demo’ing Appium, an open source test automation framework that aims to turn multi-device QA testing from nightmare to a dream. Did we mention there will also be a spiffing robot too?

So hop on the tube and come join the Saucers at Apps World 2013. Cheerio!

Announcing Selenium 2.30.0 as the New Default Version for Sauce Automated Tests

February 22nd, 2013 by Santiago Suarez Ordoñez

After a considerable period of investigation and bug fixing in collaboration with the Selenium project and the Legion of the Bouncy Castle, we are happy to announce we’re moving to Selenium 2.30.0 as the default version in our service. You can find more details about this release in the official changelog.

This transition is scheduled for Friday, March 1st. In the meantime, we advise you to try your tests on this new version by adding the following key-value to your tests’ Desired Capabilities:

"selenium-version": "2.30.0"

If you see any issues after moving over to this new version, we definitely want to hear about it. And remember, once we move everyone to 2.30.0, you can still keep your tests on our previous default (Selenium 2.18.0) version by using the “selenium-version” capability outlined above.

Happy testing!