Oops, forgot about your "static".
It's the same : if one of your tests modifies the static, then for the
same reason, in next test the value should be kept...
On Tue, 7 Dec 2004 13:18:57 +0100, Thibaut BarrÃre
<[EMAIL PROTECTED]> wrote:
> Hi Steve
>
> did you intented to post this to NUnit rat
Hi Steve
did you intented to post this to NUnit rather than NAnt-Users ?
Afaik in a nunit testfixture, isolation between tests in the same
testfixture is not achieved by the framework, which means if you have
another test which initialize your hashtable and do not set back the
hashtable to null i
Hello everyone,
Has anyone seen a problem like this? (this is a contrived example of
the problem)
For some strange reason, when I stop the debugger at BP #1, for the
first time, table_ is **already initialized to a Hashtable, count = 0 (when it
should be null, and thus step into
