Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Silverlight Testing Automation Tool
C# PowerShell Puppet Other
Branch: master
Failed to load latest commit information.
docs Updated docs for extensibility
lib really nasty merge - LOTS OF BROKEN THINGS (Save point)
src Typo fix.
.gitignore Added a first pass at the StatLight documentation for CHM generation …
StatLight.EULA.txt Initial Checkin (hope I have it all)
build-Debug.bat added -NoProfile to the bat calls into powershell
build-Full-Release-Phone.bat Updating build scripts to support a phone/nophone build of StatLight
build-Full-Release-skip-tests.bat Added new build bat file that will create a release build of the sour…
build-Full-Release.bat added -NoProfile to the bat calls into powershell
default.ps1 removing some sl3
integrationTestRunHelper.ps1 really nasty merge - LOTS OF BROKEN THINGS (Save point)
psake.psm1 hack psake
sampleMSTestRunReport.xml Fixed up new messaging and integration tests to support nested test c…


What Is StatLight?

StatLight is a tool developed for automating the setup, execution, and gathering results of Silverlight unit tests. StatLight helps to speed up the feedback cycles while practicing TDD/BDD/(insert your test style here) during Silverlight development.

Project Resource Links and Information

Where do I get the most current release?

How to build?

StatLight build infrastructure is put together with a number of psake tasks.

  1. Make sure the location you extract the project is not too far from your drives root as it runs into some msbuild max file path issues.
  2. Execute the build of choice. Release build ----- You can either execute - build-Full-Release.bat (compile the solution, runs test suite, creates package release) or - build-Full-Release-skip-tests.bat (compile the solution, creates package release) then - you should find the build artifacts in the .\Release folder. Debug build ----- execute the build-Debug.bat file and you can check out the artifacts placed in .\src\build...

Build NOTE: The unit/integration tests throw up quite a few assertion dialogs, and message boxes (Don't close them yourself, unless it hangs for more than 15 seconds). They should close automatically during the build.


Thanks for contributions from:

Something went wrong with that request. Please try again.