[IronPython] Code Coverage

Martin Maly Martin.Maly at microsoft.com
Thu Jun 22 18:51:44 CEST 2006

The debugger support works really well with IronPython. There are some limitations, but the basic experience is truly pleasant.

As for profilers, code coverage, the limitations likely to make experience less pleasant are our function name mangling and use of lightweight code generation which both will affect the code coverage and profiling tools experience.


-----Original Message-----
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Hernan Martinez Foffani
Sent: Thursday, June 22, 2006 9:00 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Code Coverage

> Unfortunately all the Python code coverage tools use ``sys.settrace``
> which isn't implemented in IronPython. This (I guess) is because Python
> stack frames and code objects aren't used in IronPython.
> .
> .
> .
> Two alternative ideas.
> 1) Implement a 'cut down' version of sys.settrace which only implements
> what is possible.
> 2) Alternatively a callback hook on the C# side could be implemented, so
> that as IronPython enters a new line we could cache this information -
> and generate a report once execution has stopped.

Profilers, Debugger and Coverage tools for .NET use the
.NET Profiling API.

Has anyone tried these with IronPython?

users mailing list
users at lists.ironpython.com

More information about the Ironpython-users mailing list