Use Travis to run automated tests

[avindra]

This sets up the basic infrastructure for testing on Travis. Detected some issues with the describe callbacks when upgrading the deps, so I fixed those.

Currently 3 tests are failing. As there is no publicly available test history, it's hard to tell if these are failing due to bumping devDeps, or if they were failing to begin with.

Benefits:

• Test suite will run against PR's automatically, saving review time 🎊
• Can program the test suite to automatically test against jQuery 2.x and 3.x in the future using environment variables

First test run resut:

https://travis-ci.org/avindra/fullcalendar/builds/137090723

[arshaw]

will npm install get run as well?

[avindra]

I've replied in the main PR, but for the sake of others reading here: yes. By default Travis uses npm install and the test command by default for node. Which is nice, because it has created a lot of consistency between hundreds (if not thousands) of OSS projects.

[arshaw]

this is awesome! will be very valuable to the project, thanks.

I'm having a tough time with Travis's UI figuring out where I can see what tests exactly failed. any pointers on how to get that insight?

[avindra]

On Travis, npm install runs by default for node, and npm test is the
default test command.

I'm away from the computer otherwise id link you, but if you click around
there's a job details section where you can expand the log and see all the
output determine which tests are failing
On Sun, Jun 12, 2016 at 3:33 PM Adam Shaw notifications@github.com wrote:

this is awesome! will be very valuable to the project, thanks.

I'm having a tough time with Travis's UI figuring out where I can see what
tests exactly failed. any pointers on how to get that insight?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#3218 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAHvgF94hKSzHyZ8zcQ83AhHMMCiSj0Hks5qLF8NgaJpZM4Iz18R
.

[avindra]

Sample job link https://travis-ci.org/avindra/fullcalendar/jobs/137090725

In order to enable Travis, you'll have to log in via oauth, give Travis permissions and enable tracking per repo (i.e., fullcalendar/fullcalendar). The next commit and subsequent prs should trigger automatic builds 😀

[arshaw]

awesome. this will be merged into master for the next release. i'll bug you and/or look at TravisCI docs if I have any more questions. thanks!

[arshaw]

Code complete and slated for v2.8.0 (wip docs). Will notify when released.

Will deal with those failing tests soon.

[arshaw]

Released in v2.8.0. thank you @avindra

[avindra]

Thanks! Have you set up the travis integration yet? I don't see any builds at:

https://travis-ci.org/fullcalendar/fullcalendar/

[arshaw]

i got it set up. it's really cool. i made a separate ticket to solve the failing tests:
#3236

thanks