On Monday 2013-06-24 18:50 -0700, Clint Talbert wrote: > So, the key things I want to know: > * Will you support code coverage? Would it be useful to your work to > have a regularly scheduled code coverage build & test run? > * Would you want to additionally consider using something like > JS-Lint for our codebase?
For what it's worth, I found the old code coverage data useful. It was useful to me to browse through it for code that I was responsible for, to see: * what code was being executed during our test runs and how that matched with what I thought was being tested (it didn't always match, it turns out) * what areas might be in need of better tests When I was looking at it, I was mostly focusing on the mochitests in layout/style/test/. (I worry I might have been one of a very small number of people doing this, though.) I think using code coverage tools separately on standards-compliance test suites might also be interesting, e.g., to see what sort of coverage the test suite for a particular specification gives us, and whether there are tests we could contribute to improve it. -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla http://www.mozilla.org/ 𝄂 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
