Appium has the ability to start Android emulators and iOS simulators in a & quot; headless & quot; modality. This mean that the devices won & # x27; t get any graphic user interface; you won & # x27; t see them on your desktop, but they will still be running silently, testing your app.

Actually, the devices won & # x27; t run silently. They will still utter sounds through your speakers, entree the microphone, or anything else they usually do, you only won & # x27; t have a window on your blind which shows what they & # x27; re doing, and you won & # x27; t get those interactive buttons.

Most surprisingly, the emulators and simulators still render the app UI, they merely don & # x27; t display it. This means that the picture transcription and screenshot commands nonetheless work as usual. The lonesome thing we lose when running in headless mode is the power for a user to manually interpose and manipulate a device during a examination session.

This style of headless virtual device is a little different from headless browsers, which do not render the UI and therefore enable decreased test times because the costly procedure of deciding how to lay everything out on the blind is skipped. Sadly, running headless copycat and simulators will save a little bit of system resourcefulness by not run the actual windowed application, but equate to the CPU and memory required to run the gimmick, this is minimal.

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

Headless simulators and emulators should run exactly the like as their graphical vis-a-vis, but I encountered an issue running our commonexample appin a headless Android emulator! The issue seems to have something to do with ReactNativeNavigation, but this shows thatsomethingis different about Android emulators in headless way.

Headless emulators and simulators are almost utilitarian for gimmick farms which run devices on servers which have no graphical window manager in the initiative place. Though rare,running OSX fully headless is possible, in which case it is convenient that simulator can still be run.

Desktop tools can also take reward of this characteristic. Imagine a tool like Appium Desktop which starts its own emulators and simulators but doesn & # x27; t want to confuse the exploiter by popping up extra windows. The tool could use the headless feature to hide these windows from the user.

(In damage of employ headless devices on my personal figurer, the best use event I discovered is to stop the iOS simulator from stealing my window focus and popping up over whatever I & # x27; m doing whenever a trial starts up.)

How to Run Headless Emulators and Simulators

It & # x27; s simple! Just set the next desired potentiality to true:

caps.setCapability (`` isHeadless '', true);

If you & # x27; re examine on android, you will have to provide the avd desired capability so that Appium starts the emulator with the necessary arguments. Not specifying the avd upshot in Appium habituate the current emulator already running, and of course if it & # x27; s already lead with a UI, the UI will stay visible.

iOS has no such topic; if you set isHeadless to true, then Appium will shut down any presently running simulators and restart them in headless mode.

Unless you instructed Appium to shut down the device afterwards, the headless emulator and simulator will still be running after your session, but you won & # x27; t see them unless you check via the simctl utility or adb.

How Does it Work?

For iOS simulators, the actual simulator is a separate process from the Simulator.app app. When Appium starts an iOS simulator unremarkably, it has to start the simulator using the simctl utility, and then it establish Simulator.app. When bunk in headless mode, Appium just skips the 2d pace. If you want to start play with a simulator which is running in headless fashion, launch Simulator.app and a window will be expose for all presently running simulators. Warning: quiting Simulator.app shuts down all simulator!

For headless Android emulators, Appium starts the emulator via ADB as usual, and adds the -no-window flag. Documentation can be foundhere.

4 Parts

Connet Now