October 2017 Summaries

The use of open source testing tools has revolutionized the world of software quality assurance (QA) over the past decade. These tools, such as Selenium, Appium, JMeter, JUnit, Robotium, and Selendroid, have gained widespread adoption due to their community support, flexibility, and customization options. The most notable advantages of open source testing tools are that they offer no vendor lock-in, making it easier for organizations to adapt to changing technological landscapes, are customizable and extensible to suit individual needs, and work on multiple platforms and languages, catering to diverse teams and applications. With their large user bases and extensive documentation, these tools provide a robust foundation for software testing, driving innovation and maturity in the industry.

The Testing Buffet: Or, Why You Need Multiple Testing Framework Options` is an article that emphasizes the importance of having multiple testing frameworks at your disposal for effective software testing and quality assurance. Having multiple options allows for flexibility, agility, and scalability in testing workflows, enabling teams to optimize their results, use their team's expertise more effectively, and ensure forward compatibility with changing project requirements. The analogy of a buffet is used to illustrate the benefits of having multiple testing frameworks, highlighting that just as a buffet provides flexibility and agility in dining choices, an automated testing platform supporting multiple frameworks allows for similar flexibility in software testing.

The "shift left" concept in software development involves moving processes to an earlier point in the delivery pipeline to make them more effective and easier to manage, saving time on the backend of the development lifecycle. This approach has already transformed QA operations with shift left testing, which can now be applied to security teams as well. By shifting security operations to the left, DevOps organizations can benefit from early detection of bugs and security issues, reducing risk and uncertainty. Continuous integration can aid in security by maintaining a secure environment for testing and deployment. This approach can help build high-quality, secure applications quickly, making the development lifecycle safer and faster.

Effective testing involves collaboration and organization between QA professionals, test automation, test case management, and other tools. However, silo-ed systems can lead to communication woes, where teams use different tools for defect tracking, test case management, and issue logging, resulting in wasted time on manual labor. Collaborations between tools eliminate this waste by integrating with one another, allowing everyone to work where they're most comfortable without duplication of effort. Integrations such as Sauce Labs with JIRA, HipChat, and Slack enable seamless communication between QA and developers, solving the adversarial workflow between teams. By leveraging these integrations, organizations can take advantage of the potential for automation and efficiency in their testing efforts.

Open standards have streamlined browser testing by providing a common framework for browsers to follow, but they do not guarantee full browser standardization or compatibility. The implementation of open standards can vary between browsers and operating systems, making it impossible to rely on successful tests in one browser to ensure compatibility with all standards-compliant browsers. Browser vendors have significant motivation to add enhancements of their own, which can lead to non-standard features that may not be compatible with other browsers, even if they are fully compliant with existing open standards. To maintain full browser compatibility, developers need to use triage-based testing strategies, automate and test in parallel, keep it simple, establish a backwards-compatibility policy, avoid single-platform features, and stay alert to changes in browsers and operating systems.

Extended Debugging provides additional information to help users debug Selenium tests by providing JS Console log and networking logs with each automated test. It helps users understand app issues and pinpoint the root cause of test failure, giving insights into browser and networking issues that can aid in quickly identifying the root causes of test failures. This feature is now available in general availability (GA) on the Sauce Labs platform.

To implement effective Continuous Delivery and Integration (CI-CD) in a system's architecture, organizations must adopt fast management of environments, self-service for teams, and scriptable databases to streamline build, testing, and deployment processes. This enables faster delivery of high-quality software with reduced manual intervention. Feature management is also crucial, allowing teams to design systems that can toggle features on or off for better testability and scalability. Moving to a pipeline that constantly delivers well-tested software requires significant effort from organizations, including process and policy changes across the entire organization. Leveraging APIs for testability, managing code dependencies through injection, and organizing test and system code in a repository are also essential for achieving a smooth CI/CD experience.