We & # x27; ve discussed before how to, but of course it & # x27; s also possible to use Windows as the legion environment for traditional mobile testing with Appium. It is not, unfortunately, possible to automate iOS simulators on Windows, because iOS simulator are only designed to run on macOS as part of Xcode. It is too not technically possible to plugged into a Windows machine, though some folk have figured this out. It & # x27; s but not a support use case.

What issupported is to with Appium on Windows! So, let & # x27; s take a look at all the step required to support this form of automation. (Note that I am assume a recent install of the modern Windows 10 OS).

Requirements

Appium & # x27; s requirements for Android try on Windows are what you & # x27; d expect: essentially, the requirements for Android dev, plus Appium & # x27; s own requirement for its runtime surround.

1. A version of NodeJS supported by Appium (currently 10+, but typically the latest stable version),or Appium Desktop
2. The Java Development Kit (JDK)
3. Android Studio and related tools

System Setup

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

1. Install NodeJS. (If you are going to run Appium Desktop, you can hop-skip this step since Appium Desktop bundles its own variant of Node. But I conceive it & # x27; s a good practice to be able to run Appium from the command line, since you might want to run a beta version of Appium at some point. And don & # x27; t care -- Appium Desktop & # x27; s Inspector can verbalise to variation of Appium escape on the CLI).
2. Install the JDK. (I commonly get Java 8 for compatibility with older test suites, but get whatever version works for you). Sorry, you & # x27; ll have to do Oracle & # x27; s signup/login dance. When you run the downloaded installer, pay attention to where Java is installed (for example, did it get put in the directory C: \Program Files\Java\jdk1.8.0?).
3. Set the JAVA_HOME environment variable in your system scope. If you & # x27; ve ne'er set an environment variable before,thisis a good guide. Basically, we need to make a new variable with the name JAVA_HOME, and the value equal to the path where the JDK was installed (e.g., C: \Program Files\Java\jdk1.8.0). Once you & # x27; ve saved out of all the dialog, open up a command prompting and type echo % JAVA_HOME %. You should see your JDK path print back out to you! Appium involve this in order to cognise where to regain relevant Java binary.

Check out:

Appium Setup

1. Start an Admin bidding prompting (type & quot; cmd & quot; into the Start menu and then hit CTRL+SHIFT+ENTER to establish the command prompt in Admin manner).
2. Use the NPM binary installed with Node to download the most late adaptation of Appium:

npm install -g appium

3. Run Appium (ensuring I & # x27; m still in the Admin console!) to make certain it act.

appium

(NB: You & # x27; ll invariably want to run Appium from an Admin console.)

For now, we can just kill the Appium server until we & # x27; re ready to really run a test.

Also check:

Android Setup

1. Download and installAndroid Studio. You can safely follow all the nonpayment during the installation.
2. Once Android Studio is launched, click the & quot; Configure & quot; menu selection in the launch window, where you & # x27; ll see two crucial point: & quot; AVD Manager & quot; and & quot; SDK Manager & quot;. First, clink SDK Manager.
   

1. Once the SDK Manager is open, ensure that at least one Android SDK is establish. On this perspective, take tone of the & quot; Android SDK Location & quot;, since we & # x27; ll need this emplacement in a bit.
2. Close the SDK Manager and open the AVD Manager. The AVD Manager is where we will create and launch Android Virtual Devices, differently known as ape. When it launches, assuming you have no other devices already, you can click & quot; Create Device & quot; to commence the imitator conception wizard. The 1st blind you & # x27; re presented with aspect something like this:
   

1. Here you can choose any gimmick configuration preset. It doesn & # x27; t really weigh what you choose at this point, so pick something fun!
2. Next, work through the several other prompts. You can safely pick default values unless you hap to know you have other needs. When move for the scheme version of the emulator, you & # x27; ll need to cull a system image that you hold downloaded. If one is not already downloaded, click the & quot; Download & quot; link beside it to make it available for the ape.
   

1. You can name the emulator whatever you require.
2. Once it & # x27; s make being created, click the green play push looking icon to establish it! You & # x27; ll see what looks like an Android twist be reboot. Let it reboot full and play with it a bit to get sure it work as expected.
3. The last thing we demand to do is make sure the location of the Android SDK is made available to Appium. We do this by make another environment variable (like we did for JAVA_HOME above). This one should be phone ANDROID_HOME, and it should be set to the positioning of the Android SDK you saw in the SDK Manager window.
4. A technically optional but very utile net step is to add component of the Android SDK path to your scheme PATH, so that sure bidding (like adb) are available from a bidding prompt. To do this, go to the same place you did to edit the environment variable, but look for an existing variable call PATH. You can redact it and tack this special string onto the end:; % ANDROID_HOME % \platform-tools. What is this doing? First of all, the semicolon separates this path segment from early ones that come before. % ANDROID_HOME % references the environment variable we previously set and include it as part of a way to a particular directory, where the program adb.exe resides.
5. Save out of all duologue and open up another command prompting. Type adb device and hit enter. If all configuration is correct, you will see some output from ADB telling you that you hold one associate gimmick, which is the emulator you booted up a moment ago.
6. One last useful tip is to add yet another directory to the path, this clip % ANDROID_HOME % \emulator, which gives you access to the emulator binary from the command line, in cause you don & # x27; t want to open Android Studio precisely to run your ape. (If you do add this, make certain not to block the; as a separator between paths).

Read:

Conclusion

Let & # x27; s critique what we & # x27; ve done: we & # x27; ve instal canonical system dependencies, the Appium server itself, and everything related to working with Android specifically. That means we & # x27; re finished!

All that remains is to depart the Appium server (just run Appium from an admin command prompt), load up an Appium test in your editor of option, pinch anything that involve to be tweaked for your system, and then kick off the test. If all goes well, you should see the Appium host spitting out logs and launching your app on the Android emulator!

4 Parts

Connet Now