First Orion releases 40% faster with Sauce Labs aura's Real Device Cloud. Sauce Labs announced that branded communications innovator First Orion has leveraged Sauce Labs to transform its physical device testing processes. First Orion replaced its manual, device-heavy testing infrastructure with Sauce Labs' programmable Real Device Cloud, accelerating telecom and mobile release cycles by up to 40% while freeing up 35% of engineering and QA capacity. "Sauce Labs has become more than a testing provider for First Orion. They're a strategic partner and an increasingly important part of how we think about our product strategy," said Mark Himelfarb, Chief Technology Officer, First Orion. "The Real Device Cloud gives us the flexibility to build the custom workflows demanded by a unique telecommunications environment, creating a foundation that will help us innovate going forward." First Orion employed Real Device Cloud to move beyond a fragmented, manually managed fleet of test devices to a fully programmable, real-device testing layer. Sauce Labs provided First Orion with complete market-matrix device breadth - combining broad OS and OEM coverage with the deep API control needed for complex telecom validation. As a result, the company was able to achieve: * 20% baseline improvement in release-cycle time across products, rising to as much as 40% for telecom solutions and mobile apps. * 35% of combined engineering and QA capacity reclaimed, giving those teams more time for product development, architecture, test design and quality analysis. * More than 10% savings on physical-device spending alone. "As software delivery accelerates to AI speed, traditional testing approaches and infrastructure become a massive bottleneck, especially in complex environments such as telecom," said Prince Kohli, CEO of Sauce Labs. "First Orion's results prove that an AI-native code release assurance foundation is key to scaling modern mobile app releases." Sauce Labs helps First Orion to smoothly scale testing as business grows First Orion provides scam protection and branded communications technology for wireless carriers, businesses, and their customers. Before using Sauce Labs, managing physical device fleets across distributed teams consumed up to 10% of engineering bandwidth in setup time alone while creating test environment inconsistencies. First Orion leveraged Sauce Labs Real Device Cloud, accessing a global fleet of public and private real devices with genuine device diversity across Apple, Google, and other OEM hardware - to expand device coverage and build custom tooling. The team achieved screen mirroring, streaming logs, and maintaining persistent connections for long-running communications tests without hardware maintenance. This API-level control enabled the company to support specialized telecom workflows impossible on conventional testing portals, turning Sauce Labs into underlying infrastructure for product development rather than just a testing service. "We looked at other vendors but found their programmatic capabilities too limited, particularly with moving data in and out, managing traffic, and emulating different conditions," said Himelfarb. "Sauce Labs stood out because it could give First Orion access to real devices with live SIM cards on U.S. carriers while also providing the level of control the company needed through its API." Programmability provides foundation to ramp up AI adoption Real Device Cloud is also giving First Orion a foundation for bringing AI more directly into how it builds releases. By making real-device telemetry, logs, network signals and test results more accessible, First Orion can feed AI models the rich, real-world context they need to identify patterns, diagnose failures, surface insights and automate decisions that would otherwise require manual engineering review. This will allow AI-driven development tools to interact more directly with the testing environment, using device data to inform changes, validate new functionality across devices and operating systems, and provide developers with faster feedback as they build. David Marshall is the founder of VMblog.com, one of the industry's longest-running independent publications covering modern data center technologies. What began as a focus on virtualization and cloud computing has expanded to cover the full spectrum of enterprise IT, including AI, security, and DevOps, making VMblog a trusted destination for vendor news, technology analysis, and industry commentary.Beyond publishing, David has spent his career at the intersection of technology and business, inventing, marketing, and launching a number of successful software companies and products, and building a reputation as a skilled marketing executive in the enterprise IT space.David is also a published author, having written two well-regarded books on virtualization and served as technical editor for two "For Dummies" titles covering virtualization and cloud computing. He co-founded CloudCow.com, a publication focused on cloud computing, and has been named a VMware vExpert every year since 2009, one of the longest continuous honoree streaks in the program's history.Connect with David on LinkedIn: https://www.linkedin.com/in/davidmarshall/

Sauce Labs has introduced bring-your-own-model capabilities to its AURA platform, allowing enterprise customers to choose their preferred large language models for software quality assurance. The feature enables organisations to use open-source, open-weight, or proprietary LLMs whilst maintaining a consistent release assurance system. AURA's architecture separates the model layer from Sauce Labs' release assurance intelligence, letting customers change models as technology or regulations evolve. The platform connects business intent to production confidence by authoring, executing, analysing, and self-healing tests at AI speed. According to the company, enterprises using AURA achieve 90% fewer production incidents and 47% faster release cycles, with 38% of engineering capacity reclaimed. The platform is informed by over 8.7 billion test executions and supports 300,000 enterprise users.

