nunit-core team mailing list archive
-
nunit-core team
-
Mailing list archive
-
Message #01233
Re: [Bug 659969] Re: Config documentation inaccurate or functionality non-existent
With tests! :-) Did you have some sort of test that failed, leading to your
initially filing this bug?
If not, write a test that queries the apartment state and priority of the thread
it's running on. For example, if you test for STA, it should fail without using
the config file setting and pass when you use it otherwise.
It's also helpful to write a test to verify that you are accessing the
config file. This is easily done with an AppSetting that sets up
an arbitrary name/value pair you can test.
Charlie
On Wed, Oct 20, 2010 at 1:11 AM, Dennis Jakobsen
<659969@xxxxxxxxxxxxxxxxxx> wrote:
> Can you tell me how you confirm them working? then i'll tell you if my
> example works..
>
> --
> Config documentation inaccurate or functionality non-existent
> https://bugs.launchpad.net/bugs/659969
> You received this bug notification because you are a member of NUnit
> Developers, which is subscribed to NUnit V2.
>
--
Config documentation inaccurate or functionality non-existent
https://bugs.launchpad.net/bugs/659969
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
Status in NUnit V2 Test Framework: New
Bug description:
this page: http://nunit.org/index.php?p=configFiles&r=2.5.7 describes how placing a config file with certain parameters can change the behaviour of running nunit..
Now if only any of them worked..
References