Displaying Number of Tests Passed

I'm using an Ant build and JUnit for my Unit Tests. It seems like TeamCity does not always pick up my test results to display "Tests passed: x" on the summary.

I had it working for a while, then when I made some (seemingly unrelated) changes to my Ant build file, it went back to just displaying 'Success'

Any rules on what it takes to get the test results to display? Thanks.

Ant Unit Test target:


]]>
<include name="*/unit/Tests.java"/>
]]>

5 comments
Comment actions Permalink

Geoffrey Lane <no_reply@jetbrains.com> writes:

>I'm using an Ant build and JUnit for my Unit Tests. It seems like
>TeamCity does not always pick up my test results to display "Tests
>passed: x" on the summary.
>
>I had it working for a while, then when I made some (seemingly
>unrelated) changes to my Ant build file, it went back to just
>displaying 'Success'

This sounds like the same problem I'm having (see 'Reporting number of
unit tests in history table' topic). At least now I know I'm not
going crazy!


--
-- Steve

0
Comment actions Permalink

Hello

Is it possible to modify build.xml file and to add there sleep for several
seconds right after the <junit/> task (you can use Ant <sleep/> task)? Most
likely this will fix the problem. Of course we wil include fair fix in the
next EAP.

--
Pavel Sher


"Steve Allan" <takezowest@yahoo.com> wrote in message
news:uk657b193.fsf@attachmate.com...

Geoffrey Lane <no_reply@jetbrains.com> writes:

>
>>I'm using an Ant build and JUnit for my Unit Tests. It seems like
>>TeamCity does not always pick up my test results to display "Tests
>>passed: x" on the summary.
>>
>>I had it working for a while, then when I made some (seemingly
>>unrelated) changes to my Ant build file, it went back to just
>>displaying 'Success'
>

This sounds like the same problem I'm having (see 'Reporting number of
unit tests in history table' topic). At least now I know I'm not
going crazy!

>
>

--
-- Steve



0
Comment actions Permalink

Pavel,

]]>

Did not seem to work.

0
Comment actions Permalink

hello pavel

I observe the same behavior with TC 1.2. What is the status on this issue?

etienne

0
Comment actions Permalink

Answering my own question here...

Upgrading to ANT 1.6.5 did solve the problem. Or alternatively, not to set an explicit ANT home path in the build configuration.

etienne

0

Please sign in to leave a comment.