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

Increase code coverage #6742

Merged
merged 2 commits into from
Feb 7, 2019
Merged

Conversation

bquorning
Copy link
Contributor

I was looking a bit at our code coverage results, and in these two files I found three unused methods:

In ImplicitStringConcatenation I found a couple of lines that could easily be covered by tests, but weren’t:

I am thinking it might be a good idea to have coverage reports in our pull requests. WDYT?


Before submitting the PR make sure the following are checked:

  • Wrote good commit messages.
  • Commit message starts with [Fix #issue-number] (if the related issue exists).
  • Feature branch is up-to-date with master (if not - rebase it).
  • Squashed related commits together.
  • Added tests.
  • Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
  • The PR relates to only one subject with a clear title
    and description in grammatically correct, complete sentences.
  • Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

According to code coverage report, these methods are never called. Confirmed by rspec.
Code coverage for ImplicitStringConcatenation increased from 87.8% to 100%.
@Drenmi
Copy link
Collaborator

Drenmi commented Feb 7, 2019

I am thinking it might be a good idea to have coverage reports in our pull requests. WDYT?

I wouldn't mind at all. 🙂

@Drenmi Drenmi merged commit 1c8335c into rubocop:master Feb 7, 2019
@bquorning bquorning deleted the increase-code-coverage branch February 7, 2019 07:26
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 this pull request may close these issues.

None yet

2 participants