Introduction
Škoda Auto, a major global car manufacturer and part of the VW Group, recognizes that in the modern automotive landscape, the quality of digital products is as crucial as the vehicle’s mechanical engineering. Jan Krcmar and his team in the Smart Quality department are responsible for User Acceptance Testing (UAT), serving as the final quality gatekeepers before digital products reach the customer. The stakes are incredibly high; unlike typical mobile apps, in-car systems demand near-perfect reliability from day one.
A bottleneck of physical devices and late-stage testing
Before integrating BrowserStack, Škoda’s testing process was constrained by several critical challenges that impacted both speed and quality:
- Physical device management: The team managed a limited pool of about 15 physical iOS and Android devices. This created significant overhead in keeping them charged, updated, and correctly configured with various OS versions to reflect their customer base.
- Time-consuming bug verification: The single biggest bottleneck was retesting bugs on different versions of an application. To check a fix on an upcoming build or verify a bug on a previous version, testers had to manually delete the existing app, install the new one, log in, and set up test data. Jan described this as “very time consuming” and “the most difficult to deal with.”
- Delayed bug discovery: The team’s UAT process was limited to testing only the final iteration of an app before its scheduled release. This meant critical bugs were often found at the last minute, forcing a halt to the release, a new development cycle to fix the issues, and a complete restart of the testing process. This led to irregular, delayed releases and significant time pressure.
- Inadequate device coverage: With a small number of in-house devices, the team “couldn’t cover the whole palette of the devices” their customers were actually using, creating gaps in test coverage.