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

Shazron Abdullah edited comment on CB-13247 at 9/7/17 7:36 AM:
---------------------------------------------------------------

I had to use a local file-transfer server to test the file-transfer tests using 
mobilespec, see CB-12173

On device, mobilespec had 4 failures:
{code}
    media.spec.24
    media.spec.22
    file.spec.147
    contacts.spec.7.3
{code}

However, when I tested the plugins individually using cordova-paramedic, I had 
only media plugin failures:
{code}
    media.spec.24
    media.spec.22
{code}

These are not critical, and consistent with the [email protected] mobile-spec 
results in CB-12687.




was (Author: shazron):
I had to use a local file-transfer server to test the file-transfer tests using 
mobilespec, see CB-12173

On device, mobilespec had 4 failures:
    media.spec.24
    media.spec.22
    file.spec.147
    contacts.spec.7.3

However, when I tested the plugins individually using cordova-paramedic, I had 
only media plugin failures:
    media.spec.24
    media.spec.22

These are not critical, and consistent with the [email protected] mobile-spec 
results in CB-12687.



> Cordova-iOS Platform Release Sept 6, 2017
> -----------------------------------------
>
>                 Key: CB-13247
>                 URL: https://issues.apache.org/jira/browse/CB-13247
>             Project: Apache Cordova
>          Issue Type: Task
>          Components: cordova-ios
>            Reporter: Shazron Abdullah
>            Assignee: Shazron Abdullah
>              Labels: backlog, ios-next
>             Fix For: [email protected]
>
>
> Following steps at 
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to