[
https://issues.apache.org/jira/browse/CB-10750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Sorokin updated CB-10750:
-----------------------------------
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:
{noformat}
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...
{noformat}
The proposed behavior is to try to recover the session after failure and if it
fails, every remaining spec would fail fast.
was:
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:
{noformat}
> CALL execute("var info = document.createElement(\"div\"); info.id = \"info\";
> document.body.appendChild(info);")
> POST /session/:sessionID/execute {"script":"var info =
> document.createElement(\"div\"); info.id = \"info\";
> document.body.appendChild(info);","args":[]}
An error occured: [execute("var info = document.createElement(\"div\"); info.id
= \"info\"; document.body.appendChild(info);")] Error response status: 6,
Failing with message: [execute("var info = document.createElement(\"div\");
info.id = \"info\"; document.body.appendChild(info);")] Error response status:
6,
[MEDIC LOG Tue, 01 Mar 2016 10:24:18 GMT] Spec failed: camera.ui.spec.3
Dismissing the camera
[MEDIC LOG Tue, 01 Mar 2016 10:24:18 GMT] Starting new spec: camera.ui.spec.4
Dismissing the edit
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.
[MEDIC LOG Tue, 01 Mar 2016 10:27:18 GMT] Spec failed: camera.ui.spec.4
Dismissing the edit
[MEDIC LOG Tue, 01 Mar 2016 10:27:18 GMT] Starting new spec: camera.ui.spec.5.1
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.
[MEDIC LOG Tue, 01 Mar 2016 10:30:18 GMT] Spec failed: camera.ui.spec.5.1
Combining options
[MEDIC LOG Tue, 01 Mar 2016 10:30:18 GMT] Starting new spec: camera.ui.spec.5.2
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.
[MEDIC LOG Tue, 01 Mar 2016 10:33:18 GMT] Spec failed: camera.ui.spec.5.2
Combining options
[MEDIC LOG Tue, 01 Mar 2016 10:33:18 GMT] Starting new spec: camera.ui.spec.5.3
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.
[MEDIC LOG Tue, 01 Mar 2016 10:36:18 GMT] Spec failed: camera.ui.spec.5.3
Combining options
etc...
{noformat}
The proposed behavior is to try to recover the session after failure and if it
fails, every remaining spec would fail fast.
> Make Appium tests fail fast if the state is irrecoverable
> ---------------------------------------------------------
>
> Key: CB-10750
> URL: https://issues.apache.org/jira/browse/CB-10750
> Project: Apache Cordova
> Issue Type: Task
> Reporter: Alexander Sorokin
> Assignee: Alexander Sorokin
>
> 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:
> {noformat}
> 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...
> {noformat}
> The proposed behavior is to try to recover the session after failure and if
> it fails, every remaining spec would fail fast.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
