Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coverage should exclude the template folder #131

Open
SBoudrias opened this issue Nov 18, 2015 · 12 comments
Open

Coverage should exclude the template folder #131

SBoudrias opened this issue Nov 18, 2015 · 12 comments
Labels

Comments

@SBoudrias
Copy link
Member

Title is pretty self explicit. We don't want to cover JS files inside the template folder.

@SBoudrias SBoudrias added the bug label Nov 18, 2015
@udnisap
Copy link
Contributor

udnisap commented Nov 26, 2015

does it include?

@SBoudrias
Copy link
Member Author

@udnisap sorry, what do you mean?

@udnisap
Copy link
Contributor

udnisap commented Nov 27, 2015

I am assuming you are referring to coverage.io reports.
https://coveralls.io/builds/4282602
there are no templates

@SBoudrias
Copy link
Member Author

Oh, I'm talking about the generated code. I removed template coverage manually from this repository, but the generated code still covers the template folder.

@hemanth
Copy link
Member

hemanth commented Dec 6, 2015

It should be done at gulp-task?
gulp-coverall doesn't provide any options to skip files.

@SBoudrias
Copy link
Member Author

in the pre-test tasks.

@hemanth
Copy link
Member

hemanth commented Dec 7, 2015

Just a '!**/templates/**' is the src is fine?

Well, I see specific files being mentioned in the src, no glob.

@SBoudrias
Copy link
Member Author

In the generated code, not the project code.

@hemanth
Copy link
Member

hemanth commented Dec 7, 2015

Ha ok, this change must be in 'node:app' right?

@udnisap
Copy link
Contributor

udnisap commented Dec 7, 2015

Generate app has 100% coverage

@eddiemonge
Copy link
Member

Ha ok, this change must be in 'node:app' right?

I think this sounds right. Should this be closed here and opened there? https://github.com/yeoman/generator-node/issues/new

@SBoudrias
Copy link
Member Author

It'd probably require some changes on both sides, so we should keep it open here and figure how we want to pass that to generator-node (probably a new option).

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

No branches or pull requests

4 participants