Sergey, can we set up AppVeyor to run the "npm test" of cordova-lib? If yes, it would be an excellent option - we will have cordova-lib jasmine tests running on windows, which otherwise happens rarely for all of us who develop on Mac or Linux.
On Mon, Jul 14, 2014 at 2:54 PM, Jesse <purplecabb...@gmail.com> wrote: > We should just use Travis for quick sanity check tests. > > re: integration testing > Getting into all the other build+test options is too close to Medic. Unless > we plan to abandon Medic, we should focus on getting Medic+BuildBot working > perfectly across all platforms, then possibly even reporting back to github > on every commit. > > @purplecabbage > risingj.com > > > On Mon, Jul 14, 2014 at 7:16 AM, Sergey Grebnov (Akvelon) < > v-seg...@microsoft.com> wrote: > > > Tests on Windows: > > I've compared Wercker and Appveyor and as for me it looks like Appveyor > is > > a better option to proceed for Windows since > > 1. Wercker's existing windows boxes doesn't support building of Windows > > 8.1 and WP 8.1 apps due to absence of Windows 8.1 and WP 8.1 SDKs on the > > boxes. > > 2. Appveyor supports above > > Please note, Wercker supports custom VM boxes so potentially we can add > > custom VMs but I'm not sure it is good idea to maintain them. > > > > Tests on OSX: > > I propose to use Travis since in comparison to Wercker it provides OSX > > test boxes with XCode installed ( > > http://docs.travis-ci.com/user/osx-ci-environment) and also supports > > Android builds (http://docs.travis-ci.com/user/languages/android) > > > > Thx! > > Sergey > > -----Original Message----- > > From: Sergey Grebnov (Akvelon) > > Sent: Monday, July 7, 2014 6:00 PM > > To: dev@cordova.apache.org > > Subject: RE: Add build status to github > > > > Hey Mark, it is really great to see you are working in this direction, > > thx! Here are my additional notes > > > > I think we should have discussion in two directions here: > > 1. Decide what we want to run as test for each repo 2. Particular > > service/implementation details > > > > As for 1: > > a) LIB, CLI: I propose to run unit tests via 'npm test' for cordova-lib, > > cordova-cli, cordova-plugman (btw, I don't see plugman tests so not sure > we > > have them) It seems, that Mark is on the same page. > > > > b) PLATFORMS: for the platforms I propose to start from implementing > > simple e2e test with the following steps (written in nodejs): > > - install cordova-cli (apache/master?) > > - create test app > > - add platform > > - build > > > > * as a long term goal we may want to move this to npm tests (but > > include to special group which can be run with additional flag since I > > don't think we should run this along with general unit tests ) > > > > As for 2: > > If we want unified build platform across all repos it seems that Wercker > > and Appveyor are the only good options due to windows support required. > > Both looks good to me, but I need to double check Wercker supports VS2013 > > (msbuild12) since it requires to build cordova-windows (will investigate > > and respond). I also think is that Travic-CI is the most safe option for > > other platforms/repos since they already proved to be a good solution for > > many open source companies. > > > > Thx! > > Sergey > > -----Original Message----- > > From: Mark Koudritsky [mailto:kam...@google.com] > > Sent: Friday, July 4, 2014 6:57 AM > > To: dev@cordova.apache.org > > Subject: Re: Add build status to github > > > > Oops, sorry, didn't look at the links before sending another link to > > AppVeyor. Why not to use AppVeyor for lib and cli too? We could > definitely > > use some testing on windows. > > > > I also experimented with Wercker <http://wercker.com/> which is yet > > another free CI service. > > Added it to a branch in my fork of cordova-lib. You can see a badge with > > build results here in README: > > https://github.com/kamrik/cordova-lib/tree/wercker > > > > I never used Travis CI, but from description looks like Wercker is a bit > > more flexible with environment setup and they even offer a predefined > > environment for building Android apps < > > http://devcenter.wercker.com/articles/languages/android.html> so maybe > we > > can use it to run a test that goes all the way to building an apk. They > say > > <http://devcenter.wercker.com/articles/bestpractices/pullrequests.html> > > they support checking pull requests too. > > > > What do you think? > > > > That said, I'm not particularly attached to any specific CI service, any > > of them would be very helpful. > > > > > > On Fri, Jun 27, 2014 at 10:40 AM, Andrew Grieve <agri...@chromium.org> > > wrote: > > > > > Make it happen :) > > > > > > > > > On Fri, Jun 27, 2014 at 10:02 AM, Mark Koudritsky <kam...@google.com> > > > wrote: > > > > > > > Would be nice to have this. Specifically Travis will only run on > > > > Linux > > > (and > > > > maybe OSX). Here is a random similar service I found that can also > > > > run on windows. > > > > http://www.appveyor.com/ > > > > > > > > > >
