How a Logistics Tech Company Brought Zebra Scanner Testing Into the Automated CI/CD Pipeline with AstroFarm

How a Logistics Tech Company Brought Zebra Scanner Testing Into the Automated CI/CD Pipeline with AstroFarm

A logistics tech company closed the one gap that had blocked every release cycle for a year — barcode-scan testing on Zebra rugged handhelds — by routing scans through AstroFarm's Zebra scanner test automation and remote device sessions.
Business Overview
This case study focuses on a logistics technology company whose app runs almost entirely on Zebra rugged handhelds. Inbound scanning, pick confirmation, pallet tagging, and route handoffs are not edge cases in this product — they are the product. The QA team had grown distributed across cities, with a few contractors overseas, and most of the app tested fine remotely. The one thing that did not was anything triggered by a physical barcode scan.
At a Glance
Scan-driven test cases went from mostly manual to fully automated in a single sprint, and barcode workflows made it into the nightly CI/CD run for the first time — by injecting scans into live remote sessions instead of needing someone physically holding a Zebra device.
The Challenge
The QA lead had a recurring problem every release cycle. Most of the app tested fine remotely — UI flows, checkout logic, sync behavior. The moment a test case hit a barcode scan, there was no remote path at all:
  • Scan-driven logic was unreachable without a device in hand. Inbound scanning, pick confirmation, pallet tagging, and route handoffs all depended on a physical scan event. There was no way to trigger one remotely, so someone had to be physically on-site with the device to run those scenarios.
  • The Appium suite couldn't simulate a scan. Scan-dependent steps were either stubbed out of the automated suite or left as manual checklist items running once a sprint instead of every night. The part of the app customers depended on most was the part the team had the least automated confidence in.
  • Distributed testers, including overseas contractors, were locked out of scan scenarios. Even when the rest of the app was testable from anywhere, scan-driven cases required on-site hardware — which meant remote contributors couldn't run the same tests as someone sitting next to a physical device.
  • On-site hardware was a daily bottleneck. The same devices that had to be reserved for routine regression were also needed for new device evaluation and hardware-specific edge cases, and the two kept competing for the same hardware.
As the company pushed toward a multi-region launch, the gap stood out clearly: scan logic is the reason this product exists, and it was the least verified part of the release.
The Solution
Searching for a way to close the gap, the team found AstroFarm — the only testing solution they evaluated that offered Zebra scanner test automation at all. Every other platform could handle general remote device interaction, but none had a way to simulate a physical barcode scan.

Barcode library in AstroFarm: The team uploaded their standard barcode set — package labels, pallet tags, route QR codes — into AstroFarm's media library so the same set could be reused across test cycles.

One-click injection into live sessions: Injecting a barcode into a running session took a single click — pick the app in the foreground, select the barcode, and the target app received it exactly as it would from a physical scan.

What changed operationally:

  • Appium scripts rebuilt around injection. Scan steps that had been stubbed out for months were rewritten to trigger barcode injections programmatically, turning a manual checklist item into a scheduled part of the automated suite.
  • Nightly CI/CD coverage for scan workflows. For the first time, barcode workflows ran as a standard step in the nightly build — a year-long goal that had never felt achievable without hardware in every tester's hands.
  • Live physical scanning kept for exploration. Real device scanning stayed available for exploratory testing and edge cases. For regression, injection became the default.
  • Same scan scenarios for remote and on-site testers. Contractors overseas and testers in other cities ran the exact same scan-driven cases as someone sitting next to a physical device.
  • On-site hardware freed for what actually needs it. New device evaluation and hardware-specific edge cases got the device time they needed, without competing against routine regression runs.
Results
  • Scan-driven test cases went from mostly manual to fully automated in a single sprint. Scan steps that used to require a person and a device now run unattended.
  • Barcode workflows reached the nightly CI/CD run for the first time. A year-long goal that had never felt achievable without hardware in every tester's hands.
  • Remote and overseas testers ran the same scan scenarios as on-site testers. No more special-case handling for distributed contributors.
  • On-site hardware freed for testing that actually needs it. New device evaluation and hardware-specific edge cases no longer compete with routine regression for device time.
Why It Matters
For a logistics app, scan logic isn't a feature among many — it's the reason the product exists. Testing it manually, or not at all, meant the most business-critical part of the app was also the least verified. AstroFarm closed that gap by treating a barcode scan like any other automatable event: something that can be injected on demand, scripted into Appium, and run on the same schedule as the rest of the regression suite.
Try AstroFarm
Ready to bring your scan-driven workflows into automated testing? Turn barcode scans into a scheduled part of your regression suite, runnable from anywhere — no device in hand required. Try AstroFarm Free →