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
> >
>

Reply via email to