Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-10100

Replace build-in test graphs with the TestNG ones

      I don't know if it's possible - probably it requires some core changes, too - but it would be very nice if the build-in test graphs (especially for Maven2 jobs as I cannot disable them there) could be replaced by the TestNG graphs

          [JENKINS-10100] Replace build-in test graphs with the TestNG ones

          nalin_makar added a comment -

          I could not understand. Could you be more specific about what you are requesting and which build-in graphs are you talking about?

          nalin_makar added a comment - I could not understand. Could you be more specific about what you are requesting and which build-in graphs are you talking about?

          kutzi added a comment -

          When using the Maven2 job type, test results are automatically displayed in a graph. See e.g. http://ci.jenkins-ci.org/view/Plugins/job/plugins_jabber/
          When I enable the TestNG plugin for such a job, the TestNG results are displayed in an additional graph below that.

          I would like to replace the build-in graph with the TestNG one as it is superior to it.
          Additional goody would be to also replace the TestResultAction attached to the build with one generated from the TestNG plugin, so other plugins evaluating the test results (e.g. ci-game) would also the TestNG ones.

          kutzi added a comment - When using the Maven2 job type, test results are automatically displayed in a graph. See e.g. http://ci.jenkins-ci.org/view/Plugins/job/plugins_jabber/ When I enable the TestNG plugin for such a job, the TestNG results are displayed in an additional graph below that. I would like to replace the build-in graph with the TestNG one as it is superior to it. Additional goody would be to also replace the TestResultAction attached to the build with one generated from the TestNG plugin, so other plugins evaluating the test results (e.g. ci-game) would also the TestNG ones.

          nalin_makar added a comment -

          Thanks for the updated information. I am not entirely sure that this can be done, but will look into it later.

          Reducing priority.

          nalin_makar added a comment - Thanks for the updated information. I am not entirely sure that this can be done, but will look into it later. Reducing priority.

          Nalin Makar added a comment -

          kutzi,

          way back, via email conversation you mentioned you'll check with olamy and others to see whats the best way of handling this. Did you or others have an idea to point me in the right direction before I start looking into this?

          Junit and TestNG publishers attach separate ProjectActions to the job and currently I don't know if a clean way of replacing Junit's ProjectAction with the one from TestNG for Maven builds.

          Nalin Makar added a comment - kutzi, way back, via email conversation you mentioned you'll check with olamy and others to see whats the best way of handling this. Did you or others have an idea to point me in the right direction before I start looking into this? Junit and TestNG publishers attach separate ProjectActions to the job and currently I don't know if a clean way of replacing Junit's ProjectAction with the one from TestNG for Maven builds.

          kutzi added a comment -

          To be honest, I don't remember if I posted this question to the dev-list at all. And if I did, I think I didn't get any answer.
          The answer would probably be a new @Extension point in Jenkins core.

          kutzi added a comment - To be honest, I don't remember if I posted this question to the dev-list at all. And if I did, I think I didn't get any answer. The answer would probably be a new @Extension point in Jenkins core.

            nullin Nalin Makar
            kutzi kutzi
            Votes:
            7 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: