Appium encounters pitfalls

Appium encounters pitfalls

Last week, I started to try to use appium. First, I went to the official website and downloaded the appium client. After downloading and installing the app, I started to install the android sdk. After downloading the app on the official website, I downloaded the app, download updatesSDK ManagerThe download fails, and the FQ does not work. After reading the method, I tried to do it. However, I still couldn't do it in the way of the wormhole. Later, I tried to search in the 360 software manager. Fortunately, I found it in the 360 software manager, downloaded it, installed it, and clicked it to update it normally. I don't know why, it may be that 360 inject other things into the software, which is unknown. In any case, our purpose is the same.

Then, when I created the android simulator, various errors were reported and failed to run. Later, I saw in a forum that it was due to the problem of the latest video card driver and can be started normally after I uninstalled it.

After editing the python script, run it and report that the service cannot be started. The Internet says that 5037 is occupied. I tried to find the pid but did not find it. Then I ran the script normally and reported an error.

Error: Failed to start an Appium session, err was: Error: Command failed: C: \ Windows \ system32 \ cmd.exe/s/c "E: \ anzhuo \ platform-tools \ adb.exe-s emulator-5554 push "C :\\ Program Files \ Appium \ node_modules \ appium \ build \ android_bootstrap \ AppiumBootstrap. jar "/data/local/tmp /"
>
> Info: [debug] Error: Command failed: C: \ Windows \ system32 \ cmd.exe/s/c "E: \ anzhuo \ platform-tools \ adb.exe-s emulator-5554 push "C :\\ Program Files \ Appium \ node_modules \ appium \ build \ android_bootstrap \ AppiumBootstrap. jar "/data/local/tmp /"
>
> At ChildProcess. exithandler (child_process.js: 751: 12)
> At ChildProcess. emit (events. js: 110: 17)
> At maybeClose (child_process.js: 1016: 16)
> At Process. ChildProcess. _handle. onexit (child_process.js: 1088: 5)
> Info: [debug] Responding to client with error: {"status": 33, "value": {"message": "A new session cocould not be created. (Original error: Command failed: C: \ Windows \ system32 \ cmd.exe/s/c \ "E: \ anzhuo \ platform-tools \ adb.exe-s emulator-5554 push \ "C: \\\ Program Files \\\\ Appium \\\ node_modules \\\\ appium \\\\ build \\\ android_bootstrap \\\ AppiumBootstrap. jar \ "/data/local/tmp/\" \ n) "," killed ": false," code ": 1," signal ": null," cmd ": "C: \ Windows \ system32 \ cmd.exe/s/c \" E: \ anzhuo \ platform-tools \ adb.exe-s emulator-5554 push \ "C: \\\ Program Files \\\\ Appium \\\ node_modules \\\\ appium \\\\ build \\\ android_bootstrap \\\ AppiumBootstrap. jar \ "/data/local/tmp/\" "," origValue ":" Command failed: C: \ Windows \ system32 \ cmd.exe/s/c \ "E :\\ anzhuo \ platform-tools \ adb.exe-s emulator-5554 push \" C: \\\ Program Files \\\\ Appium \\\ node_modules \\\\ appium \\\\ build \\\ android_bootstrap \\\ AppiumBootstrap. jar \ "/data/local/tmp/\" \ n "}," sessionId ": null}
> Info: <-- POST/wd/hub/session 500 11653.286 MS-889

To solve this problem, go to TesterHome to read an article and run it.

In my opinion, time is the only criterion for truth testing.