|
Loading...
|
nunit-discuss@googlegroups.com
[Prev] Thread [Next] | [Prev] Date [Next]
Re: [nunit-discuss] Re: Eliminating Special Settings in the Test Config File Charlie Poole Wed Feb 01 12:08:12 2012
Hi Peter and Everyone, I thought that this topic might need a final wrapup. Beginning with the fourth beta, coming out shortly, NUnit 2.6 will no longer support this setting (or any settings) in the config file. As a temporary workaround, you can use -apartment:STA on the commandline for the console runner (but not the gui). As a long-term solution, use RequiresSTAAttribute at the level of the test case, the test fixture or a higher-level setup fixture. If you like, you can even use it at the assembly level. Charlie On Sun, Jan 1, 2012 at 5:22 PM, Charlie Poole <[EMAIL PROTECTED]> wrote: > Hi Peter, > > It's easy enough to have a TestPackage setting that controls the > ApartmentState, > even if we don't necessarily expose it to the average user. I'll look > into doing that. > > That said, I wonder what would happen if you simply used [RequiresSTA] at > a higher level: TestFixture, SetUpFixture or even assembly. > > Charlie > > > > On Sun, Jan 1, 2012 at 1:55 PM, Peter Arius <[EMAIL PROTECTED]> wrote: >> Hi Charlie, >> >> thanks for asking :). >> >> We need the ApartmentState setting, because we "abuse" NUnit for GUI >> tests, too, and for some interactions with controls it is not >> sufficient to use [RequiresSTA], but one has to avoid using different >> threads, too. If the test thread runs under MTA, every [RequiresSTA] >> uses a new thread. >> >> We'd be even happier if the test thread ApartmentState could be >> controlled via a TestPackage property instead of the config file >> entry, because our own runner could set it easily in the TestPackage. >> >> Best regards, >> Peter >> >> On 30 Dez. 2011, 14:46, Charlie Poole <[EMAIL PROTECTED]> wrote: >>> Hi All, >>> >>> The test config file can have a special NUnit section, which I'm thinking >>> of removing it. I suspect it isn't used much, but I'd like to hear from >>> those >>> who use it before I take action. >>> >>> The following can be set in the NUnit section: >>> >>> * OldStyleTestCases - to enable recognition of methods starting with 'Test' >>> * ApartmentState - default apartment state for the test thread >>> * ThreadPriority - priority for the test thread >>> * DefaultLogThreshold - What level of logging (currently log4net only) to >>> display in the Gui. >>> >>> If you rely on any of these, please let me know which ones and whether you >>> could do without them or would need to have some alternative method to >>> specify the settings. >>> >>> All of these will be removed in NUnit 3.0 but I'll remove them early (2.6) >>> if they are not being used. >>> >>> Charlie >> >> -- >> You received this message because you are subscribed to the Google Groups >> "NUnit-Discuss" group. >> To post to this group, send email to [EMAIL PROTECTED] >> To unsubscribe from this group, send email to [EMAIL PROTECTED] >> For more options, visit this group at >> http://groups.google.com/group/nunit-discuss?hl=en. >> -- You received this message because you are subscribed to the Google Groups "NUnit-Discuss" group. To post to this group, send email to [EMAIL PROTECTED] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nunit-discuss?hl=en.
- [nunit-discuss] Eliminating Special Settings in the Test Config File Charlie Poole 2012/02/01
- [nunit-discuss] Re: Eliminating Special Settings in the Test Config File Peter Arius 2012/02/01
- Re: [nunit-discuss] Re: Eliminating Special Settings in the Test Config File Charlie Poole 2012/02/01
- Re: [nunit-discuss] Re: Eliminating Special Settings in the Test Config File Charlie Poole 2012/02/01 <=
- [nunit-discuss] Re: Eliminating Special Settings in the Test Config File Charlie Poole 2012/02/01