-b and -- teamcity dont work together


i've created a test project (attached) with 5 tests, 2 that need the browser and 3 that dont.
i have run the following from the command line with the results
StatLight.exe -x=UnitTestApplication\Bin\Debug\UnitTestApplication.xap -b
Test run results: Total 5, Successful 5, Failed 0,
StatLight.exe -x=UnitTestApplication\Bin\Debug\UnitTestApplication.xap
Test run results: Total 5, Successful 3, Failed 2,
StatLight.exe -x=UnitTestApplication\Bin\Debug\UnitTestApplication.xap --teamcity
Test run results: Total 5, Successful 3, Failed 2,
StatLight.exe -x=UnitTestApplication\Bin\Debug\UnitTestApplication.xap --teamcity -b
Test run results: Total 0, Successful 0, Failed 0,
Any ideas???
i get the same results in teamcity
the above is all command line calls and not via teamcity.
But when I do it from teamcity I get the same results

file attachments

Closed Jul 2, 2011 at 2:48 AM by staxmanade
Fixed in https://github.com/staxmanade/StatLight/commit/750e16d9ee310598de06fb9fbc02e03d957de661


staxmanade wrote Jun 8, 2011 at 1:33 PM

This looks like what happenes when you don't have the teamcity build agent on the server running with desktop interactivity? http://statlight.codeplex.com/documentation

amjidq wrote Jun 8, 2011 at 8:46 PM

I have setup the desktop interactivity and it seems to work, if I run it with the following

StatLight.exe -x="UnitTestApplication\Bin\Debug\UnitTestApplication.xap" -b -r="C:\temp\report.xml"
it comes back with 5 passes, in the xml

I had to jump through some hoops to get that working

amjidq wrote Jun 8, 2011 at 8:53 PM

the desktop intereactivity that is

staxmanade wrote Jun 9, 2011 at 2:24 PM

Have you tried it with the desktop interactivity correctly setup the --teamcity flag? or is the combination still causing an issue?

amjidq wrote Jun 10, 2011 at 3:28 AM

Yeh I've tried it with desktop interactivity setup correctly. and it still has the issue.
The way I am checking desktop interactivity has worked in is that I run it with -b -r=XXX (without --teamcity) through teamcity and the file genereated is correct (5 passes).

As soon as I put --teamcitry with it fails and comes back with zero tests

if you use -b or --teamcity on their own you get the expected results. But as soon as you use both together you get zero tests.

amjidq wrote Jun 10, 2011 at 3:40 AM

just had another look at it and it doesn't pick up the unit tests. In Teamcity mode (--teamcity, no -b) it pushes out

teamcity[testSuiteStarted name='XXXX]




so a start of suite
then start and finish for each test

and finishes up with finishSuite

when you use --teamcit and -b
you get

teamcity[testSuiteStarted name='XXXX]


a start and finish for the suite but no unit tests in there. The tests are just not being picked up at all with both params

Chris4Man wrote Jun 29, 2011 at 9:25 AM

I'm getting this problem too - http://statlight.codeplex.com/discussions/262473.

I don't think it's anything to do with TeamCity as I can run with the "--teamcity" flag locally (where I don't have TeamCity installed) and the test run and pass/fail as expected with the output being in the correct format.

staxmanade wrote Jun 30, 2011 at 11:41 PM

I'm reproducing this error on my side (works with v1.3 but v1.4 does not work as expected... Just need to figure out what change broke this now. (git-bisect here we come)

staxmanade wrote Jul 1, 2011 at 11:26 PM

This one's been a bugger to try to figure out. The commit here is the first time this is broken https://github.com/staxmanade/StatLight/commit/7ac70b6baa84f2e3fe36c5ab058dc0c427dfeca8

What I can't seem to figure out is what is breaking it... Even if I comment out the changes that look like they do anything it still fails. hmmmm

staxmanade wrote Jul 2, 2011 at 2:27 AM

This was a bugger of a bug to hunt down and squish... But fixed now in https://github.com/staxmanade/StatLight/commit/750e16d9ee310598de06fb9fbc02e03d957de661. You can pull the latest build from teamcity.