appium server日誌分析

文章出處

所以如果能夠更好的理解這些日誌的內容，會幫助我們更好的理解整個測試流程。

日誌的具體內容如下所示：

***** 通過」adb devices「命令列出查詢到的手機 emulator-5554

*****通過"adb -s emulator-5554 wait-for-device"和"adb -s emulator-5554 shell "echo 'ready'"檢查安卓手機是否已經準備好

> info: [debug] starting logcat capture

> info: [debug] getting device api level

> info: [debug] executing cmd: "d:\program files\android\android-sdk\platform-tools\adb.exe" -s emulator-5554 shell "getprop ro.build.version.sdk"

> info: [debug] device is at api level 19

> info: device api level is: 19

***** 通過adb執行相應的shell命令獲得安卓機器的api level

> info: [debug] getting device api level

> info: [debug] executing cmd: "d:\program files\android\android-sdk\platform-tools\adb.exe" -s emulator-5554 shell "getprop ro.build.version.sdk"

> info: [debug] device is at api level 19

***** 通過adb執行相應的shell命令獲得安卓機器的api level

> info: [debug] attempting to kill all 'uiautomator' processes

> info: [debug] getting all processes with 'uiautomator'

> info: [debug] executing cmd: "d:\program files\android\android-sdk\platform-tools\adb.exe" -s emulator-5554 shell "ps 'uiautomator'"

***** 通過adb執行相應的shell命令確保uiautomator沒有已經在跑

***** 可以發現「使用者名稱輸入框」在上次已經找過一次了，所以這裡我們相當於是在同乙個測試方法中對同乙個控制項查詢兩次。其實這是有點浪費

> info: [debug] stopping logcat capture

> info: [debug] logcat terminated with code null, signal sigterm

> info: [debug] [bootstrap] [debug] got data from client:

> info: [debug] [bootstrap] [debug] got command of type shutdown

> info: [debug] [bootstrap] [debug] returning result:

***** 關閉logcat