UI and test speed much improved, thanks. I do notice that the Test Stage doesn’t show anything added to the TestPanel unless I click on the splitter, then it updates and shows every time a test add something.

Hi Jeff
Thanks for all the work you have done to make TDD for Silverlight at least a bit sane. I have been using your Silverlight Unit Test Framework with Silverlight 3 and did the conversions you mentioned earlier to get it running with nunit. The best thing is that I was able to run the tests from Resharper and from nunit-console.exe on my Hudson build server and display the test results I came across a problem with running tests that needed to be run on the UI Thread, but was able to work around it with the following class that I created:
public static class UIThread
{
public static void Run(Action action)
{
Dispatcher dispatcher = TryGetInstance(() => Deployment.Current.Dispatcher)
?? TryGetInstance(() =>
{
PropertyInfo propertyInfo = typeof (Dispatcher).GetProperty(
“MainDispatcher”, BindingFlags.Static | BindingFlags.NonPublic);
return (Dispatcher) propertyInfo.GetValue(null, new object[] {});
})
?? TryGetInstance(() => Application.Current.RootVisual.Dispatcher);
if (dispatcher != null)
{
dispatcher.BeginInvoke(action);
}
else
{
SynchronizationContext synchronizationContext = TryGetInstance(() => SynchronizationContext.Current);
if (synchronizationContext != null) synchronizationContext.Send(state => action(), null);
else action();
}
}

private static T TryGetInstance(Func func)
where T : class
{
T instance = null;
try
{
instance = func();
}
catch (Exception) { }
return instance;
}
}

This class was able to run the test on the UI thread in the test runner as well as in resharper and through nunit-console. My world was complete!
Then I upgraded to SL4 and none of those dispatcher calls work any more when I am running the tests outside of your test runner. Most of the calls give an error about ‘agcore.dll’ is missing. This used to work in SL3.
What would I need to do to get a dispatcher thread when running outside of the silverlight app? Any ideas? Is there some Silverlight initialisation call I can make?

Thanks
-Mark

Hi Jeff
Thanks for your quick reply.
It is not running inside a Silverlight plugin.
It is basically just a Silverlight Unit Test Framework project where I have made all dlls copy local (except for mscorlib) and have used the nunit test framework (compiled for silverlight). I am then using the nunit-console test runner to run the nunit tests in the compiled dll of the project.
The strange thing is that in SL3 when I used this code I would be able to access the dispatcher using at least one of the methods above, but in SL4 none of the methods work(they now give the ‘agcore’ missing error), and there doesn’t seem to be any dispatcher instance that I can access.
Is there any way of instantiating the ui thread without having to run it inside the silverlight application environment (with a dependency on ‘agcore’)?

Hi Jeff,

Thanks for releasing this and for your continued support of Silverlight testing

One problem I’ve found though…
We have a continuous integration server which runs our SL tests using the msbuild command line and in some cases we have a need to use the tag expression which worked great in the November toolkit release
Example:
msbuild -t:test /p:tagexpression=TagToRun

But this does not seem to work in the new version, I also tried setting the tag expression in the App.xaml.cs

Example:
UnitTestSettings settings = new UnitTestSettings();
settings.TestAssemblies.Add(Assembly.GetExecutingAssembly());
UnitTestSystem.SetStandardLogProviders(settings);
settings.TestHarness = new UnitTestHarness();
UnitTestSystem.SetTestService(settings);
settings.TagExpression = “TagToRun”;
this.RootVisual = UnitTestSystem.CreateTestPage(settings);

Thanks in advance

I’ve been struggling to get the framework to run in Express Edition or VS2010 and finally downloaded WP7UnitTestsSampleApp from http://smartypantscoding.com/a-cheat-sheet-for-unit-testing-silverlight-apps-on-windows-phone-7. That worked in both editions.

Turns out the test project must be targe Windows OS 7.0 or you get:
Cannot find a Resource with the Name/Key typeNameConverter [Line: 47 Position: 24]

Happy coding.