Re: [Android] Can everyone run the tests?
Right. I just copy local.properties from framework, but yeah, that's
one of those housekeeping steps.
On Fri, Nov 16, 2012 at 1:36 PM, Andrew Grieve wrote:
> I think you need to run it so that it sets the SDK path in local.properties.
>
>
> On Fri, Nov 16, 2012 at 4:23 PM, Joe Bowser wrote:
>>
>> The project should be updated. Do you have the latest code?
>>
>> On Fri, Nov 16, 2012 at 12:40 PM, Andrew Grieve
>> wrote:
>> > Okay, actually, command line instructions were a bit off, (framework
>> > directory ---> test directory) + need to adb update project. I'll
>> > (update
>> > wiki)
>> >
>> > But! Tests all passed for me except on my 4.0.1 emulator.
>> >
>> >
>> > On Fri, Nov 16, 2012 at 2:58 PM, Andrew Grieve
>> > wrote:
>> >
>> >> Thanks Joe. Instructions look good!
>> >>
>> >> I asked around and got some advice for making webview's suck less in
>> >> the
>> >> context of destroying & recreating them:
>> >>
>> >> - create your WebView programmatically and not via xml layout
>> >> - unregister all JS interfaces on 3.0+ via call via reflection
>> >> to: type.getMethod("removeJavascriptInterface", String.class)
>> >> - explicitly call WebView.destroy(), destroyDrawingCache()
>> >>
>> >> Not sure how necessary these things are, but they are leads anyways.
>> >>
>> >>
>> >> On Fri, Nov 16, 2012 at 1:50 PM, Joe Bowser wrote:
>> >>
>> >>> BTW: The Wiki has been updated:
>> >>>
>> >>> http://wiki.apache.org/cordova/RunningTests
>> >>>
>> >>> On Fri, Nov 16, 2012 at 10:49 AM, Joe Bowser
>> >>> wrote:
>> >>> > Hey
>> >>> >
>> >>> > I noticed that the tests are failing. Worse, the tests are failing
>> >>> > randomly and they're not failing all the time. I think we leak a
>> >>> > receiver when using a CordovaWebView, so I'll have to investigate
>> >>> > this, since it's causing this spectacular WebKit crash. Really,
>> >>> > this
>> >>> > is a pretty EPIC FAIL of WebView. I'll be looking at that. Let me
>> >>> > know if you can reproduce the same epic fail on your end.
>> >>> >
>> >>> > On Fri, Nov 16, 2012 at 10:13 AM, Joe Bowser
>> >>> > wrote:
>> >>> >> Honestly, running JUnit Tests in Eclipse is pretty trivial, as is
>> >>> >> running these from the command line. I just tried it and here's
>> >>> >> the
>> >>> >> command:
>> >>> >>
>> >>> >> adb shell am instrument -w
>> >>> >> org.apache.cordova.test/android.test.InstrumentationTestRunner
>> >>> >>
>> >>> >> On Thu, Nov 15, 2012 at 7:32 PM, Andrew Grieve
>> >>> >>
>> >>> wrote:
>> >>> >>> Awesome. The steps to run it in eclipse would be a good addition
>> >>> >>> as
>> >>> well.
>> >>> >>> I'll sign up to add the iOS unit test instructions.
>> >>> >>>
>> >>> >>>
>> >>> >>> On Thu, Nov 15, 2012 at 8:11 PM, Joe Bowser
>> >>> wrote:
>> >>> >>>
>> >>> Web Driver is not necessary to run the tests. I'll get the
>> >>> command
>> >>> line
>> >>> version working tomorrow.
>> >>> On Nov 15, 2012 5:05 PM, "Andrew Grieve"
>> >>> wrote:
>> >>>
>> >>> > Started to update wiki instructions... but what is the correct
>> >>> last step?
>> >>> >
>> >>> > === To run these tests from the command line: ===
>> >>> > 1. Install "Google Web Driver" through the Android SKD Manager
>> >>> > 1. Copy the
>> >>> > extras/google/webdriver/android_webdriver_library.jar
>> >>> from
>> >>> the
>> >>> > Android SDK into the framework/libs directory
>> >>> > 1. Build Cordova by running "ant" from within the framework
>> >>> directory
>> >>> > 1. Run the following command in the framework directory with a
>> >>> device
>> >>> > attached or emulator running:
>> >>> > adb shell am instrument -w
>> >>> > com.phonegap/android.test.InstrumentationTestRunner
>> >>> >
>> >>> >
>> >>> >
>> >>> > On Wed, Nov 14, 2012 at 9:24 PM, Andrew Grieve <
>> >>> agri...@chromium.org>
>> >>> > wrote:
>> >>> >
>> >>> > > Tried to follow the command-line instructions but get:
>> >>> > >
>> >>> > >
>> >>> > > agrieve@dhcp-172-23-181-44~/git/incubator-cordova-android/framework
>> >>> > > (asdf) $ adb shell am instrument -w
>> >>> > > com.phonegap/android.test.InstrumentationTestRunner
>> >>> > > INSTRUMENTATION_STATUS: id=ActivityManagerService
>> >>> > > INSTRUMENTATION_STATUS: Error=Unable to find instrumentation
>> >>> info for:
>> >>> > >
>> >>> ComponentInfo{com.phonegap/android.test.InstrumentationTestRunner}
>> >>> > > INSTRUMENTATION_STATUS_CODE: -1
>> >>> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
>> >>> > > com.phonegap/android.test.InstrumentationTestRunner
>> >>> > >
>> >>> > > Changing to org.apache.cordova:
>> >>> > >
>> >>> > > agrieve@dhcp-172-23-181-44~/git/incubator-cordova-android/framework
>> >>> > > (asdf) $ adb shell am instrument -w
>> >>> > > org.apache.cordova/android.test.InstrumentationTestRunner
>> >>> > > android.util.AndroidException
Re: [Android] Can everyone run the tests?
I think you need to run it so that it sets the SDK path in local.properties.
On Fri, Nov 16, 2012 at 4:23 PM, Joe Bowser wrote:
> The project should be updated. Do you have the latest code?
>
> On Fri, Nov 16, 2012 at 12:40 PM, Andrew Grieve
> wrote:
> > Okay, actually, command line instructions were a bit off, (framework
> > directory ---> test directory) + need to adb update project. I'll (update
> > wiki)
> >
> > But! Tests all passed for me except on my 4.0.1 emulator.
> >
> >
> > On Fri, Nov 16, 2012 at 2:58 PM, Andrew Grieve
> wrote:
> >
> >> Thanks Joe. Instructions look good!
> >>
> >> I asked around and got some advice for making webview's suck less in the
> >> context of destroying & recreating them:
> >>
> >> - create your WebView programmatically and not via xml layout
> >> - unregister all JS interfaces on 3.0+ via call via reflection
> >> to: type.getMethod("removeJavascriptInterface", String.class)
> >> - explicitly call WebView.destroy(), destroyDrawingCache()
> >>
> >> Not sure how necessary these things are, but they are leads anyways.
> >>
> >>
> >> On Fri, Nov 16, 2012 at 1:50 PM, Joe Bowser wrote:
> >>
> >>> BTW: The Wiki has been updated:
> >>>
> >>> http://wiki.apache.org/cordova/RunningTests
> >>>
> >>> On Fri, Nov 16, 2012 at 10:49 AM, Joe Bowser
> wrote:
> >>> > Hey
> >>> >
> >>> > I noticed that the tests are failing. Worse, the tests are failing
> >>> > randomly and they're not failing all the time. I think we leak a
> >>> > receiver when using a CordovaWebView, so I'll have to investigate
> >>> > this, since it's causing this spectacular WebKit crash. Really, this
> >>> > is a pretty EPIC FAIL of WebView. I'll be looking at that. Let me
> >>> > know if you can reproduce the same epic fail on your end.
> >>> >
> >>> > On Fri, Nov 16, 2012 at 10:13 AM, Joe Bowser
> wrote:
> >>> >> Honestly, running JUnit Tests in Eclipse is pretty trivial, as is
> >>> >> running these from the command line. I just tried it and here's the
> >>> >> command:
> >>> >>
> >>> >> adb shell am instrument -w
> >>> >> org.apache.cordova.test/android.test.InstrumentationTestRunner
> >>> >>
> >>> >> On Thu, Nov 15, 2012 at 7:32 PM, Andrew Grieve <
> agri...@chromium.org>
> >>> wrote:
> >>> >>> Awesome. The steps to run it in eclipse would be a good addition as
> >>> well.
> >>> >>> I'll sign up to add the iOS unit test instructions.
> >>> >>>
> >>> >>>
> >>> >>> On Thu, Nov 15, 2012 at 8:11 PM, Joe Bowser
> >>> wrote:
> >>> >>>
> >>> Web Driver is not necessary to run the tests. I'll get the
> command
> >>> line
> >>> version working tomorrow.
> >>> On Nov 15, 2012 5:05 PM, "Andrew Grieve"
> >>> wrote:
> >>>
> >>> > Started to update wiki instructions... but what is the correct
> >>> last step?
> >>> >
> >>> > === To run these tests from the command line: ===
> >>> > 1. Install "Google Web Driver" through the Android SKD Manager
> >>> > 1. Copy the
> extras/google/webdriver/android_webdriver_library.jar
> >>> from
> >>> the
> >>> > Android SDK into the framework/libs directory
> >>> > 1. Build Cordova by running "ant" from within the framework
> >>> directory
> >>> > 1. Run the following command in the framework directory with a
> >>> device
> >>> > attached or emulator running:
> >>> > adb shell am instrument -w
> >>> > com.phonegap/android.test.InstrumentationTestRunner
> >>> >
> >>> >
> >>> >
> >>> > On Wed, Nov 14, 2012 at 9:24 PM, Andrew Grieve <
> >>> agri...@chromium.org>
> >>> > wrote:
> >>> >
> >>> > > Tried to follow the command-line instructions but get:
> >>> > >
> >>> > > agrieve@dhcp-172-23-181-44
> ~/git/incubator-cordova-android/framework
> >>> > > (asdf) $ adb shell am instrument -w
> >>> > > com.phonegap/android.test.InstrumentationTestRunner
> >>> > > INSTRUMENTATION_STATUS: id=ActivityManagerService
> >>> > > INSTRUMENTATION_STATUS: Error=Unable to find instrumentation
> >>> info for:
> >>> > >
> >>> ComponentInfo{com.phonegap/android.test.InstrumentationTestRunner}
> >>> > > INSTRUMENTATION_STATUS_CODE: -1
> >>> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
> >>> > > com.phonegap/android.test.InstrumentationTestRunner
> >>> > >
> >>> > > Changing to org.apache.cordova:
> >>> > > agrieve@dhcp-172-23-181-44
> ~/git/incubator-cordova-android/framework
> >>> > > (asdf) $ adb shell am instrument -w
> >>> > > org.apache.cordova/android.test.InstrumentationTestRunner
> >>> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
> >>> > > org.apache.cordova/android.test.InstrumentationTestRunner
> >>> > >
> >>> > > On Wed, Nov 14, 2012 at 4:41 PM, Simon MacDonald <
> >>> > > simon.macdon...@gmail.com> wrote:
> >>> > >
> >>> > >> Yup, it passed when I ran it and only it.
> >>> > >>
> >>> > >> Simon Mac Donald
> >>> >
Re: [Android] Can everyone run the tests?
The project should be updated. Do you have the latest code?
On Fri, Nov 16, 2012 at 12:40 PM, Andrew Grieve wrote:
> Okay, actually, command line instructions were a bit off, (framework
> directory ---> test directory) + need to adb update project. I'll (update
> wiki)
>
> But! Tests all passed for me except on my 4.0.1 emulator.
>
>
> On Fri, Nov 16, 2012 at 2:58 PM, Andrew Grieve wrote:
>
>> Thanks Joe. Instructions look good!
>>
>> I asked around and got some advice for making webview's suck less in the
>> context of destroying & recreating them:
>>
>> - create your WebView programmatically and not via xml layout
>> - unregister all JS interfaces on 3.0+ via call via reflection
>> to: type.getMethod("removeJavascriptInterface", String.class)
>> - explicitly call WebView.destroy(), destroyDrawingCache()
>>
>> Not sure how necessary these things are, but they are leads anyways.
>>
>>
>> On Fri, Nov 16, 2012 at 1:50 PM, Joe Bowser wrote:
>>
>>> BTW: The Wiki has been updated:
>>>
>>> http://wiki.apache.org/cordova/RunningTests
>>>
>>> On Fri, Nov 16, 2012 at 10:49 AM, Joe Bowser wrote:
>>> > Hey
>>> >
>>> > I noticed that the tests are failing. Worse, the tests are failing
>>> > randomly and they're not failing all the time. I think we leak a
>>> > receiver when using a CordovaWebView, so I'll have to investigate
>>> > this, since it's causing this spectacular WebKit crash. Really, this
>>> > is a pretty EPIC FAIL of WebView. I'll be looking at that. Let me
>>> > know if you can reproduce the same epic fail on your end.
>>> >
>>> > On Fri, Nov 16, 2012 at 10:13 AM, Joe Bowser wrote:
>>> >> Honestly, running JUnit Tests in Eclipse is pretty trivial, as is
>>> >> running these from the command line. I just tried it and here's the
>>> >> command:
>>> >>
>>> >> adb shell am instrument -w
>>> >> org.apache.cordova.test/android.test.InstrumentationTestRunner
>>> >>
>>> >> On Thu, Nov 15, 2012 at 7:32 PM, Andrew Grieve
>>> wrote:
>>> >>> Awesome. The steps to run it in eclipse would be a good addition as
>>> well.
>>> >>> I'll sign up to add the iOS unit test instructions.
>>> >>>
>>> >>>
>>> >>> On Thu, Nov 15, 2012 at 8:11 PM, Joe Bowser
>>> wrote:
>>> >>>
>>> Web Driver is not necessary to run the tests. I'll get the command
>>> line
>>> version working tomorrow.
>>> On Nov 15, 2012 5:05 PM, "Andrew Grieve"
>>> wrote:
>>>
>>> > Started to update wiki instructions... but what is the correct
>>> last step?
>>> >
>>> > === To run these tests from the command line: ===
>>> > 1. Install "Google Web Driver" through the Android SKD Manager
>>> > 1. Copy the extras/google/webdriver/android_webdriver_library.jar
>>> from
>>> the
>>> > Android SDK into the framework/libs directory
>>> > 1. Build Cordova by running "ant" from within the framework
>>> directory
>>> > 1. Run the following command in the framework directory with a
>>> device
>>> > attached or emulator running:
>>> > adb shell am instrument -w
>>> > com.phonegap/android.test.InstrumentationTestRunner
>>> >
>>> >
>>> >
>>> > On Wed, Nov 14, 2012 at 9:24 PM, Andrew Grieve <
>>> agri...@chromium.org>
>>> > wrote:
>>> >
>>> > > Tried to follow the command-line instructions but get:
>>> > >
>>> > > agrieve@dhcp-172-23-181-44~/git/incubator-cordova-android/framework
>>> > > (asdf) $ adb shell am instrument -w
>>> > > com.phonegap/android.test.InstrumentationTestRunner
>>> > > INSTRUMENTATION_STATUS: id=ActivityManagerService
>>> > > INSTRUMENTATION_STATUS: Error=Unable to find instrumentation
>>> info for:
>>> > >
>>> ComponentInfo{com.phonegap/android.test.InstrumentationTestRunner}
>>> > > INSTRUMENTATION_STATUS_CODE: -1
>>> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
>>> > > com.phonegap/android.test.InstrumentationTestRunner
>>> > >
>>> > > Changing to org.apache.cordova:
>>> > > agrieve@dhcp-172-23-181-44~/git/incubator-cordova-android/framework
>>> > > (asdf) $ adb shell am instrument -w
>>> > > org.apache.cordova/android.test.InstrumentationTestRunner
>>> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
>>> > > org.apache.cordova/android.test.InstrumentationTestRunner
>>> > >
>>> > > On Wed, Nov 14, 2012 at 4:41 PM, Simon MacDonald <
>>> > > simon.macdon...@gmail.com> wrote:
>>> > >
>>> > >> Yup, it passed when I ran it and only it.
>>> > >>
>>> > >> Simon Mac Donald
>>> > >> http://hi.im/simonmacdonald
>>> > >>
>>> > >>
>>> > >> On Wed, Nov 14, 2012 at 4:35 PM, Joe Bowser
>>> wrote:
>>> > >>
>>> > >> > How can testPreconditions fail, but testViaLoadUrl pass? Can
>>> you run
>>> > >> > the test by itself? testViaHref is known to fail, and there's
>>> an
>>> issue
>>> > >> > open about that bug.
>>> > >> >
>>> > >>
>>
Re: [Android] Can everyone run the tests?
Okay, actually, command line instructions were a bit off, (framework
directory ---> test directory) + need to adb update project. I'll (update
wiki)
But! Tests all passed for me except on my 4.0.1 emulator.
On Fri, Nov 16, 2012 at 2:58 PM, Andrew Grieve wrote:
> Thanks Joe. Instructions look good!
>
> I asked around and got some advice for making webview's suck less in the
> context of destroying & recreating them:
>
> - create your WebView programmatically and not via xml layout
> - unregister all JS interfaces on 3.0+ via call via reflection
> to: type.getMethod("removeJavascriptInterface", String.class)
> - explicitly call WebView.destroy(), destroyDrawingCache()
>
> Not sure how necessary these things are, but they are leads anyways.
>
>
> On Fri, Nov 16, 2012 at 1:50 PM, Joe Bowser wrote:
>
>> BTW: The Wiki has been updated:
>>
>> http://wiki.apache.org/cordova/RunningTests
>>
>> On Fri, Nov 16, 2012 at 10:49 AM, Joe Bowser wrote:
>> > Hey
>> >
>> > I noticed that the tests are failing. Worse, the tests are failing
>> > randomly and they're not failing all the time. I think we leak a
>> > receiver when using a CordovaWebView, so I'll have to investigate
>> > this, since it's causing this spectacular WebKit crash. Really, this
>> > is a pretty EPIC FAIL of WebView. I'll be looking at that. Let me
>> > know if you can reproduce the same epic fail on your end.
>> >
>> > On Fri, Nov 16, 2012 at 10:13 AM, Joe Bowser wrote:
>> >> Honestly, running JUnit Tests in Eclipse is pretty trivial, as is
>> >> running these from the command line. I just tried it and here's the
>> >> command:
>> >>
>> >> adb shell am instrument -w
>> >> org.apache.cordova.test/android.test.InstrumentationTestRunner
>> >>
>> >> On Thu, Nov 15, 2012 at 7:32 PM, Andrew Grieve
>> wrote:
>> >>> Awesome. The steps to run it in eclipse would be a good addition as
>> well.
>> >>> I'll sign up to add the iOS unit test instructions.
>> >>>
>> >>>
>> >>> On Thu, Nov 15, 2012 at 8:11 PM, Joe Bowser
>> wrote:
>> >>>
>> Web Driver is not necessary to run the tests. I'll get the command
>> line
>> version working tomorrow.
>> On Nov 15, 2012 5:05 PM, "Andrew Grieve"
>> wrote:
>>
>> > Started to update wiki instructions... but what is the correct
>> last step?
>> >
>> > === To run these tests from the command line: ===
>> > 1. Install "Google Web Driver" through the Android SKD Manager
>> > 1. Copy the extras/google/webdriver/android_webdriver_library.jar
>> from
>> the
>> > Android SDK into the framework/libs directory
>> > 1. Build Cordova by running "ant" from within the framework
>> directory
>> > 1. Run the following command in the framework directory with a
>> device
>> > attached or emulator running:
>> > adb shell am instrument -w
>> > com.phonegap/android.test.InstrumentationTestRunner
>> >
>> >
>> >
>> > On Wed, Nov 14, 2012 at 9:24 PM, Andrew Grieve <
>> agri...@chromium.org>
>> > wrote:
>> >
>> > > Tried to follow the command-line instructions but get:
>> > >
>> > > agrieve@dhcp-172-23-181-44~/git/incubator-cordova-android/framework
>> > > (asdf) $ adb shell am instrument -w
>> > > com.phonegap/android.test.InstrumentationTestRunner
>> > > INSTRUMENTATION_STATUS: id=ActivityManagerService
>> > > INSTRUMENTATION_STATUS: Error=Unable to find instrumentation
>> info for:
>> > >
>> ComponentInfo{com.phonegap/android.test.InstrumentationTestRunner}
>> > > INSTRUMENTATION_STATUS_CODE: -1
>> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
>> > > com.phonegap/android.test.InstrumentationTestRunner
>> > >
>> > > Changing to org.apache.cordova:
>> > > agrieve@dhcp-172-23-181-44~/git/incubator-cordova-android/framework
>> > > (asdf) $ adb shell am instrument -w
>> > > org.apache.cordova/android.test.InstrumentationTestRunner
>> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
>> > > org.apache.cordova/android.test.InstrumentationTestRunner
>> > >
>> > > On Wed, Nov 14, 2012 at 4:41 PM, Simon MacDonald <
>> > > simon.macdon...@gmail.com> wrote:
>> > >
>> > >> Yup, it passed when I ran it and only it.
>> > >>
>> > >> Simon Mac Donald
>> > >> http://hi.im/simonmacdonald
>> > >>
>> > >>
>> > >> On Wed, Nov 14, 2012 at 4:35 PM, Joe Bowser
>> wrote:
>> > >>
>> > >> > How can testPreconditions fail, but testViaLoadUrl pass? Can
>> you run
>> > >> > the test by itself? testViaHref is known to fail, and there's
>> an
>> issue
>> > >> > open about that bug.
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>>
>
>
Re: [Android] Can everyone run the tests?
Thanks Joe. Instructions look good!
I asked around and got some advice for making webview's suck less in the
context of destroying & recreating them:
- create your WebView programmatically and not via xml layout
- unregister all JS interfaces on 3.0+ via call via reflection
to: type.getMethod("removeJavascriptInterface", String.class)
- explicitly call WebView.destroy(), destroyDrawingCache()
Not sure how necessary these things are, but they are leads anyways.
On Fri, Nov 16, 2012 at 1:50 PM, Joe Bowser wrote:
> BTW: The Wiki has been updated:
>
> http://wiki.apache.org/cordova/RunningTests
>
> On Fri, Nov 16, 2012 at 10:49 AM, Joe Bowser wrote:
> > Hey
> >
> > I noticed that the tests are failing. Worse, the tests are failing
> > randomly and they're not failing all the time. I think we leak a
> > receiver when using a CordovaWebView, so I'll have to investigate
> > this, since it's causing this spectacular WebKit crash. Really, this
> > is a pretty EPIC FAIL of WebView. I'll be looking at that. Let me
> > know if you can reproduce the same epic fail on your end.
> >
> > On Fri, Nov 16, 2012 at 10:13 AM, Joe Bowser wrote:
> >> Honestly, running JUnit Tests in Eclipse is pretty trivial, as is
> >> running these from the command line. I just tried it and here's the
> >> command:
> >>
> >> adb shell am instrument -w
> >> org.apache.cordova.test/android.test.InstrumentationTestRunner
> >>
> >> On Thu, Nov 15, 2012 at 7:32 PM, Andrew Grieve
> wrote:
> >>> Awesome. The steps to run it in eclipse would be a good addition as
> well.
> >>> I'll sign up to add the iOS unit test instructions.
> >>>
> >>>
> >>> On Thu, Nov 15, 2012 at 8:11 PM, Joe Bowser wrote:
> >>>
> Web Driver is not necessary to run the tests. I'll get the command
> line
> version working tomorrow.
> On Nov 15, 2012 5:05 PM, "Andrew Grieve"
> wrote:
>
> > Started to update wiki instructions... but what is the correct last
> step?
> >
> > === To run these tests from the command line: ===
> > 1. Install "Google Web Driver" through the Android SKD Manager
> > 1. Copy the extras/google/webdriver/android_webdriver_library.jar
> from
> the
> > Android SDK into the framework/libs directory
> > 1. Build Cordova by running "ant" from within the framework
> directory
> > 1. Run the following command in the framework directory with a
> device
> > attached or emulator running:
> > adb shell am instrument -w
> > com.phonegap/android.test.InstrumentationTestRunner
> >
> >
> >
> > On Wed, Nov 14, 2012 at 9:24 PM, Andrew Grieve <
> agri...@chromium.org>
> > wrote:
> >
> > > Tried to follow the command-line instructions but get:
> > >
> > > agrieve@dhcp-172-23-181-44~/git/incubator-cordova-android/framework
> > > (asdf) $ adb shell am instrument -w
> > > com.phonegap/android.test.InstrumentationTestRunner
> > > INSTRUMENTATION_STATUS: id=ActivityManagerService
> > > INSTRUMENTATION_STATUS: Error=Unable to find instrumentation info
> for:
> > > ComponentInfo{com.phonegap/android.test.InstrumentationTestRunner}
> > > INSTRUMENTATION_STATUS_CODE: -1
> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
> > > com.phonegap/android.test.InstrumentationTestRunner
> > >
> > > Changing to org.apache.cordova:
> > > agrieve@dhcp-172-23-181-44~/git/incubator-cordova-android/framework
> > > (asdf) $ adb shell am instrument -w
> > > org.apache.cordova/android.test.InstrumentationTestRunner
> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
> > > org.apache.cordova/android.test.InstrumentationTestRunner
> > >
> > > On Wed, Nov 14, 2012 at 4:41 PM, Simon MacDonald <
> > > simon.macdon...@gmail.com> wrote:
> > >
> > >> Yup, it passed when I ran it and only it.
> > >>
> > >> Simon Mac Donald
> > >> http://hi.im/simonmacdonald
> > >>
> > >>
> > >> On Wed, Nov 14, 2012 at 4:35 PM, Joe Bowser
> wrote:
> > >>
> > >> > How can testPreconditions fail, but testViaLoadUrl pass? Can
> you run
> > >> > the test by itself? testViaHref is known to fail, and there's
> an
> issue
> > >> > open about that bug.
> > >> >
> > >>
> > >
> > >
> >
>
>
Re: [Android] Can everyone run the tests?
BTW: The Wiki has been updated:
http://wiki.apache.org/cordova/RunningTests
On Fri, Nov 16, 2012 at 10:49 AM, Joe Bowser wrote:
> Hey
>
> I noticed that the tests are failing. Worse, the tests are failing
> randomly and they're not failing all the time. I think we leak a
> receiver when using a CordovaWebView, so I'll have to investigate
> this, since it's causing this spectacular WebKit crash. Really, this
> is a pretty EPIC FAIL of WebView. I'll be looking at that. Let me
> know if you can reproduce the same epic fail on your end.
>
> On Fri, Nov 16, 2012 at 10:13 AM, Joe Bowser wrote:
>> Honestly, running JUnit Tests in Eclipse is pretty trivial, as is
>> running these from the command line. I just tried it and here's the
>> command:
>>
>> adb shell am instrument -w
>> org.apache.cordova.test/android.test.InstrumentationTestRunner
>>
>> On Thu, Nov 15, 2012 at 7:32 PM, Andrew Grieve wrote:
>>> Awesome. The steps to run it in eclipse would be a good addition as well.
>>> I'll sign up to add the iOS unit test instructions.
>>>
>>>
>>> On Thu, Nov 15, 2012 at 8:11 PM, Joe Bowser wrote:
>>>
Web Driver is not necessary to run the tests. I'll get the command line
version working tomorrow.
On Nov 15, 2012 5:05 PM, "Andrew Grieve" wrote:
> Started to update wiki instructions... but what is the correct last step?
>
> === To run these tests from the command line: ===
> 1. Install "Google Web Driver" through the Android SKD Manager
> 1. Copy the extras/google/webdriver/android_webdriver_library.jar from
the
> Android SDK into the framework/libs directory
> 1. Build Cordova by running "ant" from within the framework directory
> 1. Run the following command in the framework directory with a device
> attached or emulator running:
> adb shell am instrument -w
> com.phonegap/android.test.InstrumentationTestRunner
>
>
>
> On Wed, Nov 14, 2012 at 9:24 PM, Andrew Grieve
> wrote:
>
> > Tried to follow the command-line instructions but get:
> >
> > agrieve@dhcp-172-23-181-44 ~/git/incubator-cordova-android/framework
> > (asdf) $ adb shell am instrument -w
> > com.phonegap/android.test.InstrumentationTestRunner
> > INSTRUMENTATION_STATUS: id=ActivityManagerService
> > INSTRUMENTATION_STATUS: Error=Unable to find instrumentation info for:
> > ComponentInfo{com.phonegap/android.test.InstrumentationTestRunner}
> > INSTRUMENTATION_STATUS_CODE: -1
> > android.util.AndroidException: INSTRUMENTATION_FAILED:
> > com.phonegap/android.test.InstrumentationTestRunner
> >
> > Changing to org.apache.cordova:
> > agrieve@dhcp-172-23-181-44 ~/git/incubator-cordova-android/framework
> > (asdf) $ adb shell am instrument -w
> > org.apache.cordova/android.test.InstrumentationTestRunner
> > android.util.AndroidException: INSTRUMENTATION_FAILED:
> > org.apache.cordova/android.test.InstrumentationTestRunner
> >
> > On Wed, Nov 14, 2012 at 4:41 PM, Simon MacDonald <
> > simon.macdon...@gmail.com> wrote:
> >
> >> Yup, it passed when I ran it and only it.
> >>
> >> Simon Mac Donald
> >> http://hi.im/simonmacdonald
> >>
> >>
> >> On Wed, Nov 14, 2012 at 4:35 PM, Joe Bowser
wrote:
> >>
> >> > How can testPreconditions fail, but testViaLoadUrl pass? Can you run
> >> > the test by itself? testViaHref is known to fail, and there's an
issue
> >> > open about that bug.
> >> >
> >>
> >
> >
>
Re: [Android] Can everyone run the tests?
Hey
I noticed that the tests are failing. Worse, the tests are failing
randomly and they're not failing all the time. I think we leak a
receiver when using a CordovaWebView, so I'll have to investigate
this, since it's causing this spectacular WebKit crash. Really, this
is a pretty EPIC FAIL of WebView. I'll be looking at that. Let me
know if you can reproduce the same epic fail on your end.
On Fri, Nov 16, 2012 at 10:13 AM, Joe Bowser wrote:
> Honestly, running JUnit Tests in Eclipse is pretty trivial, as is
> running these from the command line. I just tried it and here's the
> command:
>
> adb shell am instrument -w
> org.apache.cordova.test/android.test.InstrumentationTestRunner
>
> On Thu, Nov 15, 2012 at 7:32 PM, Andrew Grieve wrote:
>> Awesome. The steps to run it in eclipse would be a good addition as well.
>> I'll sign up to add the iOS unit test instructions.
>>
>>
>> On Thu, Nov 15, 2012 at 8:11 PM, Joe Bowser wrote:
>>
>>> Web Driver is not necessary to run the tests. I'll get the command line
>>> version working tomorrow.
>>> On Nov 15, 2012 5:05 PM, "Andrew Grieve" wrote:
>>>
>>> > Started to update wiki instructions... but what is the correct last step?
>>> >
>>> > === To run these tests from the command line: ===
>>> > 1. Install "Google Web Driver" through the Android SKD Manager
>>> > 1. Copy the extras/google/webdriver/android_webdriver_library.jar from
>>> the
>>> > Android SDK into the framework/libs directory
>>> > 1. Build Cordova by running "ant" from within the framework directory
>>> > 1. Run the following command in the framework directory with a device
>>> > attached or emulator running:
>>> > adb shell am instrument -w
>>> > com.phonegap/android.test.InstrumentationTestRunner
>>> >
>>> >
>>> >
>>> > On Wed, Nov 14, 2012 at 9:24 PM, Andrew Grieve
>>> > wrote:
>>> >
>>> > > Tried to follow the command-line instructions but get:
>>> > >
>>> > > agrieve@dhcp-172-23-181-44 ~/git/incubator-cordova-android/framework
>>> > > (asdf) $ adb shell am instrument -w
>>> > > com.phonegap/android.test.InstrumentationTestRunner
>>> > > INSTRUMENTATION_STATUS: id=ActivityManagerService
>>> > > INSTRUMENTATION_STATUS: Error=Unable to find instrumentation info for:
>>> > > ComponentInfo{com.phonegap/android.test.InstrumentationTestRunner}
>>> > > INSTRUMENTATION_STATUS_CODE: -1
>>> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
>>> > > com.phonegap/android.test.InstrumentationTestRunner
>>> > >
>>> > > Changing to org.apache.cordova:
>>> > > agrieve@dhcp-172-23-181-44 ~/git/incubator-cordova-android/framework
>>> > > (asdf) $ adb shell am instrument -w
>>> > > org.apache.cordova/android.test.InstrumentationTestRunner
>>> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
>>> > > org.apache.cordova/android.test.InstrumentationTestRunner
>>> > >
>>> > > On Wed, Nov 14, 2012 at 4:41 PM, Simon MacDonald <
>>> > > simon.macdon...@gmail.com> wrote:
>>> > >
>>> > >> Yup, it passed when I ran it and only it.
>>> > >>
>>> > >> Simon Mac Donald
>>> > >> http://hi.im/simonmacdonald
>>> > >>
>>> > >>
>>> > >> On Wed, Nov 14, 2012 at 4:35 PM, Joe Bowser
>>> wrote:
>>> > >>
>>> > >> > How can testPreconditions fail, but testViaLoadUrl pass? Can you run
>>> > >> > the test by itself? testViaHref is known to fail, and there's an
>>> issue
>>> > >> > open about that bug.
>>> > >> >
>>> > >>
>>> > >
>>> > >
>>> >
>>>
Re: [Android] Can everyone run the tests?
Honestly, running JUnit Tests in Eclipse is pretty trivial, as is
running these from the command line. I just tried it and here's the
command:
adb shell am instrument -w
org.apache.cordova.test/android.test.InstrumentationTestRunner
On Thu, Nov 15, 2012 at 7:32 PM, Andrew Grieve wrote:
> Awesome. The steps to run it in eclipse would be a good addition as well.
> I'll sign up to add the iOS unit test instructions.
>
>
> On Thu, Nov 15, 2012 at 8:11 PM, Joe Bowser wrote:
>
>> Web Driver is not necessary to run the tests. I'll get the command line
>> version working tomorrow.
>> On Nov 15, 2012 5:05 PM, "Andrew Grieve" wrote:
>>
>> > Started to update wiki instructions... but what is the correct last step?
>> >
>> > === To run these tests from the command line: ===
>> > 1. Install "Google Web Driver" through the Android SKD Manager
>> > 1. Copy the extras/google/webdriver/android_webdriver_library.jar from
>> the
>> > Android SDK into the framework/libs directory
>> > 1. Build Cordova by running "ant" from within the framework directory
>> > 1. Run the following command in the framework directory with a device
>> > attached or emulator running:
>> > adb shell am instrument -w
>> > com.phonegap/android.test.InstrumentationTestRunner
>> >
>> >
>> >
>> > On Wed, Nov 14, 2012 at 9:24 PM, Andrew Grieve
>> > wrote:
>> >
>> > > Tried to follow the command-line instructions but get:
>> > >
>> > > agrieve@dhcp-172-23-181-44 ~/git/incubator-cordova-android/framework
>> > > (asdf) $ adb shell am instrument -w
>> > > com.phonegap/android.test.InstrumentationTestRunner
>> > > INSTRUMENTATION_STATUS: id=ActivityManagerService
>> > > INSTRUMENTATION_STATUS: Error=Unable to find instrumentation info for:
>> > > ComponentInfo{com.phonegap/android.test.InstrumentationTestRunner}
>> > > INSTRUMENTATION_STATUS_CODE: -1
>> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
>> > > com.phonegap/android.test.InstrumentationTestRunner
>> > >
>> > > Changing to org.apache.cordova:
>> > > agrieve@dhcp-172-23-181-44 ~/git/incubator-cordova-android/framework
>> > > (asdf) $ adb shell am instrument -w
>> > > org.apache.cordova/android.test.InstrumentationTestRunner
>> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
>> > > org.apache.cordova/android.test.InstrumentationTestRunner
>> > >
>> > > On Wed, Nov 14, 2012 at 4:41 PM, Simon MacDonald <
>> > > simon.macdon...@gmail.com> wrote:
>> > >
>> > >> Yup, it passed when I ran it and only it.
>> > >>
>> > >> Simon Mac Donald
>> > >> http://hi.im/simonmacdonald
>> > >>
>> > >>
>> > >> On Wed, Nov 14, 2012 at 4:35 PM, Joe Bowser
>> wrote:
>> > >>
>> > >> > How can testPreconditions fail, but testViaLoadUrl pass? Can you run
>> > >> > the test by itself? testViaHref is known to fail, and there's an
>> issue
>> > >> > open about that bug.
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
Re: [Android] Can everyone run the tests?
Awesome. The steps to run it in eclipse would be a good addition as well.
I'll sign up to add the iOS unit test instructions.
On Thu, Nov 15, 2012 at 8:11 PM, Joe Bowser wrote:
> Web Driver is not necessary to run the tests. I'll get the command line
> version working tomorrow.
> On Nov 15, 2012 5:05 PM, "Andrew Grieve" wrote:
>
> > Started to update wiki instructions... but what is the correct last step?
> >
> > === To run these tests from the command line: ===
> > 1. Install "Google Web Driver" through the Android SKD Manager
> > 1. Copy the extras/google/webdriver/android_webdriver_library.jar from
> the
> > Android SDK into the framework/libs directory
> > 1. Build Cordova by running "ant" from within the framework directory
> > 1. Run the following command in the framework directory with a device
> > attached or emulator running:
> > adb shell am instrument -w
> > com.phonegap/android.test.InstrumentationTestRunner
> >
> >
> >
> > On Wed, Nov 14, 2012 at 9:24 PM, Andrew Grieve
> > wrote:
> >
> > > Tried to follow the command-line instructions but get:
> > >
> > > agrieve@dhcp-172-23-181-44 ~/git/incubator-cordova-android/framework
> > > (asdf) $ adb shell am instrument -w
> > > com.phonegap/android.test.InstrumentationTestRunner
> > > INSTRUMENTATION_STATUS: id=ActivityManagerService
> > > INSTRUMENTATION_STATUS: Error=Unable to find instrumentation info for:
> > > ComponentInfo{com.phonegap/android.test.InstrumentationTestRunner}
> > > INSTRUMENTATION_STATUS_CODE: -1
> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
> > > com.phonegap/android.test.InstrumentationTestRunner
> > >
> > > Changing to org.apache.cordova:
> > > agrieve@dhcp-172-23-181-44 ~/git/incubator-cordova-android/framework
> > > (asdf) $ adb shell am instrument -w
> > > org.apache.cordova/android.test.InstrumentationTestRunner
> > > android.util.AndroidException: INSTRUMENTATION_FAILED:
> > > org.apache.cordova/android.test.InstrumentationTestRunner
> > >
> > > On Wed, Nov 14, 2012 at 4:41 PM, Simon MacDonald <
> > > simon.macdon...@gmail.com> wrote:
> > >
> > >> Yup, it passed when I ran it and only it.
> > >>
> > >> Simon Mac Donald
> > >> http://hi.im/simonmacdonald
> > >>
> > >>
> > >> On Wed, Nov 14, 2012 at 4:35 PM, Joe Bowser
> wrote:
> > >>
> > >> > How can testPreconditions fail, but testViaLoadUrl pass? Can you run
> > >> > the test by itself? testViaHref is known to fail, and there's an
> issue
> > >> > open about that bug.
> > >> >
> > >>
> > >
> > >
> >
>
Re: [Android] Can everyone run the tests?
Web Driver is not necessary to run the tests. I'll get the command line
version working tomorrow.
On Nov 15, 2012 5:05 PM, "Andrew Grieve" wrote:
> Started to update wiki instructions... but what is the correct last step?
>
> === To run these tests from the command line: ===
> 1. Install "Google Web Driver" through the Android SKD Manager
> 1. Copy the extras/google/webdriver/android_webdriver_library.jar from the
> Android SDK into the framework/libs directory
> 1. Build Cordova by running "ant" from within the framework directory
> 1. Run the following command in the framework directory with a device
> attached or emulator running:
> adb shell am instrument -w
> com.phonegap/android.test.InstrumentationTestRunner
>
>
>
> On Wed, Nov 14, 2012 at 9:24 PM, Andrew Grieve
> wrote:
>
> > Tried to follow the command-line instructions but get:
> >
> > agrieve@dhcp-172-23-181-44 ~/git/incubator-cordova-android/framework
> > (asdf) $ adb shell am instrument -w
> > com.phonegap/android.test.InstrumentationTestRunner
> > INSTRUMENTATION_STATUS: id=ActivityManagerService
> > INSTRUMENTATION_STATUS: Error=Unable to find instrumentation info for:
> > ComponentInfo{com.phonegap/android.test.InstrumentationTestRunner}
> > INSTRUMENTATION_STATUS_CODE: -1
> > android.util.AndroidException: INSTRUMENTATION_FAILED:
> > com.phonegap/android.test.InstrumentationTestRunner
> >
> > Changing to org.apache.cordova:
> > agrieve@dhcp-172-23-181-44 ~/git/incubator-cordova-android/framework
> > (asdf) $ adb shell am instrument -w
> > org.apache.cordova/android.test.InstrumentationTestRunner
> > android.util.AndroidException: INSTRUMENTATION_FAILED:
> > org.apache.cordova/android.test.InstrumentationTestRunner
> >
> > On Wed, Nov 14, 2012 at 4:41 PM, Simon MacDonald <
> > simon.macdon...@gmail.com> wrote:
> >
> >> Yup, it passed when I ran it and only it.
> >>
> >> Simon Mac Donald
> >> http://hi.im/simonmacdonald
> >>
> >>
> >> On Wed, Nov 14, 2012 at 4:35 PM, Joe Bowser wrote:
> >>
> >> > How can testPreconditions fail, but testViaLoadUrl pass? Can you run
> >> > the test by itself? testViaHref is known to fail, and there's an issue
> >> > open about that bug.
> >> >
> >>
> >
> >
>
Re: [Android] Can everyone run the tests?
Started to update wiki instructions... but what is the correct last step?
=== To run these tests from the command line: ===
1. Install "Google Web Driver" through the Android SKD Manager
1. Copy the extras/google/webdriver/android_webdriver_library.jar from the
Android SDK into the framework/libs directory
1. Build Cordova by running "ant" from within the framework directory
1. Run the following command in the framework directory with a device
attached or emulator running:
adb shell am instrument -w
com.phonegap/android.test.InstrumentationTestRunner
On Wed, Nov 14, 2012 at 9:24 PM, Andrew Grieve wrote:
> Tried to follow the command-line instructions but get:
>
> agrieve@dhcp-172-23-181-44 ~/git/incubator-cordova-android/framework
> (asdf) $ adb shell am instrument -w
> com.phonegap/android.test.InstrumentationTestRunner
> INSTRUMENTATION_STATUS: id=ActivityManagerService
> INSTRUMENTATION_STATUS: Error=Unable to find instrumentation info for:
> ComponentInfo{com.phonegap/android.test.InstrumentationTestRunner}
> INSTRUMENTATION_STATUS_CODE: -1
> android.util.AndroidException: INSTRUMENTATION_FAILED:
> com.phonegap/android.test.InstrumentationTestRunner
>
> Changing to org.apache.cordova:
> agrieve@dhcp-172-23-181-44 ~/git/incubator-cordova-android/framework
> (asdf) $ adb shell am instrument -w
> org.apache.cordova/android.test.InstrumentationTestRunner
> android.util.AndroidException: INSTRUMENTATION_FAILED:
> org.apache.cordova/android.test.InstrumentationTestRunner
>
> On Wed, Nov 14, 2012 at 4:41 PM, Simon MacDonald <
> simon.macdon...@gmail.com> wrote:
>
>> Yup, it passed when I ran it and only it.
>>
>> Simon Mac Donald
>> http://hi.im/simonmacdonald
>>
>>
>> On Wed, Nov 14, 2012 at 4:35 PM, Joe Bowser wrote:
>>
>> > How can testPreconditions fail, but testViaLoadUrl pass? Can you run
>> > the test by itself? testViaHref is known to fail, and there's an issue
>> > open about that bug.
>> >
>>
>
>
Re: [Android] Can everyone run the tests?
Tried to follow the command-line instructions but get:
agrieve@dhcp-172-23-181-44 ~/git/incubator-cordova-android/framework (asdf)
$ adb shell am instrument -w
com.phonegap/android.test.InstrumentationTestRunner
INSTRUMENTATION_STATUS: id=ActivityManagerService
INSTRUMENTATION_STATUS: Error=Unable to find instrumentation info for:
ComponentInfo{com.phonegap/android.test.InstrumentationTestRunner}
INSTRUMENTATION_STATUS_CODE: -1
android.util.AndroidException: INSTRUMENTATION_FAILED:
com.phonegap/android.test.InstrumentationTestRunner
Changing to org.apache.cordova:
agrieve@dhcp-172-23-181-44 ~/git/incubator-cordova-android/framework (asdf)
$ adb shell am instrument -w
org.apache.cordova/android.test.InstrumentationTestRunner
android.util.AndroidException: INSTRUMENTATION_FAILED:
org.apache.cordova/android.test.InstrumentationTestRunner
On Wed, Nov 14, 2012 at 4:41 PM, Simon MacDonald
wrote:
> Yup, it passed when I ran it and only it.
>
> Simon Mac Donald
> http://hi.im/simonmacdonald
>
>
> On Wed, Nov 14, 2012 at 4:35 PM, Joe Bowser wrote:
>
> > How can testPreconditions fail, but testViaLoadUrl pass? Can you run
> > the test by itself? testViaHref is known to fail, and there's an issue
> > open about that bug.
> >
>
Re: [Android] Can everyone run the tests?
Yup, it passed when I ran it and only it. Simon Mac Donald http://hi.im/simonmacdonald On Wed, Nov 14, 2012 at 4:35 PM, Joe Bowser wrote: > How can testPreconditions fail, but testViaLoadUrl pass? Can you run > the test by itself? testViaHref is known to fail, and there's an issue > open about that bug. >
Re: [Android] Can everyone run the tests?
How can testPreconditions fail, but testViaLoadUrl pass? Can you run the test by itself? testViaHref is known to fail, and there's an issue open about that bug.
Re: [Android] Can everyone run the tests?
Okay, with the update:
testViaHref
testPreconditions
fail for me on Android 4.0.3
Simon Mac Donald
http://hi.im/simonmacdonald
On Wed, Nov 14, 2012 at 4:21 PM, Joe Bowser wrote:
> 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
> 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 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
> >> 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=0x1000
> >> > 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
> 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
> 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
> 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
> >> 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
> >> >> >>> > 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
> >> >> >>> > >
Re: [Android] Can everyone run the tests?
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
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 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
>> 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=0x1000
>> > 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 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 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 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
>> >> >> 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
>> 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
>> >> >>> > 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
>> >> 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
Re: [Android] Can everyone run the tests?
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 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
> 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=0x1000
> > 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 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 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 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
> >> >> 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
> 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
> >> >>> > 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
> >> 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 he
Re: [Android] Can everyone run the tests?
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
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=0x1000
> 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 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 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 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
>> >> 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 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
>> >>> > 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
>> 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
>> >>> > > >
>> >>> > >
>> >>> >
Re: [Android] Can everyone run the tests?
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=0x1000
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 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 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 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
> >> 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 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
> >>> > 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
> 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
> >>> > > >
> >>> > >
> >>> >
> >>
> >>
> >
>
Re: [Android] Can everyone run the tests?
This isn't totally related but I can describe my experience creating a new project in Eclipse for Android 2.2 FroYo using Cordova 2.2 (I'm in Linux, Ubuntu 10.04): I got it to work but I had to be a little creative. It works pretty much out of the box for making 4.0 Android, but the AndroidManifest.xml file was a problem for 2.2. I solved it by borrowing a manifest from Cordova 2.0 and after that it compiled and ran. A simple solution, I think, would be to use a flag or argument on the create script and setting up two or more more manifests in the templates directory. Cheers all. (Love the script idea, makes setting up a new project a lot quicker) Marlin On Tue, Nov 13, 2012 at 12:38 PM, Joe Bowser 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 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 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 >>> 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 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 > 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 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 > > > > > > >>> >>> >>
Re: [Android] Can everyone run the tests?
BUMP! Can everyone run these tests? I need to know about failures ASAP On Mon, Nov 5, 2012 at 9:44 AM, Joe Bowser 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 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 >> 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 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 >>> > 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 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 >>> > > > >>> > > >>> > >> >> >
Re: [Android] Can everyone run the tests?
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 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 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 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 >> > 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 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 >> > > > >> > > >> > >> > >
Re: [Android] Can everyone run the tests?
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 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 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 > > 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 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 > > > > > > > > > >
Re: [Android] Can everyone run the tests?
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 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 > 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 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 > > > > > >
Re: [Android] Can everyone run the tests?
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 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 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 > > >
Re: [Android] Can everyone run the tests?
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 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 >
