1

Closed

Test mutliple xap-files at once

description

The current implementation is just testing one .xap file and produces then exactly one .xml result.
Using the commandline tool on any server to collect the results, would make it easier to provide a complete directory or a list of .xap files which have to be tested and combine all results in one .xml file.
 
-folder option would make it easier to include newly created testprojects without extra configuration.
-multiple xap option defines specific set of .xap's to be tested
-one test result xml option would make it easier to get the results automated at once, without parsing a bunch of result files.
 
Positiv side-effect: The Unit Test Result Viewer for Silverlight in Visual Studio would run a little bit faster as parsing multiple results is not necessary anymore and the UAC-popup would appear only once instead on n-times.
Closed Sep 25, 2010 at 5:33 AM by staxmanade
Since I haven't heard any feedback on the implementation and it's done (and working) I've merged the branch into master and I'm closing the issue.

comments

staxmanade wrote Sep 2, 2010 at 5:10 AM

I have some work done to enable this feature. You can check it out at the following github branch http://github.com/staxmanade/statlight/tree/multiXap
Please download and play with it – let me know how it looks…
With this, you can specify multiple xaps by calling "StatLight.exe -x=File1.xap -x=File2.xap"

It will also place all of the results into a single xml result file. The xml schema has changed to support this, but I think it's good for now.

Please take a look and let me know how this works for you...

Also to note - I'm not going to support a directory option. That adds too many error cases that I'd need to look at handling. My current preference is being explicit on the command line.

Also to note (2) - the implementation under the hood is very synchronous (meaning we're not spinning multiple browsers up, 1 for each xap) as there is more work to do to accomplish this. From a consumer of StatLight point of view I think it's pretty much ready to go. There will be opportunity for performance increase with this version.

wrote Sep 25, 2010 at 5:33 AM

wrote Feb 14, 2013 at 8:18 PM

wrote May 16, 2013 at 9:50 AM