Basically, we need to create 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). If you've never set an environment variable before, this is a good guide. Set the JAVA_HOME environment variable in your system settings.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?). Sorry, you'll have to do Oracle's signup/login dance. (I usually get Java 8 for compatibility with older test suites, but get whatever version works for you). And don't worry-Appium Desktop's Inspector can talk to versions of Appium running on the CLI). But I think it'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. (If you are going to run Appium Desktop, you can skip this step since Appium Desktop bundles its own version of Node. A version of NodeJS supported by Appium (currently 10+, but typically the latest stable version), or Appium Desktop.RequirementsĪppium's requirements for Android testing on Windows are what you'd expect: basically the requirements for Android dev, plus Appium's own requirement for its runtime environment. (Note that I am assuming a recent install of the modern Windows 10 OS). What is supported is to run your Android tests with Appium on Windows! So let's take a look at all the steps required to support this kind of automation. It is also not technically possible to work with real iOS devices plugged into a Windows machine, though some folks have figured this out. It is not, unfortunately, possible to automate iOS simulators on Windows, because iOS simulators are only designed to run on macOS as part of Xcode. We've discussed before how to use Appium to automate Windows desktop apps, but of course it's also possible to use Windows as the host environment for traditional mobile testing with Appium.
0 kommentar(er)
