1
Я работаю с Дженкинсом, Аппием и Муравей. Когда я запускаю тест Ant через терминал, все работает нормально. Но, когда я начинаю тест, вызывая Ant через Jenkins, я замечаю, что Jenkins принудительно останавливает приложение, а не перезапускает его (тестируется на реальных устройствах Android и Genymotion).Дженкинс прекращает работу при повторном тестировании приложения
я обнаружил, что-то странное в логах на данный момент приложение перезагружается, тест приложение запускается, но он убит Дженкинс, сервер Appium отвечает DETELE вместо GET, если я запустить тест через Jenkins:
Terminal:
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/xxx/Library/Android/sdk/platform- tools/adb with args: ["-P",5037,"-s","192.168.57.101:5555","shell","am","start","-n","com.xxx/im.actor.XXXActivity","-a","android.intent.action.MAIN","-c","android.intent.category.LAUNCHER","-f","0x10200000"]
[Appium] New AndroidDriver session created successfully, session d813f8ab-37c1-4f66-8b70-3008eb833c77 added to master session list
[MJSONWP] Responding to client with driver.createSession() result: {"platform":"LINUX","webSto...
[HTTP] <-- POST /wd/hub/session 200 3205 ms - 881
[HTTP] --> POST /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/timeouts {"type":"implicit","ms":10000}
[MJSONWP] Calling AppiumDriver.timeouts() with args: ["implicit",10000,"d813f8ab...
[debug] [BaseDriver] Set implicit wait to 10000ms
[MJSONWP] Responding to client with driver.timeouts() result: null
[HTTP] <-- POST /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/timeouts 200 3 ms - 76
[HTTP] --> GET /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/appium/device/current_activity {}
[MJSONWP] Calling AppiumDriver.getCurrentActivity() with args: ["d813f8ab-37c1-4f66-8b70-3...
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running /Users/xxx/Library/Android/sdk/platform-tools/adb with args: ["-P",5037,"-s","192.168.57.101:5555","shell","dumpsys","window","windows"]
[MJSONWP] Responding to client with driver.getCurrentActivity() result: "im.actor.SplashActivity"
Дженкинс:
[testng] [debug] [ADB] 1 device(s) connected
[testng] [debug] [ADB] Running /Users/xxxx/Library/Android/sdk/platform-tools/adb with args: ["-P",5037,"-s","192.168.57.101:5555","shell","am","start","-n","com.xxx/im.actor.XXXXActivity","-a","android.intent.action.MAIN","-c","android.intent.category.LAUNCHER","-f","0x10200000"]
[testng] [Appium] New AndroidDriver session created successfully, session 464902e9-5406-4d1e-915e-d4fad4e39da8 added to master session list
[testng] [MJSONWP] Responding to client with driver.createSession() result: {"platform":"LINUX","webSto...
[testng] [HTTP] <-- POST /wd/hub/session 200 3865 ms - 881
[testng] [HTTP] --> POST /wd/hub/session/464902e9-5406-4d1e-915e-d4fad4e39da8/timeouts {"type":"implicit","ms":20000}
[testng] [MJSONWP] Calling AppiumDriver.timeouts() with args: ["implicit",20000,"464902e9...
[testng] [debug] [BaseDriver] Set implicit wait to 20000ms
[testng] [MJSONWP] Responding to client with driver.timeouts() result: null
[testng] [HTTP] <-- POST /wd/hub/session/464902e9-5406-4d1e-915e-d4fad4e39da8/timeouts 200 4 ms - 76
[testng] [HTTP] --> DELETE /wd/hub/session/464902e9-5406-4d1e-915e-d4fad4e39da8 {}
[testng] [MJSONWP] Calling AppiumDriver.deleteSession() with args: ["464902e9-5406-4d1e-915e-d...
[testng] [debug] [AndroidDriver] Shutting down Android driver
[testng] [debug] [ADB] Getting connected devices...
[testng] [debug] [ADB] 1 device(s) connected
[testng] [debug] [ADB] Running /Users/xxxx/Library/Android/sdk/platform-tools/adb with args: ["-P",5037,"-s","192.168.57.101:5555","shell","am","force-stop","com.xxx"]
Я очень признателен, если кто-нибудь дать мне какие-либо советы для этого случая.