New Open Sauce UI and Refreshed Build Status Badges

June 20th, 2016 by Yaroslav Borets

 

We love open source. As advocates and contributors, we benefit from community participation and return the love via Open Sauce – free access to the Sauce Labs testing platform for open source projects. We’ve recently made some improvements to Open Sauce that enhances the UI and makes sharing results easier. Here’s the rundown:

  1. Simplified Badge Sharing Flow. Open Sauce users will see a new badge directly on their dashboards notifying them of the status of their latest build. Clicking on the badge will reveal a new window with inline links.image (10)
  2. New Build Status Badges.We’ve developed two new icons / badges that users can use to share the status of their latest builds on their GitHub pages or embed them anywhere where the information is needed.share badge2
  3. New Build Matrix. In addition to the badges, we’ve revised our existing browser matrix to allow our users to quickly see which browser/OS combinations the build ran against and which platforms experienced a failure.Build Matrix
  4. Redesigned Public Open Sauce Profiles. Clicking on one of the status badges or build matrixes will automatically redirect to a branded open sauce UI that allows anyone to see recent jobs performed by the open sauce user without the need to log in. Public Builds

 

Finally, the UI changes are only targeted at our Open Sauce users and won’t be seen by users on any of our other plans. As before, users with private builds (any of our paid plans) can choose to use the new badges by adding an HMAC token.

If you have any questions, please drop a note to help@saucelabs.com.

Happy Testing,

The Sauce Labs Team

 

More VMs for Open Sauce!

June 2nd, 2015 by Ken Drachnik

We love open source. As open source advocates and contributors ourselves, we know it’s important to support projects that we benefit from on a regular basis. And what better way to do it than by providing the infrastructure that helps ensure new releases are fully tested?

We have long teamed up with Travis-CI to provide a seamless experience across our platforms. However there was a disconnect in that the # of VMs each platform could support was not the same – Travis supported 5 instances and Sauce just 3. Well we just fixed that and have increased the number of VMs that you can use in Open Sauce to 5. This will allow users of Travis and Sauce to maximize their test concurrencies and complete tests faster so you can speed your apps to market.  Not using Travis CI? Don’t worry, the 5 VMs still apply.

Learn more about Open Sauce.

Learn more about Travis CI

Guest Post: Open Sauce Enables Plone to Focus on Robot Framework

May 16th, 2014 by Bill McGee

Robot Framework Our friends in the Plone community recently took to Open Sauce for their testing needs to save time. The results have been stellar; with the time saved they’re able to focus on improving Robot Framework, according to their release manager Eric Steele.

Check out the rest of what they have to say below.

When I took over as release manager for the Plone CMS project, we ran our test suite nightly, but that only covered our Python code and some simple form submissions. The entire JavaScript layer remained largely untested, save a few click-arounds by hand before each release. The suspicion that some critical feature might have broken in a browser combination we hadn’t tried kept me up at night. As I began preaching the need for continuous integration and in-browser testing, it was surprising to find a whole team’s-worth of people excited to obsess over running tests, improving coverage, and collecting a fleet of VMs to run the few Selenium tests we’d put together at that point. The latter proved to be our undoing; we spent more time managing our testing infrastructure than we did doing actual testing.

Thankfully, Sauce Labs’ Open Sauce came along to save us.

Open Sauce has freed up my testing team to do far more interesting things. We’ve put quite a bit of effort into helping Robot Framework grow. Robot’s Behavior-Driven Development abstraction seems to fit everyones’ heads a bit better and allows us to easily alter tests based on which features are active. Asko Soukka, previously featured on this blog, became Plone’s Person of the Year for 2013 based on the work he put into extending Robot Framework for our community.

Asko has created a set of Robot keywords to enable automated screenshots for our Sphinx documentation. This allows our documentation to show the Plone user interface in the same language as the document. Groups deploying Plone sites can regenerate our end-user documentation with screenshots featuring their own design customizations. It’s a huge win; users see examples that look exactly like their own site. Finally, in a bit of pure mad science, Asko has piped those image generation scripts through a text-to-speech program to create fully-automated screencasts.

The Plone community is currently at work on the upcoming release of Plone 5. With its new widgets layer and responsive design, there are so many new ways that bugs could creep into our system. Happily, that’s not the case. I get a nightly report full of screenshots of Plone in action across browser, device, and screen size. Basic accessibility gotchas are quickly caught. Content editing and management features are automatically tested on both desktop and mobile. Open Sauce allows us to focus on getting things done and done correctly. Finally, I can sleep soundly — or at least find something else to worry over.Eric Steele, Release Manager, Plone.org. Read Eric’s blog here or follow him on Twitter.

Do you have a topic you’d like to share with our community? We’d love to hear from you! Submit topics here, feel free to leave a comment, or tweet at us any time.

Open Source Stories: Q&A with Lo-Dash

March 28th, 2014 by Bill McGee

LOAs you may already know, we LOVE open source. That’s why we created Open Sauce; a way to give open source projects the ability to test their projects for free on our cloud.

In the span of a year, we now have over 800 OSS projects testing on Sauce! To celebrate, we’re exploring some of the different projects tested on Sauce with a mini series of Q&A’s with users who have produced notable projects using Open Sauce.

Today we’re featuring an interview with John-David Dalton of Lo-Dash. Get the scoop below.

Can’t get enough of John-David?  Neither can we. You can hear him speak at Front End Ops Conf 2014. Register and get tickets now!

What is your OSS project, and what is its goal?
Lo-Dash is a utility library with an emphasis on consistency, customization, & performance.

What kind of testing does the project do, both on and off Sauce?
On Sauce we automate testing of Lo-Dash in legacy, compat, mobile, modern, & underscore builds (non-minified/minified and modularized AMD builds of each) against Lo-Dash/Underscore/Backbone unit tests. We test against IE6-11, old and new Firefox, Chrome, and Opera. We even test IE compat modes. Off Sauce we automate testing in Node, Narwhal, Phantomjs, Rhino, Rhino -require, & Ringo.

How has testing with Open Sauce helped the project?
Testing used to consist of ~2 days of manual testing. With Sauce & its paralleled jobs testing is automated to ~30 minutes.

Do you have any advice regarding testing for other open source projects?
Do it. Start small and build then pretty soon you’ll have a nice collection of tests. They’ll save you so much grief and build trust with your users/developers.

What’s next for the project?
We are building up to our v3.0 release with lots of features & some changes. Check out our roadmap https://github.com/lodash/lodash/wiki/Roadmap

How can people learn more about the project or get involved?
They can go to lodash.com or http://github.com/lodash/lodash

How have you used Open Sauce? Leave us a comment below, Tweet at us, or submit your story by way of a guest post!