Checking mochitest test coverage へのコメント http://mitcho.com/blog/projects/checking-mochitest-test-coverage/ Thu, 31 May 2012 06:07:28 +0000 hourly 1 http://wordpress.org/?v=3.5.1 Philipp von Weitershausen より http://mitcho.com/blog/projects/checking-mochitest-test-coverage/comment-page-1/#comment-3933 Philipp von Weitershausen Wed, 23 Mar 2011 03:37:38 +0000 http://mitcho.com/?p=4253#comment-3933 Wow, I’m happy you were able to use my code so smoothly. This is awesome, I think I’ll be using this patch to mochitests in our upcoming projects :D OMG THIS OPEN SOURCE THING WORKS

On a side note, I’m still working on a general way of instrumenting SpiderMonkey to provide us with coverage. Since the approach here doesn’t work with xpcshell-tests (there’ll always be JS on the stack), we need a generic solution anyway.

]]> sfink より http://mitcho.com/blog/projects/checking-mochitest-test-coverage/comment-page-1/#comment-3931 sfink Wed, 23 Mar 2011 01:20:38 +0000 http://mitcho.com/?p=4253#comment-3931 The instrumentation in https://bugzilla.mozilla.org/show_bug.cgi?id=637393 might help with the speed problem, though it’s not done yet and the output format isn’t really what you want. It accumulates the execution count for every opcode, broken down by which engine executed it (interpreter vs tracejit vs methodjit). The interruptHook disables the tracing JIT and is expensive besides; this instrumentation slows down all execution but doesn’t disable anything and should be much less overhead overall. (interruptHook is doing a full function call per op; bug 637393 executes a couple of additional machine code instructions per op.)

The patch dumps out a disassembly of every JSScript (function or toplevel) on JSContext teardown, together with per-op execution counts and line numbers. So you could massage that into a coverage report. (Sum of all ops executed in a line > 0?) Or maybe better, dump out your own condensed report, though that’ll require trawling through src notes which isn’t all that fun.

I’ve never tried it on a full browser build. You’d need to arrange for the JSOPTION_PCPROFILE bit to be set on all contexts you care about.

It’s probably not baked enough to use for this yet, but any comments/suggestions in the bug will be taken seriously. (Or if you want to take it over, go ahead!)

]]>