To fix this, I edited the Microsoft.Silverlight.Toolkit.Build.targets file that came with the toolkit release, and in the target “RunTests”, for the RunUnitTestsTask action, I changed ContinueOnError=”true” to ContinueOnError=”$(ContinueOnError)”. Then at the commandline I could pass /p:TreatTestFailuresAsErrors=true;ContinueOnError=false to make the task fail on failed tests.

I learned a lot about the controls locations while I looked into it though, and made my own blog post about all of the Silverlight 4 Beta controls, their Namespaces, Assemblies, and Assembly paths at:

http://blogs.netconnex.com/2010/02/silverlight-4-beta-control-namespaces.html

Others may find the info there helpful.

Thanks!

When I create a Silverlight 4 Application project (with website) in VS2010 however, I don’t see the Silverlight Tookit controls (like the charts, etc) in the toolbox. The regular Silverlight controls are there, but not the tookit controls.

Im sure I’m being brain dead, but can you point me in the right direction to get those toolkit controls to show up in the toolbox in VS2010? What about in the Expression Blend 4 Preview?

Thanks!

I get the ‘TestMethod’ information which includes the name (among other).
If I use the ‘Description’ attribute on a test case, then I also get the in the test details in the trx.
However if I use the ‘Priority’ attribute on the test case, then this is not logged in the trx file.

1. Is there any documentation on which attributes are logged in the trx file?
2. Is it possible to customize what is logged?
2. I would like to create my own attribute type, how can I have this logged in the trx?

The reason for asking is that I’d like to do some custom parsing of the log files, and being able to group the tests based on certain criteria would be useful.

Thanks,

All test names are implicit tag expressions, so if you have a test method called “MyTest1″ you should be able to run with the parameter tagexpression=MyTest1.

@Angela,
It seems like it’s a browser issue. I tried with chrome and I got the same error you did. Firefox is the only one that seems to be working.

Unfortunately, our build environment runs on XP and is restricted to Internet Explorer only. If I can’t convince our admins to install Firefox, I’ll have to wait for a future release that addresses the XP/IE issue.

Thanks.

The plugin failing to load is a rare one indeed – but one thing you can try and do in case this is just an issue with unhandled exceptions bubbling up to the browser instead of the test framework, you could modify your app’s unhandled exception handler goo inside of App.xaml.cs to no longer include the ReportErrorToDOM() method.

One major issue with the Silverlight unit test framework is that it is a Silverlight application in and of itself, effectively self hosted – so if anything majorly wrong happens (wild browser crash, plugin AV, wild CLR bug, etc.) then you’ll probably not get a chance to respond to the problem and get results. So I dunno what the right answer is.

On the timeouts, I don’t have a great answer. At least on our team, we have tens of thousands of test methods in some test assemblies… so it’s kind of a waste to have a forced timeout of say 30 minutes – because it’s possible on a very slow machine, or VM, that 30 minutes would not even be enough for us… but I will admit, timeout behavior in the past was implemented and has probably regressed in the shipped build. Not something we rely on much.

-Jeff

Look in “C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\ProjectTemplates\CSharp\Silverlight\1033\” or similar paths.