JUnit RTC viewer versus Eclipse

I am using JBE to run my Ant build script. The script launches a series of JUnit tests (using Ant's junit task) and my build definition includes the location of the result logs on the "JUnit Publishing" tab. In my current scenario one of the tests fails. After the build is completed, the build results report generated by RTC and viewed in the Eclipse client shows only the failed test.

When I run the same test suite directly from Eclipse, the JUnit viewer there shows all test including the failed one.

My question is: is that intended behaviour or is it a bug?

Hi,

I was wondering if you are able to look at the directory of the result logs after the build completes. Does it include all of the logs files - both passing and failing logs?

Best regards,

Brent Ulbricht
Developer/Lead - RTC Build

After the build is completed, the build results report generated by RTC and viewed in the Eclipse client shows only the failed test.

This might be the problem...

When you open up a build result in Eclipse in which there are test failures, when you go to the "Tests" tab, it is true that you only see the test failures. It is not really obvious, but at the top right there is a little icon (with a green check mark). If you toggle this button, it will then show you all the successful tests as well.

The idea here is that generally only the failures are important, and so hiding the passed tests by default allows one to quickly see what went wrong.

Although, the opposite is true when a build has no test failures. When you go to the "Tests" tab, all the tests show by default (which happen to be all the passed tests).

This might be the problem...

When you open up a build result in Eclipse in which there are test failures, when you go to the "Tests" tab, it is true that you only see the test failures. It is not really obvious, but at the top right there is a little icon (with a green check mark). If you toggle this button, it will then show you all the successful tests as well.

The idea here is that generally only the failures are important, and so hiding the passed tests by default allows one to quickly see what went wrong.

Although, the opposite is true when a build has no test failures. When you go to the "Tests" tab, all the tests show by default (which happen to be all the passed tests).

Thank you both for the prompt reply.

David's suggestion was correct: that button is not depressed by default and in that state only the failed tests are shown. I think that is the source of my problem. The Eclipse JUnit viewer has a similar button but its default state is the opposite. Also, it is easy to see that it actually is a button. The RTC equivalent looks like a static icon and only when you happen to hover over it that it shows its outline and the tip.

Still. that certainly solves my problem.

Thank you and my regards,

Chris Novak

I am using the Jazz build engine to run a suite of Web services tests with soapUI (a popular Web services testing tool). soapUI can generate its test results in the JUnit XML format.

After tweaking the soapUI JUnit report a bit with an XSLT, I get the results displayed on the JUnit tab of the Jazz build report. It all looks quite nice and as I click on the individual tests in the upper pane, the lower Details pane shows 2 hyperlinks: one labeled "Class name" and the other "Method".

The JUnit tab and the links have clearly been designed to work with Java code where the class is the actual JUnit TestCase class and the method is the test class' method. Clicking on either, triggers a search through the Eclipse workspace and then the actual code is displayed in the Java editor.

My question is: is there any way to change that behaviour so that the links can point to something else in my workspace (or RTC repository)?

Regards,

Chris Novak

My question is: is there any way to change that behaviour so that the links can point to something else in my workspace (or RTC repository)?

Regards,

Chris Novak

Hi Chris,

Unfortunately there is no way at the moment to change the behavior when you click on tests in the build result. That issue is currently tracked in the following work item:
138973: Navigation to source from test results is Java-specific.
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/138973
If you want you can go there and add comments for any specifics you would like to see. Doing so also puts the work item more on the radar :)

Also, I was wondering about your soapUI XSLT you wrote. If it contains no sensitive information and you wouldn't mind, would you be able to provide it to us?(either by posting here or through email). I was thinking that it might be good to put this on the Build Wiki site for others to take advantage of.