Confirmed users
513
edits
EngineeringProductivity/Projects/CodeCoverage: Difference between revisions
EngineeringProductivity/Projects/CodeCoverage (view source)
Revision as of 14:13, 7 September 2016
, 7 September 2016fix more workding
Klahnakoski (talk | contribs) (add meeting notes) |
Klahnakoski (talk | contribs) m (fix more workding) |
||
| Line 8: | Line 8: | ||
The objective of the Code Coverage project is to provide daily code coverage details and summary statistics. The assumption is that | The objective of the Code Coverage project is to provide daily code coverage details and summary statistics. The assumption is that | ||
code coverage statistics and details can help judge code quality. We expect this information to be useful to | code coverage statistics and details can help judge code quality. We expect this information to be useful to | ||
* Release managers - Provide them with another metric to help measure risk a particular changeset, or | * Release managers - Provide them with another metric to help measure risk a particular changeset, or family of changesets, adds to a release | ||
* Module owners - Provide drill down coverage statistics so test coverage is focused on the most important part of the code | * Module owners - Provide drill down coverage statistics so test coverage is focused on the most important part of the code | ||
* Individual developers - To see if their new code | * Individual developers - To see if their new code require new tests to cover it, or if tests already cover their new code | ||
* Our own test-infrastructure team - We can reduce the number of machines dedicated to testing, if we know where tests overlap, and focus on tests that cover recent changes. | * Our own test-infrastructure team - We can reduce the number of machines dedicated to testing, if we know where tests overlap, and focus on tests that cover recent changes. | ||