Jenkins not showing Test Result Trend graph for some projects

Question

Im using Jenkins to run UI Testing suites for various xcode projects. Most of the projects shows the 'Test Result Trend' graph with no problem.

However, one of my projects fails to show the graph.

I have run the build a few times found but cannot find any obvious differences between those projects that display the graph and those that dont:

1. Their configs are setup the same (except for git repo location)
2. Their console outputs seems to display the same (no mention of errors around populating the graph)
3. The test-reports/*.xml files all appear in the same valid format

Really at a loss on this one and so thought I would post to see if anyone else has resolved an issue like this before?

Updated more details:

• Its a Freestyle project
• Using the xcode plugin
• Using Junit test result plugin set as 'test-reports/*.xml'
• When I select Test Results Analyzer the full test results display (i.e. its only the Test Result Trend graph that is failing to appear at all). The graph isn't empty it is simply not shown at all. Also, 'Latest Test Results' link is also missing.

Solution 1

Test Result Trends does not show up on Job page unless you have at least one successful (100% passed) test run. If you have all test runs as failure till date, it will not show.

Solution 2

Little bit late to the party...

"Test Result Trend" will be shown if you have at least one failed and at least one successful test.

That was the case with NUnit plugin in my Jenkins configuration.

Comments

[ben]

What do you mean by successful test run? Does it mean 100% pass rate or just that the jenkins build was successful?

[ben]

I think you meant 100% pass rate. I tried that and it worked for me. Thank you!

[Manik Jadhav]

Yes, I meant 100% Success

[Ora]

This answers the question perfectly

[Charles Anderson]

I had the same problem with the results not showing. However, I didn't need to get all the tests to pass—I just needed one test run to claim to have passed.

[Cinderhaze]

I just ran into this exact scenario - I wonder if anyone has opened a bug/issue against the plugin? I also do not see the 'cucumber reports' option on the left unless there was at least one success within the job (different cucumber-reports plugin, same issue)

[Pavol Travnik]

Thank you @ManikJadhav it seems to be a problem even today. At least one complete test run must be successful on 100%.

[trebor]

Why do I need to have a failed test in order for the test result trend to show?

[neoscribe]

I ran into this when mstest and nunit were both being used but one of them had zero tests yet. I simply removed nunit test run from the build. Everything was groovy then.