Could you please update the bug with the build logs? Also, look for testng logs on the webserver or console where jenkins is running.

Also,

I just tested this out locally but could not reproduce it. It'll help to see screenshots of the graphs or test results with v0.26 vs 0.31.

Basically all the information you can provide and/or any steps to repro.

Thanks!

Okay, here are two pics of the case where it does not show the results:
http://img191.imageshack.us/img191/8543/pic1ap.png
http://img163.imageshack.us/img163/7302/pic2yb.png

Here are two pics where it shows the results:
http://img705.imageshack.us/img705/3614/pic3g.png
http://img195.imageshack.us/img195/9258/pic4ns.png

See how it says "Not looking for any testNG results" at the bottom of the console where it fails? I don't get it why. There is no option in preferences or something it just fails to show the reports.

I installed 0.31 this morning and I don't see this issue either. Peter Lustig, I have seen the message "Not looking for any testNG results" when the previous build step failed (in my case, a shell script step returned nonzero). So the build fails at that step and it makes sense for testNG plugin to not bother looking for results. Maybe that is what you are seeing. I don't know what your config looks like, but you may want to verify that all the build steps complete without error.

I figured the same, but I am not sure now that it's the right behavior.

Sometimes testng ant ask itself can be configured to to fail the build if tests fail, but that should not stop us from reporting the tests that were executed. I made a similar change for aborted builds recently based on bug that kutzi filed and now am wondering if I should revert that behavior as well or not.

nalin, I would think that testng plugin should fail a job that would have otherwise passed, if there is no result file (which it does). And it should mark a job as unstable that otherwise would be success, if the result file is there and contains failed tests (which it also does). But seems like it should always look - even when the job is failed or aborted, the user might want to see the test results, if there are any.

Jeff, I agree that the plugin should look for results when a build failed.
But not when it was aborted, because - IMHO - cancelling/aborting a build means: 'stop as fast as possible'

kutzi,

When user aborts a bit, the current executing step should stop asap, but because testng plugin only reports results and doesnt really execute any build steps or modify the workspace, it might be beneficial to run it. Simple use case would be where there are multiple calls to running tests and even though we want to abort the build, we want to make sure that results that were already published are parsed and displayed.