[Mono-list] Question on core test support in Mono

[Rodolfo Campero]

IIRC there is a module called "monocov" in CVS. I took a look at it some 
time ago, but I can't remember right now who made it.
Check it out and see if it fulfill your needs.
Cheers,
Rodolfo


>From: "David P. Bowler" <dbowler@hegemony.com>
>To: <mono-list@lists.ximian.com>
>Subject: RE: [Mono-list] Question on core test support in Mono
>Date: Mon, 29 Mar 2004 07:41:14 -0600
>
>
>Just thought I'd re-ask and elaborate a bit...
>
>I am not talking about Nunit type tools, those are great for understanding
>the success/failure of tests... I am talking about innate profiling to
>easily understand that all functions within a project have been covered by 
>a
>test. The term in question is "Code-Coverage" and it is simply a way of
>knowing during the running of a test-suite that all of the code has been
>excercised. It has nothing to do with the success or failure of the tests
>calling the code.
>
>In test-driven development, writing test cases is easy. Knowing that you
>have written enough test cases is not. All too often portions of the code
>are missed or some conditions are not met, so entire sub-sections are never
>excercised.
>
>So, having elaborated what I meant, can anyone tell me if there is any such
>support existing or planned for Mono?
>
>-----Original Message-----
>From: mono-list-admin@lists.ximian.com
>[mailto:mono-list-admin@lists.ximian.com] On Behalf Of David P. Bowler
>Sent: Friday, March 26, 2004 10:27 AM
>To: mono-list@lists.ximian.com
>Subject: [Mono-list] Question on core test support in Mono
>
>
>
>Hello...
>
>I just read an article in MSDN magazine about writing profiler DLLs for
>dotNet that you can tailor to your individual apps to ensure that your test
>programs cover 100% of your code. The profilers simply filter out calls to
>the CLR based upon some criteria built in and they write out listings of 
>all
>functions or even blocks of code that have been hit when running a test
>program.
>
>Unfortunately for dotNet in this instance, this is something that must be
>written and on a per application basis if you are into hard-core 
>test-driven
>development and want to PROVE that your tests give you 100% code-coverage.
>
>So, what I am wondering is if Mono currently has this or if there is any
>intent to put supportiong functionality like this in at the CLR level that
>can optionally be turned on to help test-driven code-coverage oriented
>development?
>
>Cheers,
>David
>
>_______________________________________________
>Mono-list maillist  -  Mono-list@lists.ximian.com
>http://lists.ximian.com/mailman/listinfo/mono-list
>
>_______________________________________________
>Mono-list maillist  -  Mono-list@lists.ximian.com
>http://lists.ximian.com/mailman/listinfo/mono-list

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963