• Type: Bug
• Resolution: Duplicate
• Priority: Major
• Component/s: core
• Labels:

  None
• Environment:

  Platform: PC, OS: All

1. com.avaloq.adt.ui.team.tests.BuildTests.xml

   41 kB

   2008-09-03 01:20

2. 

   junit-details.png

   17 kB

   2008-09-03 01:15

3. 

   junit-overview.png

   8 kB

   2008-09-03 01:16

[JENKINS-2310] JUnit Details view is broken if results contains duplicate test names

Collapse comment: Ulli Hafner added a comment - 2008-09-03 01:15

Ulli Hafner added a comment - 2008-09-03 01:15

Created an attachment (id=365)
Details of the failed test (failure)

Expand comment: Ulli Hafner added a comment - 2008-09-03 01:15

Ulli Hafner added a comment - 2008-09-03 01:15 Created an attachment (id=365) Details of the failed test (failure)

Collapse comment: Ulli Hafner added a comment - 2008-09-03 01:16

Ulli Hafner added a comment - 2008-09-03 01:16

Created an attachment (id=366)
Overview

Expand comment: Ulli Hafner added a comment - 2008-09-03 01:16

Ulli Hafner added a comment - 2008-09-03 01:16 Created an attachment (id=366) Overview

Collapse comment: Ulli Hafner added a comment - 2008-09-03 01:20

Ulli Hafner added a comment - 2008-09-03 01:20

Created an attachment (id=367)
Surefire Results File

Expand comment: Ulli Hafner added a comment - 2008-09-03 01:20

Ulli Hafner added a comment - 2008-09-03 01:20 Created an attachment (id=367) Surefire Results File

Collapse comment: Ulli Hafner added a comment - 2008-09-09 09:45

Ulli Hafner added a comment - 2008-09-09 09:45

I investigated this bug in more details: seems that Hudson references Unit tests
by the class name. If you have several tests with the same name (but in a
different module), then Hudson correctly shows the failures but when clicking
the details sometimes the wrong "ok" result is picked.

We have 20 maven modules each of them has the same Unit test to scan for package
cycles:

<testcase classname="com.avaloq.util.BuildCycleTestCase" name="testForCycles"
time="0.485">
<failure message="Cycles exist [...]

As a workaround, I'll try to change the name of the tests programatically. So if
you like to close this issue that is ok for me (there might be some problems for
other users, though...)

Expand comment: Ulli Hafner added a comment - 2008-09-09 09:45

Ulli Hafner added a comment - 2008-09-09 09:45 I investigated this bug in more details: seems that Hudson references Unit tests by the class name. If you have several tests with the same name (but in a different module), then Hudson correctly shows the failures but when clicking the details sometimes the wrong "ok" result is picked. We have 20 maven modules each of them has the same Unit test to scan for package cycles: <testcase classname="com.avaloq.util.BuildCycleTestCase" name="testForCycles" time="0.485"> <failure message="Cycles exist [...] As a workaround, I'll try to change the name of the tests programatically. So if you like to close this issue that is ok for me (there might be some problems for other users, though...)

Collapse comment: Ulli Hafner added a comment - 2009-01-21 23:03

Ulli Hafner added a comment - 2009-01-21 23:03

Duplicate

• • • This issue has been marked as a duplicate of 2184 ***

Expand comment: Ulli Hafner added a comment - 2009-01-21 23:03

Ulli Hafner added a comment - 2009-01-21 23:03 Duplicate This issue has been marked as a duplicate of 2184 ***