teamcity 6.0.1 fails to detect suite for junit tests

We are using TeamCity 6.0.1 with Ant & Junit 3.6.  Looking at some recent test runs, I noticed that I cannot find my tests because it seems that the suite information is missing.

If I look at one of the junit result file, I see:

uxpssoldev1(bsmith): cat TEST-prtest.CR77225.xml
<?xml version="1.0" encoding="UTF-8" ?>
<testsuite name="prtest.CR77225" tests="2" failures="0" errors="0" time="0.094">
    <testcase classname="com.progress.dataxtend.si.designer.ui.headless.HeadlessTestCase" name="testEnabled" time="0.078">
    </testcase>
    <testcase classname="com.progress.dataxtend.si.designer.ui.headless.HeadlessTestCase" name="testDisabled" time="0.016">
    </testcase>
</testsuite>


The suite should be prtest.CR77225.  Yet, TeamCity doesn't seem to pick it up.  It classified all of our junit tests as having "no suite".

13 comments
Comment actions Permalink

Hello, Bill,

Could you please attach build log for such a build and some UI screen shots on how TeamCity shows your tests with "no suite"?

0
Comment actions Permalink

Hi Victory,

I've attached a screen shot showing "no suite" and the build log.

--Bill



Attachment(s):
DXSI_8.5_submit-eclipse3.6-JDK1.5.0_22_229.log.zip
TeamCity_no_suite.jpg
0
Comment actions Permalink

Bill,

Thanks a lot for your attachments.
One more thing I need.
Could you please check "Verbose" checkbox on Xml Report Processing settings pane, rerun your build and attach build log once more. Thank you!

0
Comment actions Permalink

I attached a new build logfile after enabling verbose.



Attachment(s):
DXSI_8.5_submit-eclipse3.6-JDK1.5.0_22_233.log.zip
0
Comment actions Permalink

Bill,

I suppose that "com.progress.dataxtend.si.eclipse.designer.ui.test.xml" causes the problem as it contains full list of tests that are already present in TEST-*.xml reports.

Please try specifying "Report paths" as following:

d:\views\dx_8.5.0_int\vobs_dx_qa\si\target\docs\junit\data\dbsetup\TEST-*.xml
d:\views\dx_8.5.0_int\vobs_dx_qa\si\target\docs\junit\data\eclipse\TEST-*.xml

0
Comment actions Permalink

Ok, I made the change you suggested but I still see the same issue. I've attached a screen shot again.
As you can see, out of 9064 tests that have run, just about all of them have "no suite".



Attachment(s):
no_suite.jpg
0
Comment actions Permalink

Could you, please attach the build log and TEST-*.xml reports or send them to teamcity-feedback@jetbrains.com

0
Comment actions Permalink

I attached the build log again to this post. I'll do a second post with the junit files.



Attachment(s):
DXSI_8.5_submit-eclipse3.6-JDK1.5.0_22_238.log.zip
0
Comment actions Permalink

Here are the junit files.  Keep in mind that we only specify

data/dbsetup/TEST*.xml
data/eclipse/TEST*.xml

in the xml report processing because TeamCity automatically detect and handles the other ones.



Attachment(s):
submit-junit.zip
0
Comment actions Permalink

Bumping this thread to see if you had any insight on this issue.

0
Comment actions Permalink

Hello, Bill,

Sorry for the delay in response.
Actually test suites in most of your xml reports hold test case class information.
So for navigating between them you can use View: classes on Tests tab in build results.

I've also introduced a fix in xml-report-plugin so that after installing new plugin you will be able to navigate between suites (which are actually test cases in you case).
To install the plugin put xml-report-plugin.zip under .BuildServer/plugins and restart TeamCity server.



Attachment(s):
xml-report-plugin.zip
0
Comment actions Permalink

Does the patch only affect new build/test runs that were started after the patch was installed? Or will I see a difference with the existing build/test runs?

I installed the patch, restarted TC but I don't see any difference in behavior.  Hence my question if it applies only to new build/test runs.

0
Comment actions Permalink

The patch will affect only new test runs.

0

Please sign in to leave a comment.