Perform browsertesting on commit and adopt collaborative code quality tools.

[evilaliv3]

Given the hight usage of the library it would be important to perform browsertesting on commit and adopt collaborative code quality tools.

This would allow to detect defects happening on some specific browser/version, track code coverage and work in a collaborative way on improving the code quality of the library

Given the fact that the project is already using karma performing tests with PhantomJS, i would suggest to adopt karma-coverage to perform testing on Saucelabs.

It would be great than if during the testing we could integrate Codeclimate in order to keep track of the code maturity and the code coverage of the tests.

I've no interest in suggesting this specific software/services, but this all the softwares i'm suggesting are opensource and the cloud services involved are offering a complete free support for opensource projects so that it would be great if start adopting them.

Here you find the exact integration you need given the libraries involved in the project. I did it few days ago in order to improve a library we use in GlobaLeaks: https://github.com/ghostbar/angular-zxcvbn/pull/15

The result of that integration could be something like:

Here is the current output of codeclimate for https://codeclimate.com/github/mgonto/restangular: codeclimate results for mgonto/restangular

[daviesgeek]

I agree! Can you submit a PR with changes and I'll merge that in?

[bostrom]

Good idea @evilaliv3. Any change for a PR?