2,088
edits
m (→Roundtable) |
|||
Line 115: | Line 115: | ||
* Update on Code Coverage (timr) | * Update on Code Coverage (timr) | ||
** Latest results: [http://people.mozilla.com/~mnandigama/codecoverage_html/ c/c++] and [http://people.mozilla.com/~mnandigama/jscoverage-report/jscoverage.html JS] | ** Latest results: [http://people.mozilla.com/~mnandigama/codecoverage_html/ c/c++] and [http://people.mozilla.com/~mnandigama/jscoverage-report/jscoverage.html JS] | ||
** We had a good discussions with the Content and JS teams last week. Some issues we are looking into are: | ** We had a good discussions with the Content and JS teams last week. Some issues we are looking into are: Specific files with surprisingly low coverage. How coverage for in-lined code is handled. Annotating the coverage results pages with info like: a file was recently re-designed and therefore previous bug data may no longer be valid. Setting up coverage on additional platforms. | ||
** Also see the new [http://mkngama.blogspot.com/2009/08/code-coverage-results-study-faqs.html FAQ] and [https://wiki.mozilla.org/CodeCoverage/Firefly new Code Cov one stop shopping wiki] | ** Also see the new [http://mkngama.blogspot.com/2009/08/code-coverage-results-study-faqs.html FAQ] and [https://wiki.mozilla.org/CodeCoverage/Firefly new Code Cov one stop shopping wiki] | ||
** Other next steps: Identify with the Dev teams which files should be targeted for additional testing. Work with other teams like the Firefox team to understand how this info could be used. Feel free to contact Murali or myself if you want to dig into the data with us. | ** Other next steps: Identify with the Dev teams which files should be targeted for additional testing. Work with other teams like the Firefox team to understand how this info could be used. Feel free to contact Murali or myself if you want to dig into the data with us. |
edits