Mobile Testing on Windows: What the Quash Windows App Means for QA Teams
For a long time, if your QA team ran Windows, you were working around Quash rather than with it. Browser-based access covered the basics — test case management, reports, suite configuration — but the core execution workflow, the part where Mahoraga connects to a device and actually runs a test, required a Mac.
That's no longer the case.
Why Windows Support for Mobile QA Matters More Than You'd Think
This isn't a platform checkbox. A significant portion of QA teams — particularly in enterprise environments, in markets across South and Southeast Asia, and in organisations where hardware procurement is standardised — run Windows as their primary operating system. For those teams, "local test execution requires a Mac" was, in practice, "you can't fully use the product."
The workaround options weren't good. Remote Mac access introduces latency that makes execution feedback feel slow and disconnected. Cloud-only execution removes local device testing from the equation entirely, adding cost and removing the ability to test on hardware the team controls. Neither is a substitute for a native experience on the machine a tester uses every day.
The more important issue is consistency. When execution works differently depending on operating system — or doesn't work at all on one of them — test results are harder to trust. A failure on a Windows machine means something different if the Windows execution path is a workaround rather than a first-class implementation.
Get the Mobile Testing Playbook Used by 800+ QA Teams
Discover 50+ battle-tested strategies to catch critical bugs before production and ship 5-star apps faster.
What You Can Do with the Quash Windows Desktop App
The Windows desktop app ships with full feature parity with the Mac version. No exceptions. No deferred features.
Test Studio for writing, generating, and managing test cases. Tasks for ad-hoc execution — quick single-flow runs without building a full suite. Suites for scheduled and CI-triggered runs across multiple test cases. Execution reports with AI-generated summaries, step-by-step screenshots, and full session recordings. Device management for connected Android hardware and emulators. The full Apps workspace — builds, credentials, knowledge, test data — shared across the team.
Connect an Android device or emulator via USB and Mahoraga installs automatically. The calibration, the accessibility configuration, the execution pipeline — all of it works the same way it does on Mac.
Critically: the workspace is shared. Tests created on Windows are immediately visible to teammates on Mac, and vice versa. Results from a Windows execution appear in the same reports, the same suites, and the same analytics dashboard as results from Mac. There is no Windows-specific data silo.
How Local Android Testing on Windows Actually Works
The setup path is straightforward. Download the .exe from , install on Windows 10 or 11 (64-bit, 8 GB RAM minimum), sign in to your existing workspace, and connect a device. Auto-updates are enabled — the app stays current without manual intervention.
From there, the workflow is identical to Mac. Open Test Studio, write or generate a test case, connect a device, run it. The execution report appears in the same place it always does.
For physical Android devices: plug in via USB, enable developer mode and USB debugging on the device, and the app detects it automatically. Mahoraga installs itself on first connection — no manual APK side-loading required.
For Android emulators: run your emulator as normal, and the Windows app connects to it the same way the Mac app would. The execution experience is identical.
How Does Quash Run Tests on Windows Without a Mac?
Mahoraga's execution engine runs natively on Windows. It connects to physical Android devices via ADB over USB and to Android emulators via the local ADB socket — the same mechanism the Mac app uses. The execution logic, screen reading, and report generation all work identically. The only capability not available on Windows is iOS simulator testing, which requires macOS because iOS simulators only run on Apple hardware.
What This Changes for QA Teams Operating on Windows
Immediate access. Any team member on Windows can now run local tests without routing through a Mac, a remote session, or a cloud device queue. A QA engineer on a Windows laptop at a client site can connect a physical device and run the full suite. A developer on Windows can trigger a quick task run before pushing a PR. A team that standardises on Windows hardware doesn't have to carve out Mac exceptions for QA.
Execution consistency. When execution works the same way regardless of operating system, test results are directly comparable across environments. A failure on a Windows machine is the same failure on a Mac — same device, same Mahoraga version, same report format. Cross-platform execution parity removes one variable from an already complex debugging picture.
Team workflow parity. For QA leads managing teams with mixed operating systems, this means one workflow document, one onboarding path, and no "this only works on Mac" carve-outs in runbooks.
Windows vs Mac: Is There Any Functional Difference?
For the current release, one: iOS simulator testing requires a Mac, since iOS simulators only run on macOS. Every other Quash capability — Android device testing, cloud device testing, test generation, suites, reports, CI/CD integration — works identically on Windows.
Physical Android device testing, Android emulator testing, cloud device access, Mahoraga execution, and the full workspace: all available on Windows, all behaving identically to Mac.
The Honest Conclusion
The Windows app doesn't introduce new capabilities. What it does is remove an access barrier that was real and that affected a meaningful portion of the teams who wanted to use Quash.
A testing platform that requires a specific operating system to function properly isn't really a platform — it's a partial solution. Local execution on Windows works the same way it works on Mac. That's the point. If your team has been cloud-only on Windows because local execution wasn't available, you now have the option to bring testing back to the machine.
Frequently Asked Questions
Can I run Android tests on a Windows PC with Quash? Yes. The Quash Windows desktop app (Windows 10/11, 64-bit, 8 GB RAM minimum) supports full Android test execution — physical devices via USB and Android emulators. Connect your device, open Test Studio, and run tests the same way you would on Mac.
Is the Quash Windows app the same as the Mac app? Yes, with one exception: iOS simulator testing requires macOS and is not available on the Windows app. All other features — Android testing, cloud devices, test generation, suites, reports, CI/CD — are fully available on Windows with feature parity.
Does mobile test automation work on Windows without a Mac? Yes, for Android. Quash's Mahoraga execution engine runs natively on Windows, connecting to physical Android devices via USB or Android emulators via ADB. iOS simulator testing requires Mac. Physical iOS device support is not yet available on either platform.
What are the system requirements for the Quash Windows app? Windows 10 or 11, 64-bit, minimum 8 GB RAM. Auto-updates are enabled so the app stays current after installation. Download the .exe from quashbugs.com/download.
Do test results sync between Windows and Mac in Quash? Yes. The Quash workspace is shared across all platforms. Test cases, execution reports, suites, and analytics are visible to all team members regardless of what operating system they're using.
