November 2022 Summaries

Sauce Labs has announced several updates and news for November 2022, including the release of iOS 16.1 on simulators and real devices, a new community fellowship program to foster diversity in open source communities, improved support for Chrome, Edge, and Firefox browsers, and enhancements to the Platform Configurator and saucectl test automation framework. Additionally, Sauce Labs has deprecated the containerized headless US-East environment and introduced new features such as Playwright support in Failure Analysis, a patch version of Sauce Connect Proxy, and take screenshots with Espresso. The company also highlighted its commitment to building solutions that equip developers with digital confidence in the rapidly evolving world of software development.

Sauce Labs has launched its first Community Fellowship Program, designed to foster diversity and belonging in the open source community. The program provides paid training for six months and aims to help break down barriers in technology. It welcomes new fellows who will work on Elemental Selenium, a worthwhile open source project, and is supported by Sauce Labs' commitment to nurturing and contributing to the community from which it was created. The program offers a real-world model of improving diversity in open source governance models and provides fellows with opportunities to learn the fundamentals of code, content, design, quality, and community.

Responsive website design is an approach that prioritizes making sure the content users see within a software application looks good at every possible screen resolution. It allows teams to ensure a great user experience across a wide range of screen sizes and configurations by automatically adjusting content displays depending on the screen size of the device on which the software operates. Unlike adaptive design, responsive design doesn't create different versions of an application or website for each screen resolution, but instead designs applications to adjust content automatically to fit different screen sizes. This approach offers advantages in simplicity and flexibility, as teams only need to create and test one version of a website or application, relying on it to respond automatically to various screen sizes. Responsive design is crucial for building any type of application or website, especially mobile apps and websites that need to support both desktop and mobile users, ensuring users have a positive experience on whichever device or screen configuration they use. It also goes hand-in-hand with mobile-first design, which involves designing for mobile devices first and then adapting them to support desktop computers if needed. By adopting responsive design and testing strategies, teams can deliver great user experiences across many device configurations and display sizes, making it a smart means of building applications today.

Inspecting elements on an iPhone is crucial for testing and troubleshooting web and mobile UI issues. This can be achieved through various methods such as using Safari developer tools or Sauce Labs, both of which allow developers to view and edit a website's source code, including HTML, CSS, and JavaScript, to identify and debug issues. To inspect elements on an iPhone with Safari developer tools, one needs to set up their device and computer by enabling web inspector for the Safari app, turning on the developer menu on a Mac, connecting both devices via a USB cable, and then accessing the Web Inspector window, which displays all the elements that can be inspected. Similarly, using Sauce Labs requires logging in to an account, selecting the iOS device to test on, navigating to the hidden dock area, opening Safari, restarting the simulator, and accessing the Web Inspector window. Additionally, Apple's web inspector feature is available for testing, but it comes with limitations such as requiring multiple devices and maintaining them, which can be time-consuming and expensive.

In the United States, Thanksgiving marks the unofficial start of the holiday season and is a stressful day for many systems engineers as they prepare for Black Friday and Cyber Monday. Uptime is crucial during these events, but even 99.99% uptime can be disastrous if it occurs at the worst moment. The potential fiscal impact of being down an hour is significant, with $417 million lost per minute and $7 million lost per second. To avoid a disaster, developers and SREs must invest in performance testing and API load testing to ensure their systems can handle unpredictable traffic spikes and patterns. Security testing is also essential as hackers will exploit vulnerabilities during outages. Chaos testing or failover testing can help minimize the damage of a potential outage by designing the system to fail predictably. Better planning and synchronicity among QA teams can also prevent disasters, but it's often too late once the issue arises.

Selenium Manager is a new tool developed to simplify environment setup for anyone running Selenium tests. It was created to address the frustration of configuring browser drivers, especially with the shortened release cycles of Chrome, Firefox, and Edge browsers. With Selenium Manager, users can easily configure their environment without having to manually download and install drivers. The tool has been built using lessons learned from WebDriverManager and is now part of the official Selenium project. It provides a robust mechanism for detecting browser versions, downloading drivers, and making them available for Selenium WebDriver. Selenium Manager is still in development, but it aims to improve the user experience by reducing the time needed to run tests and simplifying environment configuration. The tool is now included with each official Selenium binding, so users can easily get started with Selenium Manager by updating their project to release 4.6.0.

