[CB-10750] Make Appium tests fail fast if the state is irrecoverable

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Assignee: Alexander Sorokin
• Reporter: Alexander Sorokin
• Created: 01/Mar/16 15:20
• Updated: 02/Mar/16 10:26
• Resolved: 02/Mar/16 10:26

Description

Currently the tests would try to recreate the session before each spec which results in very long waiting time and then the spec fails anyway because the session is irrecoverable.
Example:

Failing with message: [context("WEBVIEW_org.apache.mobilespec")] Error response status: 6
 > CALL currentContext() 
 > GET /session/:sessionID/context 
 > CALL quit() 
 > DELETE /session/:sessionID 

Ending your web drivage..

[MEDIC LOG Mon, 29 Feb 2016 08:18:40 GMT] Spec failed: camera.ui.spec.5.14 Combining options
[MEDIC LOG Mon, 29 Feb 2016 08:18:40 GMT] Starting new spec: camera.ui.spec.5.15 Combining options
Failed expectation: Something went wrong: the stopFlag is on. Please see the log for more details.
Failing with message: Something went wrong: the stopFlag is on. Please see the log for more details.
 > CALL currentContext() 
 > GET /session/:sessionID/context 
 > CALL quit() 
 > DELETE /session/:sessionID 

Ending your web drivage..

[MEDIC LOG Mon, 29 Feb 2016 08:21:40 GMT] Spec failed: camera.ui.spec.5.15 Combining options
[MEDIC LOG Mon, 29 Feb 2016 08:21:40 GMT] Starting new spec: camera.ui.spec.5.16 Combining options
Failed expectation: Something went wrong: the stopFlag is on. Please see the log for more details.
Failing with message: Something went wrong: the stopFlag is on. Please see the log for more details.
 > CALL currentContext() 
 > GET /session/:sessionID/context 
 > CALL quit() 
 > DELETE /session/:sessionID 

Ending your web drivage..

[MEDIC LOG Mon, 29 Feb 2016 08:24:40 GMT] Spec failed: camera.ui.spec.5.16 Combining options
[MEDIC LOG Mon, 29 Feb 2016 08:24:40 GMT] Starting new spec: camera.ui.spec.5.17 Combining options
Failed expectation: Something went wrong: the stopFlag is on. Please see the log for more details.
Failing with message: Something went wrong: the stopFlag is on. Please see the log for more details.
 > CALL currentContext() 
 > GET /session/:sessionID/context 
 > CALL quit() 
 > DELETE /session/:sessionID 

Ending your web drivage..

[MEDIC LOG Mon, 29 Feb 2016 08:27:40 GMT] Spec failed: camera.ui.spec.5.17 Combining options
[MEDIC LOG Mon, 29 Feb 2016 08:27:40 GMT] Starting new spec: camera.ui.spec.5.18 Combining options
Failed expectation: Something went wrong: the stopFlag is on. Please see the log for more details.
Failing with message: Something went wrong: the stopFlag is on. Please see the log for more details.
 > CALL currentContext() 
 > GET /session/:sessionID/context 
 > CALL quit() 
 > DELETE /session/:sessionID 

Ending your web drivage..

[MEDIC LOG Mon, 29 Feb 2016 08:30:40 GMT] Spec failed: camera.ui.spec.5.18 Combining options
[MEDIC LOG Mon, 29 Feb 2016 08:30:40 GMT] Starting new spec: camera.ui.spec.5.19 Combining options
Failed expectation: Something went wrong: the stopFlag is on. Please see the log for more details.
Failing with message: Something went wrong: the stopFlag is on. Please see the log for more details.
 > CALL currentContext() 
 > GET /session/:sessionID/context 
 > CALL quit() 
 > DELETE /session/:sessionID 

Ending your web drivage..
etc...

The proposed behavior is to try to recover the session after failure and if it fails, every remaining spec would fail fast.