cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Mocny <>
Subject Re: [mobile-spec] consistency and reliability
Date Thu, 30 Oct 2014 23:01:37 GMT
I've seen that in the past and it usually happens due to misuse of jasmine,
which seems unfortunately quite brittle.  Specifically, if done() isn't
called, or an async event fires after a test has already failed / timed out
and calls done(), or registers new tests with it() etc, weird things will

Usually its a sign that a test is not handling failures appropriately, but
it is a bit unfortunate that jasmine is so brittle.


On Thu, Oct 30, 2014 at 6:10 PM, Toda, Shingo <>

> This is exactly what I got too.
> Regards,
> Shingo
> From: Shazron []
> Sent: Friday, October 31, 2014 9:02 AM
> To:
> Cc: Toda, Shingo
> Subject: Re: [mobile-spec] consistency and reliability
> Seems to be exactly what I am seeing.
> Here's the image as a link:
> On Thu, Oct 30, 2014 at 2:57 PM, Toda, Shingo <
> <>> wrote:
> Hi Shazron
> Our team are running mobilespec for Android, iOS and Windows. I cannot see
> the attachment but we also have been seeing what you’ve gotten since new
> style mobilespec was introduced. It seems that each plugin test run works
> fine but if all tests get run at once I am likely to get more than one
> report in a run reporting that there are a number of specs like 900 specs
> (I don’t think specs are so much).
> I noticed that some of the specs were called more than once when I got
> multiple reports. I usually disable FileTransfer, Globalization and Media
> specs at first then run test for them individually because I saw some of
> those tests got called more than once. This could be just my case so it
> might not be yours.
> Regards,
> Shingo
> From: Shazron [<>]
> Sent: Friday, October 31, 2014 7:54 AM
> To:<>
> Subject: [mobile-spec] consistency and reliability
> `cordova-mobile-spec/createmobilespec/createmobilespec.js --ios
> --globalplugins`
> Has anyone gotten mobile-spec to work consistently? I get wildly different
> results on each run. Sometimes there is more than one report in a run. See:
> [Inline image 1]

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message