Appium Start Run log analysis

Source: Internet
Author: User
Tags appium

1. Manually start the Appium service

> Launching Appium server with Command:c:\program Files (x86) \appium\node.exe lib\server\main.js--address 127.0.0.1- -port 4723--platform-name Android--platform-version--automation-name Appium--device-name "Lge-nexus_ 4-005475cbccd279d4 "--log-no-color> info:welcome to Appium v1.4.16 (REV ae6877eff263066b26328d457bd285c0cc62430d) > Info:appium REST HTTP Interface listener started on 127.0.0.1:4723> info: [Debug] Non-default server args: {"addr ESS ":" 127.0.0.1 "," lognocolors ": True," DeviceName ":" Lge-nexus_4-005475cbccd279d4 "," PlatformName ":" Android "," Platformversion ":", "Automationname": "Appium"}> info:console loglevel:debug

2. "Testscript" sends a POST request with JSON data (capabilities) to/wd/hub/session to create the session> Info:-post/wd/hub/session {"desiredcapabilities": {"apppackage": "Com.edusoho.kuozhi", "appactivity": " Com.edusoho.kuozhi.KuozhiActivity "," platformversion ":" 5.1.1 "," Automationname ":" Appium "," sessionoverride ": true, "Unicodekeyboard": True, "PlatformName": "Android", "DeviceName": "Red Note3", "Resetkeyboard": false}, " Requiredcapabilities ": {}," capabilities ": {" desiredcapabilities ": {" apppackage ":" Com.edusoho.kuozhi "," appactivity ":" Com.edusoho.kuozhi.KuozhiActivity "," platformversion ":" 5.1.1 "," Automationname ":" Appium "," Sessionoverride ": True, "Unicodekeyboard": True, "PlatformName": "Android", "DeviceName": "Red Note3", "Resetkeyboard": false}, " Requiredcapabilities ": {}}," Alwaysmatch ": {" apppackage ":" Com.edusoho.kuozhi "," appactivity ":" Com.edusoho.kuozhi.KuozhiActivity "," platformversion ":" 5.1.1 "," Automationname ":" Appium "," sessionoverride ": true, "Unicodekeyboard": True, "PlatformName": "Android", "DeviceName": "Red Note3", "Resetkeyboard": false}, "Firstmatch": []} > Info:client user-agent STRING:APACHE-HTTPClient/4.5.2 (java/1.8.0_111) > Info: [debug] The following desired capabilities were provided, but not recognized by app Ium. They'll is passed on to any other services running on the this server. : Sessionoverride

Initialize the app (without getting to the app but also Android pack (depending on the script configuration of the capabilities parameter)) > info: [debug] didn ' t get app but do get Android package, will a Ttempt to launch it on the device

New Appium session> info: [Debug] Creating new Appium session 2ac0e18a-9120-4e90-a066-c6ddb1a1deaf

3. Start Android Appium> info:starting android Appium

Check jdk> info: [Debug] Getting Java version> Info:java version is:1.8.0_111

Check adb> info: [Debug] Checking whether ADB is present> info: [Debug] Using adb from D:\Software\adt-bundle-windows-x8 6_64-20140321\sdk\platform-tools\adb.exe> warn:no app capability, can ' t parse package/activity

4. Check and connect device devices> Info: [debug] Using fast reset? true> info: [Debug] Preparing device for session> info: [Debug] Not checking whether app is present since we are Uming (assuming) it's already on the device

Check device information > info:retrieving device> info: [Debug] Trying to find a connected Android device

Connection device > Info: [Debug] Getting connected devices...> info: [Debug] Executing cmd:d:\software\adt-bundle-windows-x86_ 64-20140321\sdk\platform-tools\adb.exe devices

Device Connection Success > Info: [Debug] 1 device (s) connected> info:found device 5977b8a3> info: [Debug] Setting device ID to 5977 b8a3> info: [Debug] waiting for device-to-respond to shell commands (Timeout = 5) > Info: [Debug] exe cuting cmd:d:\software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe-s 5977b8a3 Wait-for-device > Info: [debug] Executing cmd:d:\software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe-s 5977B8A3 Shell "Echo ' Ready '"

Open logcat> Info: [Debug] Starting Logcat capture> info: [Debug] Getting device API level

Get device System API version > Info: [debug] Executing cmd:d:\software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\ Adb.exe-s 5977b8a3 Shell "Getprop ro.build.version.sdk" > Info: [Debug] Device is in API level 22> Info:device API Level is:22

Get device System language > Info: [Debug] extracting strings for language:default> info: [Debug] Apk doesn ' t exist locally> info: [Debug] Could not get strings, but it looks like we had a old strings file anyway, so ignoring> info: [Debug] Executing CMD:D : \software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe-s 5977b8a3 Shell "rm-rf/data/local/tmp/ Strings.json "

5. Check app installation and related configuration informationThere is no existing app uninstalled because the Appium server is not set--full-reset> info: [Debug] not uninstalling app since server does started with--FULL-RESET&G T Info: [Debug] Skipping install since we launched with a package instead of a app path

Map the system's 4724 port to the 4724 port of the test device > Info: [Debug] Forwarding system:4724 to device:4724> info: [Debug] Executing Cmd:d:\soft Ware\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe-s 5977b8a3 forward tcp:4724 tcp:4724

Push the Bootstrap.jar to the device

> Info: [debug] Pushing Appium bootstrap to device...> info: [Debug] Executing cmd:d:\software\adt-bundle-windows-x 86_64-20140321\sdk\platform-tools\adb.exe-s 5977b8a3 Push "C:\\Program Files (x86) \\Appium\\node_modules\\appium\\ Build\\android_bootstrap\\appiumbootstrap.jar "/data/local/tmp/

Make the Unicode keyboard available

> Info: [debug] enabling Unicode keyboard support

Push the Unicode IME input method to the device > info: [debug] Pushing Unicode IME to device...> info: [Debug] Executing cmd:d:\software\ Adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe-s 5977b8a3 Install "C:\Program Files (x86) \appium\ node_modules\appium\build\unicode_ime_apk\unicodeime-debug.apk "

Get device Current Input method

> Info: [debug] Executing cmd:d:\software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe-s 5977B8A3 Shell "Settings get secure Default_input_method"

Cancel device Current Input method (Baidu Input Method Xiaomi V6 version) > Info: [debug] unsetting IME ' com.baidu.input_miv6/. Imeservice '

Set the Unicode input method to the device current Input method > info: [Debug] Setting IME to ' io.appium.android.ime/. Unicodeime ' > Info: [debug] Executing cmd:d:\software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\ Adb.exe-s 5977b8a3 Shell "ime enable io.appium.android.ime/. Unicodeime "> Info: [debug] Executing cmd:d:\software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\ Adb.exe-s 5977b8a3 Shell "IME set io.appium.android.ime/. Unicodeime "

install setting and unlock apk to test deviceInstall setting APK to test device > Info: [debug] Pushing settings apk to device...> info: [Debug] Executing Cmd:d:\software\adt-bu Ndle-windows-x86_64-20140321\sdk\platform-tools\adb.exe-s 5977b8a3 Install "C:\Program Files (x86) \appium\node_ modules\appium\build\settings_apk\settings_apk-debug.apk "

Install unlock.apk to test equipment > Info: [debug] pushing unlock helper app to device...> info: [Debug] Executing Cmd:d:\software\ad T-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe-s 5977b8a3 Install "C:\Program Files (x86) \appium\node_ modules\appium\build\unlock_apk\unlock_apk-debug.apk "> info:starting app> info: [Debug] attempting to kill all ' Uiautomator ' processes> info: [Debug] Getting all processes with ' uiautomator ' > Info: [debug] Executing Cmd:d:\soft Ware\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe-s 5977b8a3 Shell "ps ' uiautomator '" > Info: [ Debug] No matching processes found

6, run bootstrap on test machine > Info: [Debug] Running bootstrap> info: [Debug] Spawning:d:\software\adt-bundle-windows-x86_64-20140321\sdk\ Platform-tools\adb.exe-s 5977b8a3 Shell Uiautomator runtest appiumbootstrap.jar-c IO.APPIUM.ANDROID.BOOTSTRAP.BOOTSTRAP-E pkg com.edusoho.kuozhi-e disableandroidwatchers false> info: [Debug] [ Uiautomator STDOUT] instrumentation_status:numtests=1> info: [Debug] [Uiautomator STDOUT] Instrumentation_status: stream=> info: [Debug] [uiautomator STDOUT] io.appium.android.bootstrap.bootstrap:> info: [Debug] [Uiautomator STDOUT] instrumentation_status:id=uiautomatortestrunner> info: [Debug] [Uiautomator STDOUT] Instrumentation_ status:test=testrunserver> info: [Debug] [Uiautomator STDOUT] instrumentation_status:class= io.appium.android.bootstrap.bootstrap> info: [Debug] [Uiautomator STDOUT] Instrumentation_status:current=1> Info: [Debug] [Uiautomator STDOUT] Instrumentation_status_code:1

Appium socket server on port 4724 open > Info: [Debug] [BOOTSTRAP] [debug] socket opened on port 4724> info: [Debug] [Bootstra P] [debug] Appium Socket Server ready> info: [Debug] [BOOTSTRAP] [debug] Loading json ...

Register Crash listener > Info: [Debug] [BOOTSTRAP] [debug] registered crash watchers.

If device lock screen, wake device > Info: [debug] waking up device if it's not alive

Push the wake command to appium Task Force column > info: [debug] pushing command to appium Work queue: ["Wake",{}]> info: [Debug] [BOOTSTRAP] [ Debug] Client connected> info: [Debug] [BOOTSTRAP] [debug] Got data from Client: {"cmd": "Action", "action": "Wake", "Para MS ":{}}> info: [Debug] [BOOTSTRAP] [debug] Got command of type action> info: [Debug] [BOOTSTRAP] [debug] Got command action:wake> info: [Debug] [BOOTSTRAP] [debug] Returning result: {"status": 0, "value":true}> info: [Debug] Executin G cmd:d:\software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe-s 5977b8a3 Shell "Dumpsys window" > Info: [Debug] screen already unlocked, continuing.

Push the Getdatadir command to appium Task Force column > info: [debug] pushing command to appium Work queue: ["Getdatadir",{}]> info: [Debug] [ BOOTSTRAP] [debug] Got data from client: {"cmd": "Action", "Action": "Getdatadir", "params":{}}> info: [Debug] [ BOOTSTRAP] [Debug] Got command of type action> info: [Debug] [BOOTSTRAP] [debug] Got command action:getdatadir> INF o: [Debug] [BOOTSTRAP] [debug] Returning result: {"status": 0, "value": "\/data\/local\/tmp"}> info: [Debug] DataDir Set To:/data/local/tmp

Push the Compressedlayouthierarchy command to the Appium Task Force column> Info: [debug] pushing command to appium Work queue: ["Compressedlayouthierarchy", {"Compresslayout":false}]> info : [Debug] [BOOTSTRAP] [debug] Got data from client: {"cmd": "Action", "Action": "Compressedlayouthierarchy", "params": {" Compresslayout ":false}}> info: [Debug] [BOOTSTRAP] [debug] Got command of type action> info: [Debug] [BOOTSTRAP] [de Bug] Got Command action:compressedlayouthierarchy> info: [Debug] [BOOTSTRAP] [debug] Returning result: {"status": 0, "V Alue ": false}

Check the device API version > Info: [Debug] Getting device API level> info: [Debug] Executing cmd:d:\software\adt-bundle-windows-x8 6_64-20140321\sdk\platform-tools\adb.exe-s 5977b8a3 Shell "Getprop ro.build.version.sdk" > Info: [Debug] Device is at API level 22

Start app> info: [Debug] Executing cmd:d:\software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe-s 5977B8A3 Shell "am start-s-a android.intent.action.main-c android.intent.category.launcher-f 0x10200000-n Com.edusoho . kuozhi/com.edusoho.kuozhi.kuozhiactivity "

Let the app under test get focus > Info: [debug] Waiting for pkg "Com.edusoho.kuozhi" and Activity "com.edusoho.kuozhi.KuozhiActivity" to be focused> info: [Debug] Getting focused package and activity> info: [Debug] Executing CMD:D:\SOFTWARE\ADT-BUNDLE-WI Ndows-x86_64-20140321\sdk\platform-tools\adb.exe-s 5977b8a3 Shell "Dumpsys window Windows"

Get device System version > Info: [debug] Executing Cmd:d:\software\adt-bundle-windows-x86_64-20140321\sdk\platform-tools\adb.exe -S 5977B8A3 Shell "Getprop ro.build.version.release" > Info: [Debug] Device is at release version 5.1.1

Device initialization successful, ready to receive commands sent by Testscript->appium server > Info: [Debug] Device launched! Ready for Commands

Set command default timeout time is 60 seconds > Info: [debug] Setting command timeout to the default of secs> info: [Debug] Appium session Starte D with SessionId 2ac0e18a-9120-4e90-a066-c6ddb1a1deaf

7. Feedback the results of the first POST request> Info: <--post/wd/hub/session 303 10052.520 ms-74

Appium Start Run log analysis

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.