Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Candidate Release Comments (Test Coverage) #23

Open
klumb opened this issue Jun 24, 2019 · 3 comments

Comments

Projects
None yet
5 participants
@klumb
Copy link
Member

commented Jun 24, 2019

This issue was created to collect comments about the upcoming metrics release.

This thread is for comments about Test Coverage

GitHub location: https://github.com/chaoss/wg-risk/blob/master/metrics/Test_Coverage.md

Release candidate: https://chaoss.community/metric-test-coverage

See all release candidates of metrics are at:
https://chaoss.community/metrics-rc/

Important Dates

Release Freeze: June 21st, 2019
Candidate Release: June 24th, 2019
Comments Close: July 24th, 2019
Release Date: August 1st, 2019

@sgoggins

This comment has been minimized.

Copy link
Member

commented Jul 1, 2019

The metric definition would benefit from examples using a few projects to illustrate test coverage metrics. So, run test coverage tools on 2-3 projects and illustrate the output.

@germonprez

This comment has been minimized.

Copy link
Contributor

commented Jul 9, 2019

This should be rewritten as a statement: How much of a given code base is covered by at least one test suite.

@foundjem

This comment has been minimized.

Copy link

commented Jul 9, 2019

A good test courage might control for code quality, moreover, a machine learning model can be trained to suggest areas that need more coverage.

@sgoggins sgoggins self-assigned this Jul 15, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.