EngineeringProductivity/Projects/CodeCoverage
Jump to navigation
Jump to search
Code Coverage
Introduction
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
- Release managers - Provide them with another metric to help measure risk a particular changeset, or set 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
- Individual developers - To see if their new code requires 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.
Generally, we would like to know
- Is code coverage going up or down?
- If code coverage is going down, what new code is not being covered? Is it OK to not be covered?
- If code coverage is going down, what tests have been dropped? Is that OK?
- Should we alert when code coverage down "significantly"?
- When adding or change code in source file S, what tests cover that source file? What tests should we run?
Getting Started
- Getting Started with Code Coverage - https://public.etherpad-mozilla.org/p/coverage_quickstart
User Interface
- GUI objective - http://people.mozilla.org/~choller/firefox/coverage/mc-coverage-20130210-29dd80c95b7d/
- Existing code - http://chinhodado.github.io/codecoverage_presenter/
Reference docs
The following is optional reading, for reference purposes only.
- Previous term CodeCoverage meeting notes (optional, reference only) - https://public.etherpad-mozilla.org/p/ucosp_meeting_notes