Hook up code-coverage

Open
#16 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
ci-cd, testing-qa

Research direction

Start by inspecting the repository's CI configuration and comparing it with the travis.yml example at https://github.com/phayes/rsa-fdh. Determine how coverage reporting fits into the existing test run, then verify that CI produces and publishes a coverage report. Done means coverage reporting runs successfully in CI.

Written by the indexing model from the issue text.

Description

ci help wanted

Hi there,

I was wondering if you could hook up code-coverage reporting (I personally like codecov, but coveralls and others would be fine too).

Once this is done, I will work on getting code coverage up to 100% (or as close as possible).

Check out the travis.yml file over at https://github.com/phayes/rsa-fdh for an example of how to do it.

Dominant language
Rust
Stars
673
Forks
190
No merged PRs in 30d

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.

More from RustCrypto/RSA

All issues in RustCrypto/RSA

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.