Comments on: Instantiating a WPF control from an NUnit test

By: louis vuitton for sale

louis vuitton for sale — Wed, 07 Jul 2010 07:53:18 +0000

Well , the view of the passage is totally correct ,your details is really reasonable and you guy give us new balance 1300 valuable informative post, I totally agree the standpoint of upstairs. I often surfing on this forum when I m free and I find there are so much good information we can learn in this forum!

By: Stefan Andersson

Stefan Andersson — Mon, 07 Jun 2010 19:04:47 +0000

Chris,

excellent post; it seems with R#5 JetBrains has flipped this, so the runner runs in MTA.

By: Unit Test MsBuild Custom Task

Unit Test MsBuild Custom Task — Mon, 01 Feb 2010 04:35:44 +0000

[...] doesn't matter in this case. It is however annoying. I was able to make NUnit run in STA mode by creating a config file for the test assembly. NUnit has an attribute to set the apartment mode but this didn't seem to [...]

By: Juan

Juan — Thu, 10 Dec 2009 01:38:21 +0000

Your CrossThreadTestRunner class worked perfectly! Thank you!

By: Eric

Eric — Thu, 27 Aug 2009 15:48:59 +0000

Works like a charm! Thanks!

By: brett

brett — Mon, 08 Jun 2009 15:49:50 +0000

Thanks a million finally found a solution to my problem. Where I kept having issues with the STA thread using different test runners.

brett

By: Sunit Joshi

Sunit Joshi — Thu, 16 Apr 2009 21:51:09 +0000

Thanks Chris…this helped me too. My failed tests were driving me nuts earlier !!

By: Ben Rice

Ben Rice — Thu, 05 Feb 2009 17:59:01 +0000

I’ve had no luck reading a config file in my test project.

For my dll ProjectTests.dll I created a file ProjectTests.config with the configuration you have above.

I’m testing:
Assert.AreEqual(“STA”, ConfigurationManager.AppSettings["ApartmentState"]); // fails, is null

In fact, Configuration.AppSettings has no keys at all. Any ideas?

By: What's the best way to do WPF application unit test | keyongtech

What's the best way to do WPF application unit test | keyongtech — Thu, 22 Jan 2009 10:18:04 +0000

[...] as usual winforms PS: see there how to solve the issue with instantiating WPF controls from nunit http://www.hedgate.net/articles/2007…-an-nunit-test — WBR, Michael Nemtsev [.NET/C# MVP]. My blog: http://spaces.live.com/laflour Team blog: [...]

By: Chris

Chris — Thu, 11 Dec 2008 11:01:31 +0000

Unfortunately, the plugin I was using for showing code nicely made all xml-tags lowercase, which broke the config file I include in the post. I have now edited it, so it looks like JohnD recommends above (and how it would have looked if not for that plugin…), so now it should work better.

By: Richard

Richard — Fri, 05 Sep 2008 14:16:36 +0000

Hey Chris,
You have a bunch of UPPERCASE stuff in those samples that breaks them. Any chance of editing them to work correctly?

By: Chris

Chris — Fri, 05 Sep 2008 06:30:33 +0000

Hi Drew,

I am not quite sure what you mean by configuring Resharper? You could of course create a template to avoid having to write the boiler-plate code manually each time, but maybe you are referring to something else?

By: Drew

Drew — Fri, 29 Aug 2008 06:49:47 +0000

Hi Chris,

I was wondering if you are aware of a way of configuring resharper to use these settings?

Cheers,
Drew

By: Yingqiang Woo

Yingqiang Woo — Tue, 26 Feb 2008 08:19:56 +0000

hi,JohnD
could you send me the config file, wuyq101 @ gmail.com.
Thank you very much.
i am using Nunit 2.4.3, i just can’t get it work.

By: Chris

Chris — Tue, 05 Feb 2008 14:44:15 +0000

John, thanks for sharing that information. Hope it helps others in the same situation.

By: JohnD

JohnD — Thu, 24 Jan 2008 22:54:34 +0000

Hey!

The XML I put in the last post didn’t show up. So, I’ll describe what I had to do:
1. Create a config file for the test project or test DLL. Making the changes in NUnit’s main config file didn’t get the job done.
2. NUnit is case sensitive so the XML names must be NUnit and TestRunner rather than nunit and testrunner.
3. The setting of NUnit/TestRunner must be within the configuration tag rather than outside it as shown in the original example.

When set up like that, Nunit 2.4.6 runs WPF tests just fine!
Good luck!
JohnD

By: JohnD

JohnD — Thu, 24 Jan 2008 22:43:02 +0000

The following test project config file gets the job done for NUnit 2.4.6

By: JohnD

JohnD — Wed, 23 Jan 2008 22:05:12 +0000

Hey Chris,

What version of NUnit are you using? I tried your technique to run all tests as STA with NUnit 2.4.6 and had no luck at all! Are we using different versions of NUnit or is there some magic setting that I failed to set appropriately? Here are the details behind my questions:

When I set up the config file as you showed in the example, nunit-console complained that there were two root elements and pointed at the line.

I moved the section inside the section and NUnit complained that sectiongroup was an unrecognized token. I removed the stuff and ended up with:

…

At this point, nunit-console could successfully parse the config file but all the tests failed with the System.InvalidOperationException indicating that the config file changes were not having the desired result.

Same sort of thing happened with the GUI test runner.

Thanks for any help
John

By: Greg Finzer

Greg Finzer — Fri, 28 Sep 2007 16:37:48 +0000

Chris, thanks for creating this article. I have recently created an NUnit Test Generator. What do you think would be useful features for interacting with WPF for the test generator?

http://www.kellermansoftware.com/p-30-nunit-test-generator.aspx