ipfs/kubo

Code Coverage on subprojects

Open

#3,112 opened on Aug 23, 2016

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wantedkind/teststatus/deferred

Description

go-ipfs has many dependencies, and just like in #3053 we want to have solid tests on all of them. The plan is to use coveralls.io to have this all automated for us.

Contributor guide

Tech stack
go
Domain
testing
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go testingCoveralls integrationCI pipeline
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue proposes integrating coveralls.io to track code coverage across subprojects. To implement, examine the existing CI configuration (e.g., .travis.yml or GitHub Actions), set up a coveralls account, and add coverage flags to go test commands. The repo's test files are in root and subdirectories. No prior work or comments exist, but refer to issue #3053 for context.
Code Coverage on subprojects · ipfs/kubo#3112 | Good First Issue