badges/shields

Enhance TeamCity Coverage Badge

Open

#3,111 opened on Feb 27, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (5,423 forks)batch import
good first issueservice-badge

Repository metrics

Stars
 (22,337 stars)
PR merge metrics
 (Avg merge 6d 3h) (71 merged PRs in 30d)

Description

:clipboard: Description

Enhance the TeamCity Coverage Badge to allow the user to specify the coverage metric (lines, statements, etc.) they want to use via a param.

Our current badge implementation is keying off statement coverage, but while I was working on resolving https://github.com/badges/shields/issues/2901 I noticed that a lot (actually the majority) of TeamCity projects with coverage did not have statement coverage (most had line coverage long with method/function, and others).

If we allowed the user to specify their target coverage metric (we can still default to statement) then we can make the coverage badge for TeamCity available to a much broader set of users

Contributor guide

Research direction
Investigate the current TeamCity badge implementation and add a parameter for coverage metric selection. Refer to similar patterns in other coverage badges in the repository.
Tech stack
javascriptnodejs
Domain
backenddevtools
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.
Half day
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.
Clear
Prerequisites
GitJavaScriptNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75