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

Custom SimpleCov coverage_dir not supported #143

Closed
dueckes opened this issue Nov 8, 2016 · 2 comments
Closed

Custom SimpleCov coverage_dir not supported #143

dueckes opened this issue Nov 8, 2016 · 2 comments

Comments

@dueckes
Copy link

dueckes commented Nov 8, 2016

Gem version: 1.0.1

The reporter does not appear to recognise a custom SimpleCov coverage directory.

I often use a configuration such as this to consolidate my generated artifacts under one directory:

SimpleCov.start do
  coverage_dir "tmp/coverage"
end

When I run the reporter using this configuration, here's the error I'm seeing:

Coverage report generated for RSpec to /my/project/tmp/coverage. 35 / 35 LOC (100.0%) covered.

bundle exec codeclimate-test-reporter

Coverage results not found

rake aborted!

Command failed with status (1): [bundle exec codeclimate-test-reporter...]

Any chance there is support for customising this directory (current or planned)?

@dblandin
Copy link
Contributor

dblandin commented Nov 8, 2016

Hey @dueckes,

Yep! Supporting an alternate coverage directory makes sense to me. At the moment it's hard-coded to ./coverage, but we should definitely support alternate locations via a flag on the binary. Would something like the following work for you?

$ codeclimate-test-reporter --directory /tmp/coverage

@dueckes
Copy link
Author

dueckes commented Nov 10, 2016

That would work.

It would be ideal to have it inferred from SimpleCov settings, but given the hard separation of the reporter from SimpleCov / running the tests, repeating the directory seems appropriate.

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

No branches or pull requests

3 participants