Re: Use of ExpectedExceptionAttribute class in unit tests

On 12/20/05, Charlie Poole <cpoole@xxxxxxxxxxxxxxxxxxx> wrote:
> "Not welcome" is a pretty strong statement.

I did not mean to be offensive. Sorry if it sounds that way. Just then
there were some post(s) supporting the idea, but as all we know, there
were no time for this. Now, as the new version is out, I would like to
offer my time again :)

>
> "Exceeded our bandwidth" is more accurate.

I do understand.

>
> One of the changes discussed in the past is in our 2.2.4 release. Additional
> changes to ExpectedException are in the 2.4 release plan. Boris agreed to
> work on making his particular idea an _extension_ rather than a change to
> the NUnit core. Our focus on getting the extensibility mechanism working
> right is aimed at exactly this problem: many people want many things out of
> NUnit, and they can't all be in the core - or at least we don't think they
> should be.
>
> Charlie

Extensions - as far as I understand - this is the way to create "new"
test scenarios (attributes, etc.). Or adding functionality to the
existing ones. What am I missing. And is there any documentation where
to start from? If I did not understand, and using these new mechanism
changes can be made to existing scenarios, I'll be glad to work with
Boris to prepare more broad extension than just COM exception
checking.

And, if I got it right, I still think that change in the base
implementation of ExpectedException, which allows custom property test
still holds water, as it can be a good base for additions, needed by
Boris and others.

--
--
Svetoslav Milenov (Sunny)


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click