Skip to content
This repository has been archived by the owner on Aug 30, 2021. It is now read-only.

Adding another job for Travis CI to run the grunt coverage task on every build #886

Merged

Conversation

lirantal
Copy link
Member

@lirantal lirantal commented Sep 4, 2015

This addresses the code coverage running as part of our CI in #811

@lirantal lirantal self-assigned this Sep 4, 2015
@lirantal lirantal added this to the 0.4.x milestone Sep 4, 2015
@ilanbiala
Copy link
Member

@lirantal why not have coverage run at the end of the tests? What's better about this way?

@lirantal
Copy link
Member Author

lirantal commented Sep 4, 2015

I don't know. Do you care to see the code coverage everytime you run tests? I didn't think it was related. Having distinct tasks for each, just like we separated the whole tests into test:server and test:client seems to make more sense.

@codydaig
Copy link
Member

codydaig commented Sep 4, 2015

I'll second @lirantal. I don't want to see the coverage report every time I run tests on the project.

@ilanbiala
Copy link
Member

@lirantal ok, I agree with you on that. LGTM.

@lirantal
Copy link
Member Author

lirantal commented Sep 4, 2015

Cool, let's see if we get code coverage reports now on coveralls

lirantal added a commit that referenced this pull request Sep 4, 2015
…ge-task

Adding another job for Travis CI to run the `grunt coverage` task on every build
@lirantal lirantal merged commit 522cc6b into meanjs:master Sep 4, 2015
@codydaig
Copy link
Member

codydaig commented Sep 4, 2015

@lirantal
Copy link
Member Author

lirantal commented Sep 4, 2015

Yep, awesome! :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants