May 26th, 2016 by Bill McGee
Thanks to everyone who signed up for our recent webinar, “Practical Tips and Tricks for Selenium Test Automation”, featuring Selenium project contributor Dave Haeffner.
In this presentation, Dave reviews the best and most useful tips & tricks from his weekly Selenium tip newsletter, Elemental Selenium. If you have unanswered Selenium questions, or want to learn how to use Selenium like a pro, check out the recording and slide deck as Dave covers topics such as:
- Headless test execution
- Testing HTTP status codes
- Blacklisting third-party content
- Load testing
- Broken image checking
- Testing “forgot password”
- Working with A/B testing
- File downloads
- Additional debugging output
- Visual testing & cross-browser testing
Want to learn more about Selenium? Download Dave’s Selenium Bootcamp for a comprehensive getting started guide.
Access the recording HERE and view the slides below:
May 25th, 2016 by Joe Alfaro
In my last blog post, I described the first step on our journey from Engineering to DevOps, which was the formation of project-focused SCRUM teams. SCRUM brings many opportunities for improving the development process, but it’s wise to keep in mind the old saying “SCRUM doesn’t fix problems, it points them out.” This means that the very first thing to emerge from SCRUM is transparency, because it requires us to examine how our teams and processes actually function on a day-to-day basis, and through ceremonies like stand ups and retrospectives, we are asked to clarify our goals and purposes to our colleagues, our customers, and ourselves.
The essence of SCRUM ceremonies is communication, and communication leads to transparency. In standups, making a statement about what you plan to do that day, and what is blocking you, provides a simple way to bring transparency about your work to your team. But it also forces you to be introspective, to be clear to yourself about what you are doing, what the blockers and issues are, and what it is that you can accomplish. More than anything else, stand ups are opportunities for reflective communication that surfaces problems at the same that it seeks to resolve them and move the entire team closer to their goal. The same can be said of retrospectives, but here the emphasis shifts from internal to external communication. From the internal perspective, retrospectives are useful for documenting issues and how they were met, and then using that information for iterative improvement. But they are much more important for communicating to customers that we understand where our challenges are, and that we have ways to deal with them. Read the rest of this entry »
May 24th, 2016 by Ken Drachnik
The Sauce Labs Ecosystem & Integrations team is proud to announce our latest ecosystem integration: Sauce Labs for Atlassian Bitbucket Pipelines. Bitbucket Pipelines is a continuous delivery service built right within Bitbucket Cloud that gives developers end-to-end visibility from coding to deployment.
As more and more devs work in agile teams, they increasingly rely on their code repos to manage code, threads and bug fixes and many use Bitbucket. As a code collaboration tool, Bitbucket is an amazing tool for managing code across large teams.
With Sauce Labs and Bitbucket Pipelines, it is easy to launch your automated Selenium and Appium tests as part of your Bitbucket Pipeline build process. Sauce Labs allows users to reduce their overall build time to as low as a couple minutes through cloud based test execution and massive parallelization. You can also leverage the over 700 browser and OS combinations including real mobile devices through Sauce Labs for Bitbucket Pipelines.
Bitbucket Pipelines is currently in Beta. To enable Bitbucket Pipelines visit Bitbucket Pipelines Integrations. You can learn more about the Sauce Labs integration on our documentation wiki.
Also, visit the Atlassian Marketplace to see additional Sauce integrations available for JIRA and Bamboo.
May 23rd, 2016 by Chris Riley
I’ve yet to see two development environments that are alike. But even if there is no cookie cutter approach to software delivery, there are standard approaches, and methodologies that are consistent throughout modern software development and that frame nearly all environments.
Because there is a big move in software testing to go from purely manual testing (a non-technical process) to a fully automated deeply technical one, how QA processes are set up, and how it fits into the overall delivery chain is very important. Let’s take a look at the two most common architectures for test automation, and why they may or may not be the best approach. Read the rest of this entry »
May 19th, 2016 by Michael Churchman
Is your test environment secure? Do you know who has access to your test data, your source code, your design specifications?
There was a time, back in the days of stand-alone test systems and networks that were strictly local-area, when those questions would have been easy to answer. A co-worker or two might have been looking over your shoulder, but that would have been about it.
These days, however, applications are exposed to the public web, and such questions can have serious implications for your software’s security and your company’s bottom line. Software and IT companies may still have physical locations, but much of the development and testing is done off-site, by employees, contractors, and services that transfer data over the Internet, such as cloud-based testing solutions. That is why picking one who cares about your application security is important. Lets look at the risks, then at what a good solution looks like. Read the rest of this entry »
May 17th, 2016 by Hemant Jain
Continuous integration (CI) has emerged as one of the most efficient ways to develop code. But testing has not always been a major part of the CI conversation.
In some respects, that’s not surprising. Traditionally, CI has been all about speeding up the coding, building, and release process. Instead of having each programmer write code separately, integrate it manually, and then wait until the next daily or weekly build to see if the changes broke anything, CI lets developers code and compile on a virtually continuous basis. It also means developers and admins can work together seamlessly, since the programming and build processes are always in sync.
Unfortunately, the quality assurance team does not necessarily reap the same benefits. While CI assures that your app keeps building successfully as the code is continually updated, it doesn’t automatically test how new builds behave within different types of environments. An otherwise well-run CI operation might require app testing to be done separately, on a non-continuous basis, instead of building it into the rest of the process.
This poses real problems for an organization. Unless you add automated testing to your CI mix, you could end up with an app that users can download and install properly, but which suffers from critical usability issues in certain browsers or operating systems. Arguably, an app that installs successfully but frustrates users due to lack of testing is worse than one that doesn’t install at all. Read the rest of this entry »
May 13th, 2016 by Bill McGee
Thanks to everyone who joined us for our recent webinar, “Practical Tips on How to Transition from Traditional to Modern Testing Practices”, featuring DevOps analyst Chris Riley and test engineering experts Ashley Hunsberger and Greg Sypolt.
Chris, Ashley and Greg discussed the benefits of automated testing — accelerated delivery, improved quality, and reduced costs — and the transformation required of all organizations moving from manual testing to automated testing. They also addressed the following questions:
- How do you build an automation strategy from the bottom up?
- How do you begin to introduce automated testing to your organization?
- What do you do when things go wrong?
- How do you measure success?
- What are the types of tools you should have in your tool chain?
Want to learn more about automated testing and Continuous Integration? Download our free report, “How to Get the Most out of Your CI/CD Workflow Using Automated Testing”.
Access the recording HERE and view the slides below:
May 12th, 2016 by Greg Sypolt
When learning about the ability to capture network traffic by using my existing Selenium scripts or the headless test framework – PhantomJS scripts, I was excited. A whole new set of tests is about to be added to the continuous integration (CI) pipeline. We often come across requirements when we need to capture and analyze browser network traffic in real time to find HTTP status of the page, examine the headers, validate parameters, do performance analysis, and more. Just another testing strategy to protect the end-user experience when they are using your web application in real time.
What is network traffic?
Why do we need to inspect web application network traffic?
The inspection of network traffic paints a picture of a web page’s condition. The painting starts by going to a web page which triggers all the HTTP requests and responses that need to be collected in real time. To finish, analyze and measure activity across all identified pages of your application. Read the rest of this entry »
May 9th, 2016 by Chris Riley
Faster, more frequent releases at a higher quality. That is all DevOps is. That’s not hard to understand. What is hard to accept, however, is how much organizations are neglecting the latter part of this equation. Not only does a lack of focus on quality slow down releases in the long term, it does not fit with the overall goal of DevOps.
DevOps for existing development organizations is hard to implement. Entrenched development shops not only do not have the option to stop everything and start over, they are also slipstreaming new processes and technologies into an existing process, and an already-established delivery pipeline. I have seen many organizations for which the transition has worked out great, and other times where it has fallen flat. But I’ve very rarely seen an environment where QA drives change. Read the rest of this entry »
May 3rd, 2016 by Ken Drachnik
As more and more devs work in agile teams, they need tools to plan, track, and release software and many of them use JIRA. As a tracking tool, JIRA is amazing for collaboration and project planning. For many teams, JIRA is the place of record for everything in the software development lifecycle. We have found that many of our customers use JIRA and the #1 product ask was to integrate Sauce Labs’ test results with JIRA so it would be simple to track all the tests associated with a project in one place.
Let’s say you are running an automated or manual test on Sauce Labs and find a bug. You want to add it to JIRA so that someone on your team can take a look or so that it can be prioritized in the backlog. Historically, one would have to download all the Sauce assets, login to JIRA, create a ticket, and upload the assets again. This can be tedious when you’re running lots of tests.
With Sauce Labs for JIRA, this is all simplified and automated. With the click of a button you can now create a JIRA ticket directly from your Test Details page. The plugin gives you the option to upload the screenshots, logs, and video link to your tests, making it easy to share out among your team.
To download Sauce Labs for JIRA, visit the Atlassian Marketplace: https://marketplace.atlassian.com/plugins/sauce-jira-integration/cloud/overview. To read more, visit our JIRA integration Docs page.
The Sauce Labs Ecosystems & Integrations Team