OK, I'm getting the same error on this end. I have no idea why this passed last week. I'll add it to the manifest.
On Wed, Nov 14, 2012 at 1:18 PM, Simon MacDonald <simon.macdon...@gmail.com> wrote: > The manifest in the Apache repo ( > https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-android.git;a=blob;f=test/AndroidManifest.xml;h=e35f6c678ba6381f4b9e9fcadc86ccf0930969bc;hb=HEAD) > does not have "backbuttonmultipage" anywhere it in. > > > Simon Mac Donald > http://hi.im/simonmacdonald > > > On Wed, Nov 14, 2012 at 4:14 PM, Joe Bowser <bows...@gmail.com> wrote: > >> Simon: Looks like it's missing the manifest. Can you make sure your >> manifest is updated? I had to clean that up on one of the more recent >> commits. >> >> On Wed, Nov 14, 2012 at 1:10 PM, Simon MacDonald >> <simon.macdon...@gmail.com> wrote: >> > All of org.apache.cordova.test.BackButtonMultiPageTest fail for me. Seems >> > to be missing: >> > >> > java.lang.RuntimeException: Unable to resolve activity for: Intent { >> > act=android.intent.action.MAIN flg=0x10000000 >> > cmp=org.apache.cordova.test/.actions.backbuttonmultipage } >> > at >> android.app.Instrumentation.startActivitySync(Instrumentation.java:370) >> > at >> > >> android.test.InstrumentationTestCase.launchActivityWithIntent(InstrumentationTestCase.java:119) >> > at >> > >> android.test.InstrumentationTestCase.launchActivity(InstrumentationTestCase.java:97) >> > at >> > >> android.test.ActivityInstrumentationTestCase2.getActivity(ActivityInstrumentationTestCase2.java:104) >> > at >> > >> org.apache.cordova.test.BackButtonMultiPageTest.setUp(BackButtonMultiPageTest.java:47) >> > at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:169) >> > at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:154) >> > at >> > >> android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:545) >> > at >> > >> android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1551) >> > >> > >> > Simon Mac Donald >> > http://hi.im/simonmacdonald >> > >> > >> > On Tue, Nov 13, 2012 at 1:38 PM, Joe Bowser <bows...@gmail.com> wrote: >> > >> >> BUMP! Can everyone run these tests? I need to know about failures ASAP >> >> >> >> On Mon, Nov 5, 2012 at 9:44 AM, Joe Bowser <bows...@gmail.com> wrote: >> >> > Sorry, wrong thread. Obviously. >> >> > >> >> > The command line version of the unit tests is on the Wiki. >> >> > >> >> > >> >> > On Mon, Nov 5, 2012 at 9:43 AM, Joe Bowser <bows...@gmail.com> wrote: >> >> >> >> >> >> I did send an e-mail about the cleaning of the tests with the wiki >> >> >> article. Did everyone get it? >> >> >> >> >> >> >> >> >> On Mon, Nov 5, 2012 at 9:21 AM, Andrew Grieve <agri...@chromium.org> >> >> >> wrote: >> >> >>> >> >> >>> Yes, thanks Joe for pushing on this. Testing will only make things >> >> >>> better! >> >> >>> >> >> >>> Do you think it'd be feasible to create a script that would launch >> the >> >> >>> tests? Eclipse is great when they fail, but to ensure they pass, >> >> command >> >> >>> line is often nicer. The instructions on the wiki seem like they >> may be >> >> >>> out >> >> >>> of date? They reference phonegap, and they don't say what cordova >> >> target >> >> >>> to >> >> >>> build. >> >> >>> >> >> >>> >> >> >>> On Fri, Nov 2, 2012 at 9:25 PM, Joe Bowser <bows...@gmail.com> >> wrote: >> >> >>> >> >> >>> > If we still have JAR issues, that should be a blocker for the >> >> release. >> >> >>> > Having these tests should be required now, since we have too many >> >> Java >> >> >>> > bits that we can't break. I removed the old Selenium JAR a while >> ago. >> >> >>> > >> >> >>> > I would love it if we could get Selenium to work with >> CordovaWebView >> >> so >> >> >>> > that we could click on HTML elements, but we should be able to >> >> automate >> >> >>> > the >> >> >>> > Back Button and Menu Button bindings, as well as random key >> bindings. >> >> >>> > That >> >> >>> > being said, we should be able to execute Javascript to do what we >> >> need >> >> >>> > instead of testing touch and click events, which in theory should >> >> have >> >> >>> > been >> >> >>> > tested as part of Android's CTS. (No idea if this ever happens). >> >> >>> > >> >> >>> > >> >> >>> > On Fri, Nov 2, 2012 at 5:58 PM, Simon MacDonald >> >> >>> > <simon.macdon...@gmail.com>wrote: >> >> >>> > >> >> >>> > > That's great Joe. I was under the impression that the Android >> repo >> >> >>> > > tests >> >> >>> > > were still dependent on a jar we didn't have access to. I'll >> make >> >> >>> > > sure >> >> >>> > > running the tests is part of my regular process and "gasp" I >> will >> >> >>> > > even >> >> >>> > > write a few. >> >> >>> > > >> >> >>> > > Simon Mac Donald >> >> >>> > > http://hi.im/simonmacdonald >> >> >>> > > >> >> >>> > > >> >> >>> > > On Fri, Nov 2, 2012 at 4:38 PM, Joe Bowser <bows...@gmail.com> >> >> wrote: >> >> >>> > > >> >> >>> > > > Hey >> >> >>> > > > >> >> >>> > > > After the last scare with CordovaWebView, I want to know if >> >> >>> > > > everyone >> >> >>> > who >> >> >>> > > > commits on Android can run the tests that are currently >> committed >> >> >>> > > > with >> >> >>> > > > Android? You have to be able to do both things with the tests >> in >> >> >>> > Eclipse: >> >> >>> > > > >> >> >>> > > > 1. Run the test as an Android Application >> >> >>> > > > 2. Run the Android JUnit Tests >> >> >>> > > > >> >> >>> > > > There is a command-line method to do this, but honestly if >> you're >> >> >>> > finding >> >> >>> > > > failures here, you'll probably need Eclipse anyway to debug >> the >> >> >>> > > > Java >> >> >>> > > code. >> >> >>> > > > If you're super hardcore, I believe that this command is >> still >> >> in >> >> >>> > > > the >> >> >>> > > wiki >> >> >>> > > > here: >> >> >>> > > > >> >> >>> > > > http://wiki.apache.org/cordova/RunningTests >> >> >>> > > > >> >> >>> > > > Also, are other platforms doing testing outside of mobile-spec >> >> >>> > > > Jasmine >> >> >>> > > > tests? What impact would this have on CI work? I'm pretty >> sure >> >> >>> > > > that >> >> >>> > the >> >> >>> > > > Android tests should be relatively simple. >> >> >>> > > > >> >> >>> > > > Joe >> >> >>> > > > >> >> >>> > > >> >> >>> > >> >> >> >> >> >> >> >> > >> >> >>