Silverlight Testing Automation Tool
C# PowerShell Puppet Other
Latest commit 2b4acad Apr 28, 2014 @staxmanade Merge pull request #17 from kyberias/patch-1
Typo fix.
Permalink
Failed to load latest commit information.
artifacts added the StatLight logo artifacts Apr 22, 2011
docs Updated docs for extensibility Dec 30, 2011
lib
src Typo fix. Apr 28, 2014
tools moved some file around May 14, 2011
.gitignore Added a first pass at the StatLight documentation for CHM generation … Dec 29, 2011
README.markdown added kkozmic to the contributors Aug 17, 2012
StatLight.EULA.txt Initial Checkin (hope I have it all) Dec 2, 2009
StatLight.nuspec fix to nuspec May 14, 2011
build-Debug.bat added -NoProfile to the bat calls into powershell Apr 21, 2010
build-Full-Release-Phone.bat
build-Full-Release-skip-tests-Phone.bat Updating build scripts to support a phone/nophone build of StatLight Dec 27, 2011
build-Full-Release-skip-tests.bat Added new build bat file that will create a release build of the sour… Jul 2, 2010
build-Full-Release.bat added -NoProfile to the bat calls into powershell Apr 21, 2010
default.ps1 removing some sl3 Feb 2, 2014
integrationTestRunHelper.ps1 really nasty merge - LOTS OF BROKEN THINGS (Save point) Dec 22, 2011
psake.psm1 hack psake Feb 2, 2014
sampleMSTestRunReport.xml Fixed up new messaging and integration tests to support nested test c… Feb 27, 2010

README.markdown

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?

http://statlight.codeplex.com

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.

Contributors

Thanks for contributions from: