Research: Code coverage solutions

Open
#925 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

Compare the code coverage services named in the issue, especially Coveralls and Codecov, against the project's need to detect disabled tests and provide granular coverage details. Document the options, tradeoffs, and a recommendation; done means the project has a clear service choice and integration direction.

Written by the indexing model from the issue text.

Description

enhancement

We've had a few bugs in the past several months due to accidentally disabling tests. These would be harder to miss if we integrated with a code coverage solution. I've also seen discussions in code reviews about code coverage, but we don't have good tooling to show granular details about code coverage.

We should research options for code coverage services.

Here are the ones I'm aware of:

  • Coveralls: I've used it, and I found it fine but not great. It felt like they stopped developing it 6 years ago.
  • Codecov: Looks promising, haven't tried it
Dominant language
Python
Stars
3.5k
Forks
291
No merged PRs in 30d

Contributor guide

Open the contributing guide

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.

More from tiny-pilot/tinypilot

All issues in tiny-pilot/tinypilot

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.