I see, it looks like our testing infra is going to be redunant/distributed regardless. (travis + X) No sense in fighting it!
On Tue, Jul 15, 2014 at 9:31 AM, Parashuram Narasimhan (MS OPEN TECH) < panar...@microsoft.com> wrote: > Don't we still need Travis to drive the Saucelabs test? > > P.S: I have been investigating to see if I could use Appium to run Medic > tests. No Windows support yet though :( > > -----Original Message----- > From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf Of > Brian LeRoux > Sent: Tuesday, July 15, 2014 9:18 AM > To: dev@cordova.apache.org > Subject: RE: Add build status to github > > https://docs.saucelabs.com/reference/status-images/ > On Jul 15, 2014 9:17 AM, "Brian LeRoux" <b...@brian.io> wrote: > > > Or we could use SauceLabs (for all) > > On Jul 15, 2014 9:16 AM, "Parashuram Narasimhan (MS OPEN TECH)" < > > panar...@microsoft.com> wrote: > > > >> We would need both right? For covering Windows and Linux platforms > >> for lib to build/run. > >> > >> -----Original Message----- > >> From: Mark Koudritsky [mailto:kam...@google.com] > >> Sent: Tuesday, July 15, 2014 7:55 AM > >> To: dev@cordova.apache.org > >> Subject: Re: Add build status to github > >> > >> Ok, let's ask here. > >> > >> Does anybody have any strong preferences for either AppVeyor or > >> TravisCI or both for cordova-lib? > >> note, this is only about running "npm test" in cordova-lib. > >> > > >
