#CLOUD GENY ANDROID#

That reduces your chances to forget a running device.

In other words, you can't leave Genymotion SaaS devices up and running after your test session ends. behavior.shutdownDevice cannot be disabled ĭetox CLI has -u, -cleanup argument, and the behavior config has the respective shutdownDevice property, but none of them can be effectively disabled on Genymotion SaaS devices.ĭetox always shuts them down in the end of the test session, unless you abruptly terminate its execution (see the previous caveat). Besides, Ctrl+C'ing proves to be useful when you want to leave the device activeĪt some point of your test scenario and interact with it manually. We plan to improve this behavior and secure emergency teardown someday, but beforehand the next issue This can minimize the costsĮven if you accidentally leave the device powered on. You can set up a safeguard for the maximum run duration So that you're able to see your e-mail after running this: Next, you should get gmsaas CLI tool installed and configured, The new accounts – they come with 2 concurrent devices and free 60 minutes out of the box. If you already have an account there, make sure there are available device minutes. You need to register an account in Genymotion SaaS, so that you have valid credentials to use with their CLI tool,

#CLOUD GENY ANDROID#

Genymotion SaaS, the platform that offers cloud-based Android Virtual Devices. In other words, if you're experiencing scaling issues or struggling with managing local Android emulators,Ī good idea would be to migrate to SaaS platforms, where you can start and stop devices on demand at any scale.Īt the moment, Detox can offer you a first-class integration with Running a few virtual devices at once, but running a dozen devices at once would make it slow and unreliable. Indeed, an average build agent would handle Would be forwarding -maxWorkers ), but this approach has its limitations. As the number of your end-to-end tests grows, the overall test session duration might easily surpass an hour or two.Ī good idea first would be to parallelize the test execution using your test runner (e.g.

Cloud geny