The Eras Tour by Taylor Swift broke records and highlighted the importance of software testing in ultra-high-volume ticket sales. Performance testing is crucial to handle large bursts of traffic, security testing prevents attacks on vulnerable systems, and chaos testing ensures that systems can withstand unexpected events. A converged approach to these disciplines is necessary to mitigate risks and ensure reliability. Effective collaboration between teams is essential to address the complexities of these issues, requiring strong executive leadership and a deep understanding of the blast radius of failures.

Building a top-rated mobile app requires addressing user frustrations through effective error monitoring and reporting. With the rise of app store optimization, ratings matter more than ever, as consumers increasingly look at flagged issues in ratings to gauge an app's quality. One in five users won't wait for errors to be fixed, and 25% have written negative reviews after a bad digital experience. To keep bad reviews from affecting new user adoption, developers must identify and fix functional errors across the development lifecycle of their app. This includes implementing error monitoring and crash reporting tools that can streamline both development and deployment. By reducing mean time to detect (MTTD) and mean time to resolution (MTTR), teams can improve the reliability and competitiveness of their app, allowing them to focus resources on the most important issues. Effective error monitoring and reporting tools, such as those provided by Sauce Labs and Backtrace, enable teams to capture, prioritize, and quickly resolve application errors, reducing MTTD and MTTR by up to 90% and 50%, respectively.

### Appium vs Espresso for Mobile App Testing Appium and Espresso are two popular tools for mobile app testing, each with its own strengths and weaknesses. While both can be used for Android app testing, Espresso is designed specifically for functional testing of Android applications, whereas Appium can test both Android and iOS applications. Appium offers more flexibility in terms of language independence and client/server architecture, but at the cost of slower tests due to an additional layer between automation code and device. On the other hand, Espresso provides a comprehensive framework with automatic synchronization of the UI, intuitive development, and easy maintenance. However, it is only compatible with Java and Kotlin languages and can only be used for Android app testing. Ultimately, the choice between Appium and Espresso depends on the scope of the testing, with Espresso suitable for developers building native Android applications and Appium better suited for teams requiring cross-platform support and validation across multiple platforms.

The TestNG DataProvider feature allows users to pass parameters into a test method, enabling the reuse of code and reduction in testing time. By using a DataProvider, testers can create multiple test cases from a single test method, reducing redundancy and improving test efficiency. This feature is particularly useful for scenarios with large numbers of permutations and combinations to test. The TestNG DataProvider can be used to pass strings or more complex parameters into a test method, allowing users to iterate over different data sets without having to write separate code for each scenario. Additionally, the DataProvider can be used in conjunction with other features such as parallel execution and reporting to further improve testing efficiency.

Most web traffic today is driven by API calls between web applications and RESTful APIs. A RESTful API allows endpoints to integrate with each other in accordance with business logic built into the API, enabling microservices to work together like a traditional monolithic application. REST stands for Representational State Transfer, defined by 6 constraints: client-server, stateless, cacheable, layered system, uniform interface, and code on demand. A RESTful API defines a set of functions that developers can perform requests and receive responses via HTTP protocol such as GET, DELETE, and POST. Resources can be called upon singularly, making it possible for mobile apps to continue providing expected functionality while select components are being edited or improved. The use of RESTful APIs has become essential in today's apps and games that provide top customer experience by employing short release cycles and microservices powered by REST APIs to maintain high levels of code reliability, resilience, and efficiency throughout iterative changes.

To create a winning mobile testing strategy, it's essential to understand the challenges of mobile app testing, including device fragmentation, screen size and OS fragmentation, localization, and different types of mobile apps. A mix of real devices and virtual devices (Android emulators and iOS simulators) should be used as part of the mobile testing strategy. There are three main points of focus for mobile application testing: functional testing, hardware device testing, and attribute testing. An integrated approach that incorporates both manual and automated tests is recommended, with automation covering 80% of test cases and manual testing covering the remaining 20%. Mobile beta testing allows teams to validate applications with real users in real-world environments, while choosing the right automated testing framework is crucial for effective and efficient testing. Finally, considering cloud-based real devices or in-house mobile testing options can help scale and automate testing efforts.

The original test automation pyramid, created by Mike Cohn, prioritizes unit testing at the base, followed by API or integration testing, and then UI testing. In contrast, the modern mobile test automation pyramid 2.0 considers not only specific testing needs of different personas but also scaling mobile test automation and actual user use cases. The new pyramid consists of four layers: desktop browser testing for system testing and responsive design, emulator and simulator testing for functional flow and native integrations, real device testing for usability and visual components, and a bonus layer that includes running mobile beta tests on real devices to collect real-time user feedback and meaningful bug reports. This revised approach aims to remove bottlenecks and inject quality at every stage of the software development lifecycle (SDLC).