Introduction
Schneider Electric is a global leader in energy management and industrial automation, serving businesses and industries across the world with software, hardware, and connected systems. The Customer & Innovation Lab sits at the centre of Schneider Electric’s testing and verification activities, supporting multiple lines of business across the organisation with system-level testing of mobile applications, embedded systems, and connected devices across Android and iOS platforms.
With teams distributed across geographies including India, Canada, France, and the United States, and a growing portfolio of enterprise applications that needed to run reliably on a wide range of real devices, the lab’s legacy approach of maintaining a physical device bank was reaching its limits. By adopting BrowserStack App Automate, Schneider Electric scaled device coverage by 10 times, reduced infrastructure maintenance overhead by 70%, and cut both bug reproduction time and test flakiness by 50%, while giving distributed teams around the world instant, secure access to the devices they needed.
A physical device lab that could not scale with a globally distributed team
Before BrowserStack, Schneider Electric’s Customer & Innovation Labs maintained an in-house device bank: a locked kiosk containing physical Android and iOS devices, connected via USB cables to a central hub. As the team and its testing demands grew, and as Covid made remote work the new reality, the limitations of this approach became impossible to ignore.
1. Physical device management was a constant operational burden: Maintaining the device bank meant charging devices, applying software updates, provisioning them for shared access, and ensuring they were always available and in working condition. Every device required active management, and any failure or unavailability directly blocked testing activity.
2. Distributed teams could not access shared devices: With product teams spread across India, Canada, France, and the US, sharing a physical device bank was impractical. Shipping devices to remote team members based on testing priority was both time-consuming and logistically complex, and it still left teams without devices when they needed them most.
3. Covid accelerated an already critical problem: When the pandemic forced teams to work from home, the device bank became entirely inaccessible to anyone not physically present in the lab. The challenge of how to give every team member access to the right device, regardless of where they were, became urgent overnight.
4. Limited device coverage constrained test plans and release velocity: With only ten to fifteen physical devices available, the lab could cover only a fraction of the real-world device and OS combinations that Schneider Electric’s applications needed to support. Test plans had to be scoped down to fit the available hardware, and release velocity was effectively capped by the size of the physical infrastructure.
5. iOS testing required dedicated, expensive hardware setups: Testing iOS applications required a Mac machine physically connected to an iPhone, along with careful version management and environment configuration. This created a separate, costly infrastructure requirement for every team that needed iOS coverage, and made cross-platform testing particularly burdensome.
6. Reproducing field issues on specific devices was often impossible: When field issues were reported from customers or field service engineers on specific device and OS combinations, the lab frequently did not have that exact configuration available. Reproducing the issue was either impossible or required procuring new hardware, delaying resolution and eroding confidence in the team’s ability to support Schneider Electric’s businesses in the field.