This looks like what I was thinking too. The tests I have are for 1.6.0 and wanted to get them in for testing this release - so not sure it makes sense to go into the CordovaWebView branch right now. Instead, I created a "tests" branch for review. I followed the same structure that Joe define in the branch, such that both sets of tests can be merged when CordovaWebView branch is ready.
On Wed, Mar 28, 2012 at 6:58 PM, Filip Maj <[email protected]> wrote: > To elaborate on what Joe implied: let's try to implement/prototype new > features *together* on one branch instead of individually too ya? > > On 3/28/12 4:41 PM, "Michael Brooks" <[email protected]> wrote: > > >+1 > > > >Love it. > > > >On Wed, Mar 28, 2012 at 3:36 PM, Joe Bowser <[email protected]> wrote: > > > >> We already have this in the CallbackWebView branch. > >> > >> On Wed, Mar 28, 2012 at 3:29 PM, Brian LeRoux <[email protected]> wrote: > >> > >> > +1 > >> > > >> > On Wed, Mar 28, 2012 at 3:22 PM, Filip Maj <[email protected]> wrote: > >> > > I like tests. > >> > > > >> > > On 3/28/12 3:18 PM, "Bryce Curtis" <[email protected]> wrote: > >> > > > >> > >>I have some native Android tests to validate backbutton, > >>multitasking, > >> > >>etc., that would be good to run to for release verification. It > >>looks > >> > >>like > >> > >>some platforms have a test dir for that purpose - so was thinking of > >> > >>creating an Android project under "test/". I think Drew has some > >> > >>Blackberry tests too that he will want to add in the near future. > >> > > > >> > > >> > >
