This has been per-project for almost a decade now, which if nothing else shows it's an uncommon problem. :-)
I gather you are running each test assembly separately rather than through an nunit project. That would require modifying each project config file. This may also explain why modifying the nunit project config is not doing anything for you. All that said, I agree that it could be a commandline option, allowing you to use a script to run all your tests at a lower priority. If you agree, I'll re-focus this bug as a feature request to add the option. Charlie On Wed, Oct 13, 2010 at 1:09 PM, Dennis Jakobsen <659...@bugs.launchpad.net> wrote: > > Our solution has about 20 sub projects.. setting a run-once nunit parameter > on every project .dll ..and every future sub project added to the solution > seems kinda wrong.. what priority the nunit thread has.. has got nothing to > do with my projects.. > > Ideally it should be an nunit.config setting and cmdline parameter. > > -- > 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.. _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : nunit-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
