- Add deprecation notice to post-install gem message.
-
Lock simplecov to
<= 0.13
, so we can safely use an internal-to-simplecov method. (@bliof)Note: you may need to run
bundle update codeclimate-test-reporter simplecov
to resolve your bundle.
- Continue improving our support for sending payloads in contexts where git is not available. (@sullerandras)
- Allow Codeship users to send a test coverage report without mounting their
.git
directory within the docker container where they run their tests without manually exposing an environment variable. Instead, use an environment variable already exposed by the CI environment. (@c-knowles)
- Allow Codeship users to send a test coverage report without mounting their
.git
directory within the docker container where they run their tests. (@antoniobg)
- Accept path to coverage results as optional first argument (@jreinert)
- Handle multi-command resultsets (@pbrisbin)
- Improve strategy for Ruby 1.9.3 compatibility testing
- Fixed crashing error when the path to a file in the coverage report contains a parenthesis.
- Made sure the gem can be built while running Ruby 1.9.3
-
Previously, this gem extended
Simplecov
with a custom formatter which posted results to Code Climate. Now, you are responsible for executingSimplecov
yourself.-
If you already have the following in your test/test_helper.rb (or spec_helper.rb, cucumber env.rb, etc)
require 'codeclimate-test-reporter' CodeClimate::TestReporter.start
then you should replace it with
require 'simplecov' SimpleCov.start
-
-
Previously, the
codeclimate-test-reporter
automatically uploaded results at the end of your test suite. Now, you are responsible for runningcodeclimate-test-reporter
as a separate step in your build. -
Previously, this gem added some exclusion rules tuned according to feedback from its users, and now these no longer happen automatically. If you are experiencing a discrepancy in test coverage % after switching to the new gem version, it may be due to missing exclusions. Filtering
vendor
,spec
, ortest
directories may fix this issue. -
Previously, during the execution of multiple test suites, this gem would send results from the first suite completed. You are now expected to run an executable packaged with this gem as a separate build step, which means that whatever results are there (likely the results from the last suite) will be posted to Code Climate.
- Support
ENV["SSL_CERT_PATH"]
for custom SSL certificates