It is my pleasure to introduce you all to our project to collect code coverage!
Motivation Knowing code coverage statistics and code coverage specifics can help evaluate risk in code: It can show what test suites cover what lines, it can show if new code is covered by an existing test. There are many other exciting insights we can extract from code coverage. But first, we must collect it. The Problem The biggest problem we face is scale: Firefox has many LoC, it is composed of multiple languages, it is run on multiple platforms, and the test suites are split among hundreds of machines for a single build. History For just over a year, this CodeCoverage project has had number of excellent contributors from various Universities across Canada[1]. They did the exploratory work required to solve the problems of scaling collection and aggregation so to handle the Mozilla-scale problem with code coverage. If any of those contributors are reading this: Thank you! The Plan For the next month we will be working on c++ coverage, Rust coverage and validating the data and process. There are many unknowns and I will have more concrete deliverables in the next update. The details of that plan is in our freshly minted planning document [2]. There you can find bugs, and code links. If you are interested in more, please contact me [3] I will send out monthly emails with our progress, some links where you see our progress, and our future plans. [1] UCOSP (Undergraduate Capstone Open Source Projects)http://ucosp.ca/ [2] The actual plan: https://docs.google.com/document/d/1dOWi18qrudwaOThNAYoCMS3e9LzhxGUiMLLrQ_WVR9w/edit# [3] Kyle Lahnakoski email: klahnako...@mozila.org irc: ekyle on #at...@irc.mozilla.org _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
