>> Remember, we're not testing the plugins, so that shouldn't block any release.
+1, that any issues with plugins should not hold up the release. However, I thought that with each cadence release we were going to publish a list of the plugins that were tested with that release [1] - a sort of snapshot. We were going to at least list the commits on the blog post so it is possible to consistently recreate a 3.2 timeframe project at a future point. If we are still planning to do this than I think we need to run the manual plugin tests. [1] http://markmail.org/message/54crgxwa5anvva3o On Wed, Nov 6, 2013 at 5:14 PM, Joe Bowser <[email protected]> wrote: > On Wed, Nov 6, 2013 at 2:04 PM, Marcel Kinard <[email protected]> wrote: > > BTW, I also found a couple failures in the Android native tests on 4.2.2 > on a Nexus 7 with 3.2.0-rc1: > > > > junit.framework.AssertionFailedError > > at > org.apache.cordova.test.BackButtonMultiPageTest.testViaHref(BackButtonMultiPageTest.java:63) > > > > I actually think it's the test. It passes when I run it by itself > sometimes. I'm thinking that this should probably be deleted because > it's not the most reliable. > > > junit.framework.ComparisonFailure: expected:<pass> but was:<null> > > at > org.apache.cordova.test.CordovaResourceApiTest.testWebViewRequestIntercept(CordovaResourceApiTest.java:258) > > I got two failures with the ResourceAPI the last time I tested it as > well. It'd be good if this test was looked into, since I'm afraid it > might have gotten stale since it was written. > > > > > I thought it was pretty cool that 100% of the automated tests in > mobile-spec passed. An unbroken set of green dots ;-) > > I think it's cool as well. I wonder if this would happen on Jasmine 2. > > > > > On Nov 6, 2013, at 4:07 PM, Mike Billau <[email protected]> wrote: > > > >> I have been testing 3.2.0rc1 on Android 4.2.2 and 4.3 (hitting the 2.x > >> devices tomorrow. >
