May 2016 Summaries

Dave Haeffner recently presented "Practical Tips and Tricks for Selenium Test Automation" in a webinar, covering useful tips from his weekly Selenium tip newsletter, Elemental Selenium. The presentation covered various topics such as headless test execution, testing HTTP status codes, load testing, and debugging output, among others. For those interested in learning more about Selenium, Dave's Selenium Bootcamp provides a comprehensive getting started guide that can be downloaded. The webinar recording is available for access, along with the slide deck on the Saucelabs website.

The text discusses two common architectures for test automation in software development: the siloed approach and the centralized approach. The siloed approach involves breaking down the delivery chain into isolated components, which can scale more easily but also creates barriers between teams and increases points of failure. On the other hand, the centralized approach segments the delivery chain by environments, with the greatest amount of testing happening in the integration environment, allowing for frequent testing as every developer commit. The text highlights common misconceptions about the centralized approach, such as the definition of "environment" not needing to equal a single set of servers, and emphasizes the importance of team ownership and strategy in both approaches. Ultimately, the choice between these two architectures depends on company culture, history, and technology, with no one-size-fits-all solution.

A secure online test environment is crucial to protect intellectual property, prevent competitors from gaining an unfair advantage, and maintain user privacy. Companies must ensure that their online test environment is designed with security in mind, using features such as dedicated virtual machines, secure communication protocols, no external communication channels, and on-site storage of data or artifacts is not allowed. A genuinely secure software testing service can guarantee the confidentiality and integrity of test data, but many companies may still be unaware of the risks associated with online testing or may not have implemented adequate security measures to mitigate these risks.

The Benefits of Mobile Cloud Testing` Mobile cloud testing is a solution to several problems faced by modern testers and quality assurance managers, including unreliable testing infrastructure, multiple potential testing devices, and agile development processes that require continuous testing. It addresses issues such as Android fragmentation by providing access to hundreds of devices, multiple operating systems, and various OS versions. This allows for efficient testing without the need for expensive hardware maintenance or setup. Mobile cloud testing also facilitates global collaboration among distributed teams, similar to Google Docs, with features like Jira and Github integration. Additionally, it enables automated testing in parallel on several devices simultaneously, significantly reducing testing time and shortening app release cycles.

Network traffic refers to all network requests made by a browser when loading a web page, including requests for JavaScript, CSS, and image files. Capturing network traffic provides valuable insights into the performance of a web application, allowing developers to identify potential issues before shipping to production. This can include analyzing HTTP status codes, request and response sizes, and resource loading times. By using tools like PhantomJS or BrowserMob Proxy, developers can create scripts to capture network traffic in real-time, enabling them to optimize their web applications for better performance and user experience. These scripts can also help identify issues with caching, rendering speed, and other factors that may impact the end-user experience. By incorporating network monitoring testing into their pipelines, teams can ensure a smoother transition from development to production, reducing the likelihood of errors or performance issues that may affect users.

The key to implementing DevOps successfully lies in empowering QA teams to take the lead in driving change within an organization. By leveraging their holistic view of the entire environment and automation capabilities, QA teams can identify bottlenecks, quantify technical debt, and point out areas for improvement. With greater empowerment, QA teams can recommend tools, transition to more test strategy, gain exposure to the roadmap, and shift from a reactive to proactive focus. This enables organizations to move towards DevOps without major organizational changes or reliance on special hires, and ultimately benefits from increased visibility of the QA team's influence in shaping processes and tools.

JIRA is now integrated with Sauce Labs' test results, allowing developers to easily track all tests associated with a project in one place. With the click of a button, users can create a JIRA ticket directly from their Test Details page and upload screenshots, logs, and video links to share among team members. This simplifies the tedious process of downloading assets, logging into JIRA, creating tickets, and uploading assets again. The integration is now available on the Atlassian Marketplace for easy download and setup.