You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now we still need selenium grid with all devices connected which is pretty old school.
When we do hard appium restart in between sessions it kill selenium node and reconnect asap but grid itself still continue to use old connection.
As result 2nd test crash with below exception.
let's investigate the approach when we cleanup appium log file instead of hard kill and start to keep appium and selenium grid connection.
run regular mobile sample test
-> all 3 should executed, for each session video and session.log registered in the reporting
override capabilities.app to use invalid non existing path and execute test
-> all 3 tests should fail but we should see for each of them session.log attached obligatory. for some of them even video might be generated
run with invalid path and device with pin
-> all 3 tests should have session.log obligatory and 90% that video as well how device is unpined
Note: step 2 and 3 should be done only with 7.3.15+ or 7.3.15-SNAPSHOT as only in this version we deliver fallbackSessionId for reference. Exact reporting build and env - still TBD
As of now we still need selenium grid with all devices connected which is pretty old school.
When we do hard appium restart in between sessions it kill selenium node and reconnect asap but grid itself still continue to use old connection.
As result 2nd test crash with below exception.
let's investigate the approach when we cleanup appium log file instead of hard kill and start to keep appium and selenium grid connection.
The text was updated successfully, but these errors were encountered: