ipfs/kubo

Code Coverage on subprojects

Open

#3,112 opened on Aug 23, 2016

View on GitHubContributor guide
 (0 comments) (1 reaction) (0 assignees)Go (2,725 forks)batch import
help wantedkind/teststatus/deferred

Repository metrics

Stars
 (13,906 stars)
PR merge metrics
 (Avg merge 4d 2h) (28 merged PRs in 30d)

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

Research direction
Explore the coverage setup for subprojects in go ipfs using coveralls.io and integrate it with the repository.
Tech stack
go
Domain
testing
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70