Cross Browser Testing Best Practices every QA team should follow. What Is Cross Browser Testing and Why Is It Important? Web applications are accessed through different browsers, operating systems, devices, and browser versions. As a result, an application that works correctly in one browser may display differently or behave unexpectedly in another. Cross Browser Testing helps QA teams identify these compatibility issues by validating application functionality, layout, navigation, and user interactions across multiple browser environments. A consistent experience across supported browsers is important for maintaining application quality and avoiding browser-specific issues that can affect usability. An effective testing approach considers the browsers and versions most relevant to the application's users and business requirements. QARA enterprise supports functional UI test automation, helping QA teams automate repeatable test scenarios and improve testing coverage. This guide explores practical Cross Browser Testing Best Practices that can help organizations identify compatibility issues earlier and deliver more consistent web application experiences. How Do Browser Compatibility Testing and UI Testing Improve Web Application Quality? Web applications can behave differently across browsers due to variations in rendering engines, browser versions, operating systems, and supported web technologies. Browser Compatibility Testing helps QA teams verify that an application's functionality, layout, navigation, and interactive elements work as expected across the browsers included in the testing scope. Identifying these differences early can help prevent browser-specific issues from reaching end users. UI Testing is another important part of cross-browser validation. It focuses on checking whether elements such as menus, forms, buttons, images, text, and page layouts are displayed and behave correctly across different browser environments. Even when the underlying functionality works, differences in rendering can affect how users interact with an application. Combining Browser Compatibility Testing with UI Testing allows QA teams to evaluate both functional behaviour and visual consistency across supported browsers. With QARA, teams can automate functional UI test scenarios and execute repeatable tests, helping improve coverage and identify compatibility issues more efficiently. How Do Chrome Testing, Firefox Testing, and Edge Testing Improve Browser Coverage? Web applications may display or behave differently across browsers because of differences in rendering, browser versions, operating systems, and supported web technologies. Chrome Testing and Firefox Testing help QA teams validate application functionality and user interface behaviour across widely used browser environments. Testing across multiple browsers can reveal rendering differences, interaction issues, and compatibility problems that may not be visible when an application is tested on only one browser. Edge Testing can also be included in the browser testing scope when it is part of an organization's supported browser environment. Teams should define their browser matrix based on their target users and business requirements and then validate important workflows, forms, navigation, page layouts, and interactive elements across those environments. QARA supports multi-browser and multi-platform testing, helping QA teams automate functional UI test scenarios across different browser environments. QARA also supports integrations with platforms such as BrowserStack and Sauce Labs, allowing teams to extend their browser and device testing coverage. This approach can help identify compatibility issues earlier and provide greater confidence in consistent web application behaviour across supported browsers. What Are QARA Test Cross Browser Testing Best Practices? Following effective cross-browser testing practices helps QA teams identify browser-specific issues before they affect users. A structured approach should consider the browsers, versions, operating systems, and application workflows that are most relevant to the target audience rather than attempting to test every possible environment. QARA Enterprise Cross Browser Testing Best Practices include: * Define a browser testing matrix: Identify the browsers, versions, operating systems, and environments that require testing based on user and business requirements. * Prioritize critical workflows: Focus on essential functions such as login, registration, forms, navigation, transactions, and other high-priority user journeys. * Validate UI consistency: Check layouts, buttons, menus, images, fonts, and interactive elements across supported browsers. * Automate repetitive scenarios: Use functional UI automation for repeatable test cases to improve consistency and reduce repetitive testing effort. * Test after application changes: Re-run relevant browser test scenarios after updates to identify compatibility regressions. * Use broader browser environments when required: Integrate with platforms such as BrowserStack or Sauce Labs to extend browser and device coverage. * Track browser-specific issues: Document recurring compatibility problems and use test results to improve future testing cycles. QARA's multi-browser and multi-platform testing capabilities can help QA teams execute repeatable functional UI tests across supported environments. By combining appropriate browser coverage with automation and structured testing practices, organizations can identify compatibility issues earlier and deliver more consistent web application experiences. Key Takeaways on Cross Browser Testing Best Practices Cross Browser Testing is an important part of delivering consistent and reliable web applications across different browsers and environments. From Browser Compatibility Testing and UI Testing to Chrome, Firefox, and other supported browser environments, a structured testing approach helps QA teams identify rendering differences, functional issues, and compatibility gaps before they affect users. With QARA, organizations can support multi-browser and multi-platform testing while automating functional UI test scenarios across supported environments. By defining the right browser testing matrix, prioritizing critical workflows, validating UI consistency, and automating repeatable scenarios, QA teams can improve test coverage, identify compatibility issues earlier, and build greater confidence in application releases. Ready to strengthen your cross-browser testing process? Start your free trial of QARA today and explore a more efficient approach to functional UI test automation. In its next blog, The Digital Group'll explore Software Testing Metrics and examine the key metrics QA teams can use to measure testing effectiveness, track quality, identify improvement areas, and make more informed software testing decisions. Key Questions About Cross Browser Testing What is Cross Browser Testing? Cross Browser Testing is the process of checking whether a web application functions and displays correctly across different browsers, browser versions, operating systems, and supported environments. Why is Cross Browser Testing important? Yes, absolutely. It helps identify browser-specific functionality, rendering, navigation, and UI issues that may not appear when an application is tested on only one browser. What is Browser Compatibility Testing? Browser Compatibility Testing verifies that an application's features and interface work as expected across the browsers and environments included in the testing scope. How does UI Testing support Cross Browser Testing? Yes, it plays an important role. UI Testing helps verify that elements such as forms, buttons, menus, images, fonts, and page layouts remain functional and consistent across supported browsers. Should organizations test applications on Chrome, Firefox, and Edge? Yes, when these browsers are part of the target user environment. Organizations should define their browser testing matrix based on their users, application requirements, and supported browser environments. Can Cross Browser Testing be automated? Yes, absolutely. Automated functional UI testing can help QA teams repeatedly execute test scenarios across supported browser environments, reducing repetitive manual effort and improving testing consistency. What are the best practices for Cross Browser Testing? Key practices include defining a browser testing matrix, prioritizing critical workflows, checking UI consistency, automating repetitive scenarios, testing after application changes, and tracking browser-specific issues. Can QARA support Cross Browser Testing? Yes. QARA supports multi-browser and multi-platform testing and functional UI test automation. It also supports integrations with platforms such as BrowserStack and Sauce Labs to help extend browser and device testing coverage. How can QARA improve Cross Browser Testing? QARA can help QA teams automate repeatable functional UI test scenarios across supported environments, improve test coverage, and identify browser compatibility issues earlier in the testing process.