Android Emulator for App Testing & Development
Genymobile provides Genymotion: a powerful Android emulator for PC, Mac, and Cloud environments . Trusted by leading companies including Verizon, Tinder, Meta, and IBM, Genymotion enables developers and QA teams to test Android applications at scale with virtual device simulation, GPS, battery, and network condition testing capabilities.
You first create and validate an account, then sign in and click Launch App in the Genymotion SaaS section, then Request Trial. Choose Individual or Company/Enterprise, fill out the form, and wait for validation before the trial is activated. Individual: 60 free minutes, up to 2 simultaneous devices, and a valid personal email are required. Requests are usually processed within 5 business days.
You pay $0.60 per hour for each running instance, plus any AWS cloud platform fees. Running multiple instances multiplies that per-instance rate. Genymotion Device image For example, 5 instances running for 1 hour cost the same as 1 instance running for 5 hours, because the billing is per instance-hour. If you need a better rate for larger volumes, a Private Offer is available.
Yes, Genymotion offers online testing and test automation with Genymotion SaaS. A game controller can also be used on Android 12 or later to test how an app reacts to a gamepad. CloudBeat centralizes the execution and analysis of automated tests in DevOps environments. CloudBeat Genymotion supports automation tests, integration, regression, and CI/CD.
Yes. Genymotion SaaS runs in a GitLab CI/CD pipeline through the gmsaas command-line tool: the job installs it, authenticates with an API token, starts a virtual device and connects it to adb. Ready-made integrations are also listed for GitHub Actions, CircleCI, Bitrise, Jenkins and Detox on Integrations.
Custom pricing is available, and you should contact sales at sales@genymotion.com. The cloud pricing page lists Premium as a tailor-made plan with custom pricing and says to contact sales. It also offers annual billing and volume-oriented options on Genymotion Android Emulator in the Cloud.
Yes. Genymotion devices can be rooted dynamically, and rooted devices give you a complete view of what is happening on the machine, which can help with traffic capture and security testing. This is available only on some Android images. Mobile Testing and Development Android virtual devices in the Cloud
Genymotion SaaS supports Appium-based automation, and there is a dedicated guide for running parallel tests with Appium on Android. See the tutorial here: Parallel tests with Appium and Genymotion SaaS. If you want a Node.js setup, you typically point Appium to your Genymotion device via ADB and use the same desired capabilities you would use for an Android device.
Example of a CircleCI pipeline to run Appium tests with Genymotion SaaS Objective: Build the APK, start Genymotion Cloud devices, run Appium tests in parallel, and stop the devices. Prerequisites Genymotion Cloud account (https://cloud.genymotion.com) API credentials stored as environment variables in the CircleCI project: GMCLOUD_SAAS_EMAIL GMCLOUD_SAAS_PASSWORD Node.
Genymotion SaaS now supports arm64-only virtual Android devices, so you should create or recreate your device from a recent arm64 OS image. If your app has native code, recompile it with arm64-v8a support. What happened to x86/x86_64 devices in Genymotion SaaS? Deploy Applications How to use it Start a new virtual device from an official or custom recipe that uses an arm64 image.
The SaaS license gives you cloud access to Android virtual devices and works as a subscription, not a purchase. It is non-exclusive and non-transferable, and it lets you use the service during the license term. Main advantages Access your cloud devices from the Genymotion Desktop launcher in the CLOUD tab. No paid Genymotion Desktop license is needed to use Cloud Virtual Devices.
These are the most-asked questions. For all 203 Q&As with complete answers, see llms-full.txt.
Step-by-step CLI guides that AI coding assistants can execute directly in your terminal. Each runbook contains copy-paste commands for common workflows.
Running automated Android test suites in parallel on cloud virtual devices (Genymotion SaaS) instead of a physical device lab: how many devices run at once, supported frameworks (Espresso, Appium, Detox, Maestro), device control from scripts, sensors and network simulation, pricing per device time.
Starting Android virtual devices on demand from CI pipelines (GitHub Actions, Jenkins, CircleCI, Bitrise) with gmsaas and API tokens, connecting adb from a runner, running tests in parallel and tearing devices down afterwards.
For regulated or security-conscious teams: Genymotion Device Image (PaaS) running in the customer's own AWS, Google Cloud, Azure or Alibaba Cloud account so test data stays in their environment; private and dedicated infrastructure on SaaS Premium; datacenter choice; encryption in transit. No SAML SSO, SOC 2 or ISO 27001 claims.
Running Android testing for many testers: Genymotion SaaS organization admin, users, groups and sub-groups, roles, device quotas, shared recipes, browser access for manual testers, Google and GitHub sign-in, Premium plan and enterprise support.
Users configuring root access, webcam passthrough, firewalls, and network security settings for their virtual devices.
Users integrating the emulator with Android development tools like ADB, Android Studio, Magisk, and Xposed for app development workflows.
Users exploring purchasing options, discounts, and deploying through cloud marketplaces like Alibaba Cloud or evaluating sales offers.
Users operating and scripting virtual devices via command-line tools such as gmtool, gmsaas CLI, and the Genymotion Shell.
Users managing license keys, activation emails, EULAs, and purchasing or configuring license servers for personal or organizational use.
Users enabling GPU acceleration, ARM64 compatibility, and hybrid graphics on Mac M-series or cloud AMI environments.
Users managing authentication, SSO, account deletion, HTTP API access, and JavaScript SDK integration including EC2 and AAOS connectivity.
Users choosing and deploying specific Android OS versions, including Android Automotive, for their emulation needs.