When running with -c flag and multiple XAP files, it only monitors the first XAP file


If you start statlight with two or more xap files and with the continuous -c flag (i.e. statlight -x="Tests1.xap" -x="Tests2.xap" -c), statlight will only monitor the first XAP for changes and will only run the tests in it. The expected behavior is that statlight will monitor all XAPs and run all tests.
Closed Nov 27, 2011 at 9:29 PM by staxmanade
This should be working now.


staxmanade wrote Sep 22, 2011 at 8:13 PM

Reasonable expectation...

I'm also thinking it should run all tests from all xaps? Or maybe only the xaps that changed, since the build process will only rewrite xaps that have changes. Thoughts?

nseba wrote Sep 23, 2011 at 6:34 AM

I think it will be enough if it runs only the tests in the xaps that have changed. The other ones will have the same outcome anyway, so it's a bit faster this way.

ChadForGood wrote Nov 4, 2011 at 12:56 PM

I'm of two minds on whether it should run all the xap files or just the changed ones.

It is a waste of time (longer time to wait for results) to re-run tests that will have the same outcome as the previous run. And, it's easy enough for me to force all tests to run by doing a full/clean solution build.

But, test result reporting would be an issue if it runs the tests of a xap as soon as it notices a file change since it might process each xap file in sequence -- scrolling the results of a previous test off the screen before the user has a reasonable change to see it -- a behavior I consider undesirable outside of the continuous feature. I can't think of a good way to resolve this issue in a command line tool. The real solution would be a GUI -- such as a continuous integration tool.

wrote Nov 4, 2011 at 12:58 PM

wrote Nov 27, 2011 at 9:29 PM

wrote Feb 14, 2013 at 8:17 PM

wrote May 16, 2013 at 9:49 AM