Uploaded image for project: 'Apache Cordova'
  1. Apache Cordova
  2. CB-10750

Make Appium tests fail fast if the state is irrecoverable

    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      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.

        Attachments

          Activity

            People

            • Assignee:
              alsorokin Alexander Sorokin
              Reporter:
              alsorokin Alexander Sorokin
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: