Hello- I'm a Google engineer on Google Books in Mountain View and a contributor to Closure Library. I'm doing a bit of curious investigation into the possibility of coverage instrumentation in Chromium. The use case is this:
When bringing up a Closure-style unit test, such as the one for array.js: http://closure-library.googlecode.com/svn/trunk/closure/goog/array/array_test.html I'd like to be able to get statistics about what which lines in the module in question: http://closure-library.googlecode.com/svn/trunk/closure/goog/array/array.js were run. The way I'd envision this is to enable a --js-flags flag in Chromium to dump an execution log to stdout/stderr, which could then be parsed and interpreted (one could generate coverage statistics if each source line and path were logged, with some knowledge of non-statement lines). But at present, it seems there's just facilities for profiling, which just generates a high level report. There's a defunct FF extension project that attempted to do this: https://addons.mozilla.org/en-US/firefox/addon/4837/ Any thoughts or pointers you can give would be appreciated. Thank you, Nathan -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
