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

Excluding some files from coverage #44

Closed
jzuhone opened this issue Jan 19, 2015 · 4 comments
Closed

Excluding some files from coverage #44

jzuhone opened this issue Jan 19, 2015 · 4 comments

Comments

@jzuhone
Copy link

jzuhone commented Jan 19, 2015

Hello,

Is there a way to exclude a file from coverage?

It's a file that generates a bunch of symbols using a macro, and I've tried several ways to make it fall under test coverage but none of them have worked, unfortunately.

@pluskid
Copy link

pluskid commented Jan 29, 2015

+1 for this feature. In Mocha.jl, some of the components using GPU cannot be tested on Travis-CI due to absence of GPU devices. I'm currently using a hack to ignore a subdirectory. But I think it might be useful to have a more principled way of ignoring some files. For example

  1. Using something similar to .gitignore to specify patterns of files to be ignored.
  2. Automatically ignore files that have not been loaded. In Mocha.jl, the whole codebase for GPU backend is not loaded if GPU is not enabled in the environment variable. It might be good if coverage could report only the files that are actually loaded during the test. Though I'm not sure whether this is a generally applicable situation for other packages.

@vtjnash
Copy link
Member

vtjnash commented Nov 12, 2020

Moved to JuliaCI/CoverageTools.jl#33

@vtjnash vtjnash closed this as completed Nov 12, 2020
@kongdd
Copy link

kongdd commented Aug 14, 2022

Is this feature implemented now?

@DilumAluthge
Copy link
Member

DilumAluthge commented Aug 14, 2022

No, it's just being tracked in JuliaCI/CoverageTools.jl#33 (instead of on this repo).

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

Successfully merging a pull request may close this issue.

6 participants