Run LightHouse against multiple Xap files


I can see where you are coming from but I am running LightHouse from within my CI build template which always run all tests in my solution. If possible, I would prefer to use wildcard instead of adding one InvokeProcess activity for each of my Xap file and change the build template every time a new Xap is added to my solution...
For now, I try "for each xap -> invoke" in my build template. This should solve my problem.


hsun wrote Jan 18, 2012 at 4:48 AM

I am running LightHouse from within my CI build template (MSBuild InvokeProcess). My Silverlight tests are distributed in multiple XAPs. It would be great if LightHouse could process all my XAPs in one go and generate a result file contains result for all my tests.

For example:
lighthouse.exe -m:Xap *UnitTests.xap TestResult.xml 
This will run Module1.UnitTests.xap Module2.UnitTests.xap.
Also, this is not that important to me but maybe we could do something like: if no test result name is specified then generate one test result file for each assembly that is passed in. The name of the test result file will be assembly name plus .TestResult.xml or just assembly name plus .xml. This will make processing test result by code a lot easier.

Please let me know if you need more info.


hsun wrote Jan 18, 2012 at 4:51 AM

Or we could do something similar to what LightHouse already done for Dlls.
lighthouse.exe -m:Xap -tests:"*UnitTests.xap" TestResult.xml

wrote Feb 13, 2013 at 7:06 PM