Currently Travis is configured to run the backend specs (using the default bundle exec rake).
Code Climate is configured to report on the coverage of those backend specs (with a corresponding README badge).
Ideally we'd like to have Travis also run the karma test suite (using gulp test); and have Code Climate report on the front end coverage as well.
For Travis this presumably means:
Including an install step that runs npm install
Having a karma.conf.js setup that runs the suite once, in (ideally) Chrome and PhantomJS (or perhaps PhantomJS and Firefox if Chrome is not possible); and outputs in LCOV
Adding the codeclimate-test-reporter NPM package as a dependency
Piping the LCOV output into the codeclimate reporter (codeclimate < LCOV.output)
Not sure how Code Climate would deal with two different sets of coverage results?
Currently Travis is configured to run the backend specs (using the default
bundle exec rake
). Code Climate is configured to report on the coverage of those backend specs (with a corresponding README badge).Ideally we'd like to have Travis also run the karma test suite (using
gulp test
); and have Code Climate report on the front end coverage as well.For Travis this presumably means:
npm install
codeclimate-test-reporter
NPM package as a dependencycodeclimate
reporter (codeclimate < LCOV.output
)Not sure how Code Climate would deal with two different sets of coverage results?