[Testing] functioning "peekaboo" code available for sugar-jhbuild

[Titus Brown]

On Sat, Apr 12, 2008 at 11:13:19PM -0700, Titus Brown wrote:
-> 
-> 	http://iorich.caltech.edu/~t/git/sugar/

Oops, I should mention: this git branch also has figleaf code coverage
recording enabled for sugar independently of the peekaboo stuff.
However, you have to explicitly write the coverage information out to
disk periodically.

One solution is to just add an gobject_idle_callback that calls
figleaf.write_coverage('.figleaf').

(I wrote peekaboo partly because I was so annoyed at having to write
stuff to disk :)

--

To produce HTML output from figleaf, find a .figleaf file and run

% figleaf2html /path/to/.figleaf

This will produce a directory 'html/' containing annotated versions of
all of the Python code executed.

You can also specify multiple .figleaf files:

% figleaf2html /some/path/.figleaf /some/other/path/.figleaf

This combines multiple figleaf trace records.

--

If people think this style of coverage is useful and want a separate
branch or config setup to write straight coverage information, let me
know.  In the absence of automated tests, I think peekaboo is more
useful, but I'm open to doing whatever people actually *find* useful!

cheers,
--titus