markbates / markbates/cover_me

What is the purpose of the `rake cover_me:report` task?

Open
#25 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
203
Forks
17
PR merge metrics
No merged PRs in 30d

Description

It's not really clear to me what this does. Is it that it must be run after your tests in order for an accurate report to be generated? I find it odd that after running my test suite, my coverage report is opened in my browser (89% coverage, thankyouverymuch), but if I run rake cover_me:report after that, the coverage report is opened in my browser again, but with 92% coverage.

This would make sense to me if every file had increased somewhat in coverage (as my test suite runs rspec tests and then cucumber tests, and the initial coverage report is opened as the rspec tests are completed), but the numbers just seem to change after running rake cover_me:report: some go up, some go down. Doesn't that seem somewhat odd to you?

Also, a related question: is it possible to programmatically determine the overall coverage percentage? I would love to fail my build if it dips below some arbitrary threshold.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the rake cover_me:report task and trace how it combines coverage from the RSpec and Cucumber runs. Compare the reports produced before and after that task, then document the task's purpose, why percentages differ, and whether the overall percentage can be retrieved for a build check.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.