nunit-core team mailing list archive
-
nunit-core team
-
Mailing list archive
-
Message #01226
Re: [Bug 659969] Re: Config documentation inaccurate or functionality non-existent
This should work, running your tests in the STA and at Lowest priority.
Do I understand that it works correctly if you you the same entries
into x.Tests.dll.config
and run the single assembly directly? If so, I'm surprised but it
indicates where to look
for the problem.
Charlie
On Thu, Oct 14, 2010 at 1:27 AM, Dennis Jakobsen
<659969@xxxxxxxxxxxxxxxxxx> wrote:
> I have a Main.nunit file with my assemblies listed..
>
> <NUnitProject>
> <Settings activeconfig="Debug" />
> <Config name="Debug" appbase="bin\Debug" binpathtype="Auto">
> <assembly path="x.Tests.dll" />
> <assembly path="y.Tests.dll" />
> .. and so on..
>
> and yes i have the config section like the document example:
> <configSections>
> <sectionGroup name="NUnit">
> <section name="TestCaseBuilder" type="System.Configuration.NameValueSectionHandler"/>
> <section name="TestRunner" type="System.Configuration.NameValueSectionHandler"/>
> </sectionGroup>
> </configSections>
> <NUnit>
> <TestRunner>
> <add key="ApartmentState" value="STA" />
> <add key="ThreadPriority" value="Lowest" />
> </TestRunner>
> </NUnit>
>
> The cmd line i run is (from cc.net.. basedirectory is where Main.nunit is):
> nunit-console.exe Main.nunit /xml:../trunk-NUnit-results.xml /exclude=TDD,SMTP /nologo /nodots
>
> --
> 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