Forum Archives
Resources Support
Forums › NCover Community Edition Suggestions / Feature Requests › Default directory for coverage results

Default directory for coverage results

Default directory for coverage results

A default directory, where the coverage results will be stored seems to be very helpful, from my point of view. This default directory can be set using an environment variable.

To use this it would be necessary to add a guid to each coverage file to make it unique.

Having this feature would enable runing various tests and gathering the whole information finally. NCoverExplorer supports some nice merge feature in between.

Re: NCover on web services in ASP.Net

Hi,

Did you find any way of getting this up and running. If so could you please write to me the workaround as I am stuck with exactly the same problem.

 

Re: report containing "Excluded From Coverage Results"

Thanks for the feedback and suggestion. I'm a bit snowed at the moment with the day job but hopefully in a few weeks can get back to NCoverExplorer again. Without looking at the code I can't comment on this much more at this point sorry - in theory it sounds fairly trivial to add.

Re: display of anonymous delegates

Hi Thomas,

Thanks for reporting the problem. I will discuss this with Peter to see if he can improve things on the NCover side to exclude this code from the output for NCover 1.5.7 or a future release. I am reluctant to add even more compensating kludges in NCoverExplorer (I have more than enough in there already to cope with various NCover version behaviour!) unless it genuinely is too difficult for Peter to exclude this, but it surely should be possible one way or another.

Incidentally there is a similar problem with "yield" which also gives NCoverExplorer a bit of a problem to deal with.

Re: display of anonymous delegates

I tried this with 1.5.8 and 2.0.2 (licensed Pro version) and the behavior is still there. Any progress on this issue?

Thanks.

Dan

[quote="forums":f4ea8]Hi Thomas, Thanks for reporting the problem. I will discuss this with Peter to see if he can improve things on the NCover side to exclude this code from the output for NCover 1.5.7 or a future release. I am reluctant to add even more compensating kludges in NCoverExplorer (I have more than enough in there already to cope with various NCover version behaviour!) unless it genuinely is too difficult for Peter to exclude this, but it surely should be possible one way or another. Incidentally there is a similar problem with "yield" which also gives NCoverExplorer a bit of a problem to deal with.[/quote:f4ea8]