On 6/25/14, 8:15 AM, Jason Orendorff wrote:
We're considering building a JavaScript API for dynamic analysis of JS
code.
Here's the sort of thing you could do with it:
- Gather code coverage information (useful for testing/release mgmt?)
As someone who develops JS for Firefox features, code coverage is near
the top of my list of wants.
I want it as a development aid to ensure the tests I write cover the
code I want/need them to. Just a few weeks ago we had an FHR shutdown
hang because of a typo that was getting hit in a (fortunately rare)
branch I thought we had test coverage for.
I want code coverage so I know when I'm working with unfamiliar code I
have an idea of how robust the test coverage is so I can adjust my patch
and review rigor appropriately.
I want code coverage so automation could potentially do things like warn
when changed lines in a patch aren't being tested - something that will
make me think twice about granting review.
I want code coverage to quantify how much our zeal to disable
intermittent failures is leading to reduced test coverage - something
that will snowball into increased technical debt and lead to lower
productivity.
I want code coverage because we can use it in automation to identify
what changes impact what tests, which potentially leads to us executing
a more minimal set of tests for changes.
Code coverage is a flashlight that illuminates a very dark alley of
JavaScript development today. I can't wait to have it so I can apply
more rigor to developing JavaScript. I also believe that good code
coverage tools can increase developer productivity and allow us to move
faster.
On behalf of JavaScript developers everywhere, I implore you to build
this functionality.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
