[ 
https://issues.apache.org/jira/browse/CB-11162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260323#comment-15260323
 ] 

ASF GitHub Bot commented on CB-11162:
-------------------------------------

GitHub user alsorokin opened a pull request:

    https://github.com/apache/cordova-plugin-camera/pull/208

    CB-11162 Appium tests: retry spec on failure

    https://issues.apache.org/jira/browse/CB-11162

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/MSOpenTech/cordova-plugin-camera CB-11162

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cordova-plugin-camera/pull/208.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #208
    
----
commit f91578ce0128f6ba51f2ddd79c6ec3fd022d0a84
Author: Alexander Sorokin <[email protected]>
Date:   2016-04-27T15:02:48Z

    CB-11162 Appium tests: retry spec on failure

----


> Implement retry logic for Camera Appium tests
> ---------------------------------------------
>
>                 Key: CB-11162
>                 URL: https://issues.apache.org/jira/browse/CB-11162
>             Project: Apache Cordova
>          Issue Type: Task
>          Components: Appium, Plugin Camera
>            Reporter: Alexander Sorokin
>            Assignee: Alexander Sorokin
>
> Camera plugin Appium tests are very flaky because of some weird Android 
> emulator behavior. The most common error is happening at random stages of 
> image capture. The error callback gets called with the message "Camera 
> cancelled".
> To avoid these flaky failures, each spec should be retried up to three times. 
> If the failure persists, then and only then it should fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to