Posted
over 13 years
ago
by
staxmanade
Breaking Change
--MSGenericTestFormat option has been replaced by --ReportOutputFile:MSGenericTest
Features
New "native" xUnit runner. Contributed by Remo Gloor
MSTestProvider: Emit Description, Owner and Properties from a TestMethod into the XML
... [More]
File
Now supports MSTest's TestContext.WriteLine(...) - The output will be written to the metadata section of the StatLight xml output.
Added NUnit xml report formatting to the output types.
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
Running under WinXP
Statlight -c does not run tests after the first run when build xap file is locked
Fixed the dll only option that would fail when run against a dll that did not reference the Microsoft.Silverlight.Testing.dll. This fixed issues with AGUnit dll only support. [Less]
|
Posted
over 13 years
ago
by
staxmanade
Breaking Change
--MSGenericTestFormat option has been replaced by --ReportOutputFile:MSGenericTest
Features
New "native" xUnit runner. Contributed by Remo Gloor
MSTestProvider: Emit Description, Owner and Properties from a TestMethod into the XML
... [More]
File
Now supports MSTest's TestContext.WriteLine(...) - The output will be written to the metadata section of the StatLight xml output.
Added NUnit xml report formatting to the output types.
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
Running under WinXP
Statlight -c does not run tests after the first run when build xap file is locked
MSTestProvider: Emit Description, Owner and Properties from a TestMethod into the XML File
Fixed the dll only option that would fail when run against a dll that did not reference the Microsoft.Silverlight.Testing.dll. This fixed issues with AGUnit dll only support. [Less]
|
Posted
over 13 years
ago
by
Breaking Change
--MSGenericTestFormat option has been replaced by --ReportOutputFile:MSGenericTest
Features
New "native" xUnit runner. Contributed by
Remo Gloor MSTestProvider: Emit Description, Owner and Properties from a TestMethod into
... [More]
the XML File
Now supports MSTest's TestContext.WriteLine(...) - The output will be written to the metadata section of the StatLight xml output.
Added NUnit xml report formatting to the output types.
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
Running under WinXP
Statlight -c does not run tests after the first run when build xap file is locked
MSTestProvider: Emit Description, Owner and Properties from a TestMethod into the XML File
Fixed the dll only option that would fail when run against a dll that did not reference the Microsoft.Silverlight.Testing.dll. This fixed issues with AGUnit dll only support.
[Less]
|
Posted
over 13 years
ago
by
staxmanade
Until this is "officially released" just pull the latest build from TeamCity
Breaking Change
--MSGenericTestFormat option has been replaced by --ReportOutputFile:MSGenericTest
Features
New "native" xUnit runner. Contributed by Remo Gloor
... [More]
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 section of the StatLight xml output.
Added NUnit xml report formatting to the output types.
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
Running under WinXP
Statlight -c does not run tests after the first run when build xap file is locked
MSTestProvider: Emit Description, Owner and Properties from a TestMethod into the XML File
Fixed the dll only option that would fail when run against a dll that did not reference the Microsoft.Silverlight.Testing.dll. This fixed issues with AGUnit dll only support. [Less]
|
Posted
over 13 years
ago
by
staxmanade
Until this is "officially released" just pull the latest build from TeamCity
Breaking Change
--MSGenericTestFormat option has been replaced by --ReportOutputFile:MSGenericTest
Features
New "native" xUnit runner. Contributed by Remo Gloor
... [More]
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 section of the StatLight xml output.
Added NUnit xml report formatting to the output types.
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
Running under WinXP
Statlight -c does not run tests after the first run when build xap file is locked
MSTestProvider: Emit Description, Owner and Properties from a TestMethod into the XML File
Fixed the dll only option that would fail when run against a dll that did not reference the Microsoft.Silverlight.Testing.dll. This fixed issues with AGUnit dll only support. [Less]
|
Posted
over 13 years
ago
by
staxmanade
Until this is "officially released" just pull the latest build from TeamCity
Breaking Change
--MSGenericTestFormat option has been replaced by --ReportOutputFile:MSGenericTest
Features
New "native" xUnit runner. Contributed by Remo Gloor
... [More]
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 section of the StatLight xml output.
Added NUnit xml report formatting to the output types.
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]
|
Posted
over 13 years
ago
by
Bug in 1.4 related to U.I. tests and TeamCity
-b and -- teamcity dont work together. If you need U.I. test support it's recommended that you use a recent
TeamCity build
Features
Run tests straight from a test assembly (no xap required)
... [More]
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 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]
|
Posted
over 13 years
ago
by
staxmanade
Bug in 1.4 related to U.I. tests and TeamCity -b and -- teamcity dont work together. If you need U.I. test support it's recommended that you use a recent TeamCity build
Features
Run tests straight from a test assembly (no xap required)
You should
... [More]
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 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]
|
Posted
over 13 years
ago
by
staxmanade
Breaking Change
--MSGenericTestFormat option has been replaced by --ReportOutputFile:MSGenericTest
Features
New "native" xUnit runner. Contributed by Remo Gloor
MSTestProvider: Emit Description, Owner and Properties from a TestMethod into the XML
... [More]
File
Now supports MSTest's TestContext.WriteLine(...) - The output will be written to the metadata section of the StatLight xml output.
Added NUnit xml report formatting to the output types.
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]
|
Posted
over 13 years
ago
by
staxmanade
Breaking Change
--MSGenericTestFormat option has been replaced by --ReportOutputFile:MSGenericTest
Features
New "native" xUnit runner. Contributed by Remo Gloor
MSTestProvider: Emit Description, Owner and Properties from a TestMethod into the XML
... [More]
File
Now supports MSTest's TestContext.WriteLine(...) - The output will be written to the metadata 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]
|