StatLight

Features New "native" xUnit runner. Contributed by Remo Gloor MSTestProvider: Emit Description, Owner and Properties from a TestMethod into the XML File Now supports MSTest's TestContext.WriteLine(...) - The output will be written to the metadata ... [More] section of the StatLight xml output. Resolved Items fixed an issue where reflecting over assemblies in xap could cause a ReflectionTypeLoadException if assembly referenced another assembly that was not found in the xap. UnhandledExceptionClientEvent are not surfaced -b and -- teamcity dont work together [Less]

Features Run tests straight from a test assembly (no xap required) You should only have to specify the assembly to be tested. StatLight will find all dependend assemblies automatically Feature to allow you to export an MSTest xml report Using a ... [More] Summary Results File with a Generic Test. Use the -r option in conjunction with the --MSGenericTestFormat command Support for custom unit test providers. (This means StatLight will look within your test assemblies for an implementation of IUnitTestProvider) Use the -o, --OverrideTestProvider with a value of MSTestWithCustomProvider Example providers Raven Custom Silverlight Unit Test Provider xUnit Contrib (NOTE: up and coming will be a "native" xUnit runner within StatLight - thanks to https://github.com/remogloor) Updated StatLight build process to include the git hash the build was from as the assembly description attribute. Completely removed any UI for better support on a C.I. server. To get any UI tests to run you have to give it the -b option. Update auto-detect to detect xunit contrib Some benefits to the new architecture outlined above StatLight can now work with your MEF code that depends on use of the DeploymentCatalog StatLight can now be used if your tests depend on resource or other files contained within your xap under test. Using Application.GetResourceStream in Silverlight tests looks in StatLight XAP Added support for the MSTest AssemblyInitialize and AssemblyCleanup attributes Added ability to extend StatLight through MEF See Example Say you want to write a Growl plugin? Added config options where you can override the default coloring used in the console runner. Resolved Items "No communcation from the web browser" error when running large xUnit test suite Feature Request: console usage help documentation indicates that --debug command line option takes a value (i.e. --debug[=VALUE]) Show contents of DescriptionAttribute Fixed the StatLight build so it would work under Powershell (where the build was running under .net 3.5) UnhandledExceptionClientEvent are not surfaced "No communcation from the web browser" error when running large xUnit test suite xUnit runner doesn't recognize Theory tests Update auto-detect to detect xunit contrib Feature Request: console usage help documentation indicates that --debug command line option takes a value (i.e. --debug[=VALUE]) [Less]

Features Run tests straight from a test assembly (no xap required) You should only have to specify the assembly to be tested. StatLight will find all dependend assemblies automatically Feature to allow you to export an MSTest xml report ... [More] Using a Summary Results File with a Generic Test. Use the -r option in conjunction with the --MSGenericTestFormat command Support for custom unit test providers. (This means StatLight will look within your test assemblies for an implementation of IUnitTestProvider) Use the -o, --OverrideTestProvider with a value of MSTestWithCustomProvider Example providers Raven Custom Silverlight Unit Test Provider xUnit Contrib (NOTE: up and coming will be a "native" xUnit runner within StatLight - thanks to https://github.com/remogloor) Updated StatLight build process to include the git hash the build was from as the assembly description attribute. Completely removed any UI for better support on a C.I. server. To get any UI tests to run you have to give it the -b option. Update auto-detect to detect xunit contrib Some benefits to the new architecture outlined above StatLight can now work with your MEF code that depends on use of the DeploymentCatalog StatLight can now be used if your tests depend on resource or other files contained within your xap under test. Using Application.GetResourceStream in Silverlight tests looks in StatLight XAP Added support for the MSTest AssemblyInitialize and AssemblyCleanup attributes Added ability to extend StatLight through MEF See Example Say you want to write a Growl plugin? Added config options where you can override the default coloring used in the console runner. Resolved Items "No communcation from the web browser" error when running large xUnit test suite Feature Request: console usage help documentation indicates that --debug command line option takes a value (i.e. --debug[=VALUE]) Show contents of DescriptionAttribute Fixed the StatLight build so it would work under Powershell (where the build was running under .net 3.5) UnhandledExceptionClientEvent are not surfaced "No communcation from the web browser" error when running large xUnit test suite xUnit runner doesn't recognize Theory tests Update auto-detect to detect xunit contrib Feature Request: console usage help documentation indicates that --debug command line option takes a value (i.e. --debug[=VALUE]) [Less]

After this has posted, I will be updating the codeplex docs. Features Run tests straight from a test assembly (no xap required) You should only have to specify the assembly to be tested. StatLight will find all dependend assemblies ... [More] automatically Feature to allow you to export an MSTest xml report Using a Summary Results File with a Generic Test. Use the -r option in conjunction with the --MSGenericTestFormat command Support for custom unit test providers. (This means StatLight will look within your test assemblies for an implementation of IUnitTestProvider) Use the -o, --OverrideTestProvider with a value of MSTestWithCustomProvider Example providers Raven Custom Silverlight Unit Test Provider xUnit Contrib (NOTE: up and coming will be a "native" xUnit runner within StatLight - thanks to https://github.com/remogloor) Updated StatLight build process to include the git hash the build was from as the assembly description attribute. Completely removed any UI for better support on a C.I. server. To get any UI tests to run you have to give it the -b option. Update auto-detect to detect xunit contrib Some benefits to the new architecture outlined above StatLight can now work with your MEF code that depends on use of the DeploymentCatalog StatLight can now be used if your tests depend on resource or other files contained within your xap under test. Using Application.GetResourceStream in Silverlight tests looks in StatLight XAP Added support for the MSTest AssemblyInitialize and AssemblyCleanup attributes Added ability to extend StatLight through MEF See Example Say you want to write a Growl plugin? Added config options where you can override the default coloring used in the console runner. Resolved Items "No communcation from the web browser" error when running large xUnit test suite Feature Request: console usage help documentation indicates that --debug command line option takes a value (i.e. --debug[=VALUE]) Show contents of DescriptionAttribute Fixed the StatLight build so it would work under Powershell (where the build was running under .net 3.5) UnhandledExceptionClientEvent are not surfaced "No communcation from the web browser" error when running large xUnit test suite xUnit runner doesn't recognize Theory tests Update auto-detect to detect xunit contrib Feature Request: console usage help documentation indicates that --debug command line option takes a value (i.e. --debug[=VALUE]) [Less]

After this has posted, I will be updating the codeplex docs. Features Run tests straight from a test assembly (no xap required) You should only have to specify the assembly to be tested. StatLight will find all dependend assemblies automatically ... [More] Feature to allow you to export an MSTest xml report Using a Summary Results File with a Generic Test. Use the -r option in conjunction with the --MSGenericTestFormat command Support for custom unit test providers. (This means StatLight will look within your test assemblies for an implementation of IUnitTestProvider) Use the -o, --OverrideTestProvider with a value of MSTestWithCustomProvider Example providers Raven Custom Silverlight Unit Test Provider xUnit Contrib (NOTE: up and coming will be a "native" xUnit runner within StatLight - thanks to https://github.com/remogloor) Updated StatLight build process to include the git hash the build was from as the assembly description attribute. Completely removed any UI for better support on a C.I. server. To get any UI tests to run you have to give it the -b option. Update auto-detect to detect xunit contrib Some benefits to the new architecture outlined above StatLight can now work with your MEF code that depends on use of the DeploymentCatalog StatLight can now be used if your tests depend on resource or other files contained within your xap under test. Using Application.GetResourceStream in Silverlight tests looks in StatLight XAP Added support for the MSTest AssemblyInitialize and AssemblyCleanup attributes Added ability to extend StatLight through MEF See Example Say you want to write a Growl plugin? Added config options where you can override the default coloring used in the console runner. Resolved Items "No communcation from the web browser" error when running large xUnit test suite Feature Request: console usage help documentation indicates that --debug command line option takes a value (i.e. --debug[=VALUE]) Show contents of DescriptionAttribute Fixed the StatLight build so it would work under Powershell (where the build was running under .net 3.5) UnhandledExceptionClientEvent are not surfaced "No communcation from the web browser" error when running large xUnit test suite xUnit runner doesn't recognize Theory tests Update auto-detect to detect xunit contrib Feature Request: console usage help documentation indicates that --debug command line option takes a value (i.e. --debug[=VALUE]) [Less]

NOTE: This release is the first on the .net 4.0 framework. If you still need .net 3.5 support you can look back at using StatLight V1.2. Features Replaced the WebServer implementation. Note: Thanks to Jeff Wilcox and Microsoft - Much of ... [More] this change was code ripped out of the Microsoft.Silverlight.Testing's server implementation. (Great head start) Features of new WebServer: Faster startup time No requirement for elevated privileges to start on web server port(s) Easier control over requests made to the StatLight web server. (Specifically allowing StatLight to generate a user friendly note regarding "out of normal usage" web service calls) Added initial support to test with multiple browsers Some basic (not fully tested in all scenarios) support for Firefox Chrome (default - in process browser - the one StatLights always used) Resolved Items from the Issue Tracker Support of NUnit TestCase attribute with test method arguments NOTE: this is not full support - but should cover the most general cases. [Less]

NOTE: This release is the first on the .net 4.0 framework. If you still need .net 3.5 support you can look back at using StatLight V1.2. Features Replaced the WebServer implementation. Note: Thanks to Jeff Wilcox and Microsoft - Much of this change ... [More] was code ripped out of the Microsoft.Silverlight.Testing's server implementation. (Great head start) Features of new WebServer: Faster startup time No requirement for elevated privileges to start on web server port(s) Easier control over requests made to the StatLight web server. (Specifically allowing StatLight to generate a user friendly note regarding "out of normal usage" web service calls) Added initial support to test with multiple browsers Some basic (not fully tested in all scenarios) support for Firefox Chrome (default - in process browser - the one StatLights always used) Resolved Items from the Issue Tracker Support of NUnit TestCase attribute with test method arguments NOTE: this is not full support - but should cover the most general cases. [Less]