![]() If all configuration is correct, you will see some output from ADB telling you that you have one connected device, which is the emulator you booted up a moment ago. Save out of all dialogs and open up another command prompt.%ANDROID_HOME% references the environment variable we previously set and includes it as part of a path to a particular directory, where the program adb.exe resides. What is this doing? First of all, the semicolon separates this path segment from other ones that came before. You can edit it and tack this special string onto the end: %ANDROID_HOME%\platform-tools. To do this, go to the same place you did to edit the environment variables, but look for an existing variable called PATH. A technically optional but very useful final step is to add part of the Android SDK path to your system PATH, so that certain commands (like adb) are available from a command prompt.This one should be called ANDROID_HOME, and it should be set to the location of the Android SDK you saw in the SDK Manager window. We do this by creating another environment variable (like we did for JAVA_HOME above). The last thing we need to do is make sure the location of the Android SDK is made available to Appium.Let it boot fully and play with it a bit to make sure it works as expected. Once it's done being created, click the green play button looking icon to launch it! You'll see what looks like an Android device being booted.You can name the emulator whatever you want.Use the NPM binary installed with Node to download the most recent version of Appium:. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |