We’ve covered a lot of ground in the past few blog posts, including how to contribute to the project, and some details of what you can expect as a Selenium user. But there’s more to Selenium than just the APIs you use to write your tests, and one of the big features we’ve not covered yet is the refreshed Selenium Grid: a mechanism that allows you to distribute your tests across a fleet of machines.
Like most other companies (essential workers notwithstanding), we were forced to shift to an all-remote workforce, meaning many Saucers found themselves working from home for the first time. This presented challenges, of course—some of us simultaneously became homeschool teachers, we lost the ability to have quick hallway conversations, and we just plain missed seeing our coworkers—but in the end, we rallied together and embraced the new normal (or should we say the Zoom normal?).
By now you may have seen the news that Sauce Labs has acquired API Fortress, a leading provider of modern API testing solutions for agile and DevOps teams. This is an exciting milestone for us, and we are thrilled to welcome the capable API Fortress team into the Sauce Labs team! Here, I’d like to go into a bit more depth on why we did this acquisition and what this will mean for our customers.
Sauce Labs provides a number of features that help secure your testing experience and ensure that your data and applications are safe while using our cloud platform. One of the most popular features is Sauce Connect Proxy—a built-in HTTP proxy server that opens a secure "tunnel" connection for testing between a Sauce Labs virtual machine or real device and a website or mobile app hosted on your local computer ("localhost") or behind a corporate firewall.
Sauce Connect Proxy™ is a built-in HTTP proxy server that opens a secure "tunnel" connection for testing between a Sauce Labs virtual machine or real device and a website or mobile app hosted on your local computer ("localhost") or behind a corporate firewall. It provides a means for Sauce Labs to access your application or website.
A product manager’s job first and foremost is to deliver value to their customers with the products they oversee. In order to ensure quality, those products need to be tested. Testing before release in a well thought-out manner gives product managers the confidence to create and execute high quality products and user experiences.
In my last posts, we talked about how to contribute to Selenium, and why we’re bumping the version number to 4. That’s enough preamble! Today, we’ll cover some details about the new tricks and capabilities that Selenium 4 offers.
Many organizations are working toward digital confidence by optimizing their testing practices. This may look like reconfiguring the delivery pipeline to integrate quality more meaningfully, moving test infrastructure to the cloud, and automating an increasing number of test cases. While all of these are helpful steps on the road to achieving digital confidence, some use cases might not benefit from more automated testing.
You have decided to add the power of Selenium automated testing to your testing strategy, but are overwhelmed with how much learning is involved. The Selenium automation framework can be intimidating, and getting started with little to no experience can be a massive undertaking for any organization. The good news is that there is a great way to get started with automated functional testing and it’s not what you would expect: visual testing!
Automated UI testing is a daily struggle for efficiency and reliability. A single misconfigured line of code can cost teams in hours of lost feedback time and test error triaging—potentially costing companies hundreds of thousands of dollars. In this case study we will see how interactions with only two web elements led to a 34% degradation in the test execution time.
