It would be great to have a sparkline/trendline to quickly view the unit test success trend on the jobs. It could be an extra option in the "Test Result" column config dropdown, looking a bit like the test results graph, but simpler.

          [JENKINS-21630] Add Column : Test sparkline

          Fred G added a comment - - edited

          I had a look around for a lightweight JavaScript framework that shows such a sparkline. Sparklines.js seems to go in the right direction, for example.
          Nevertheless I think this will have a major impact on the performance of displaying the job list, especially if you have a few dozen or even hundreds of jobs on a page.
          One alternative could be to generate such sparklines as graphics, but this would involve server-side graphic generation which is also not trivial.
          So the question is, what information does a sparkline give you compared to simple icons (like the weather symbols) that show the current trend of success?

          Fred G added a comment - - edited I had a look around for a lightweight JavaScript framework that shows such a sparkline. Sparklines.js seems to go in the right direction, for example. Nevertheless I think this will have a major impact on the performance of displaying the job list, especially if you have a few dozen or even hundreds of jobs on a page. One alternative could be to generate such sparklines as graphics, but this would involve server-side graphic generation which is also not trivial. So the question is, what information does a sparkline give you compared to simple icons (like the weather symbols) that show the current trend of success?

          Bruno Perel added a comment -

          Hi,

          I am not so sure about the performance concern. This benchmark shows that several thousands of sparklines can be generated per second, so it seems that even with low-grade clients displaying hundreds of jobs the page rendering shouldn't suffer too much from it. I do agree that a server-side graphic generation doesn't seem a good idea.

          Concerning the utility of such a column content, I would find it useful to view quickly (and without having to go in the job details view) :

          • If the last build has failed, how many failed tests are responsible of that (sure, you can know this number concerning the last builds with the "Test results", but what about the previous ones ?)
          • The failed tests trendline. Believe it or not, a lot of the projects I have seen on Jenkins were always "red" because there was this one test that failed all the time and whose resolution was constantly postponed. But then when another test came to fail also, we didn't see the difference. With a sparkline we could have known instantly that the job was failing, let's say, more than expected, and have a look at the list of failed tests.

          Bruno Perel added a comment - Hi, I am not so sure about the performance concern. This benchmark shows that several thousands of sparklines can be generated per second, so it seems that even with low-grade clients displaying hundreds of jobs the page rendering shouldn't suffer too much from it. I do agree that a server-side graphic generation doesn't seem a good idea. Concerning the utility of such a column content, I would find it useful to view quickly (and without having to go in the job details view) : If the last build has failed, how many failed tests are responsible of that (sure, you can know this number concerning the last builds with the "Test results", but what about the previous ones ?) The failed tests trendline. Believe it or not, a lot of the projects I have seen on Jenkins were always "red" because there was this one test that failed all the time and whose resolution was constantly postponed. But then when another test came to fail also, we didn't see the difference. With a sparkline we could have known instantly that the job was failing, let's say, more than expected, and have a look at the list of failed tests.

          Fred G added a comment -

          Unfortunately I won't have time to work on this in the foreseeable future, but I'll happily accept patches/contributions/pull requests for this issue.
          Please re-open if necessary.

          Fred G added a comment - Unfortunately I won't have time to work on this in the foreseeable future, but I'll happily accept patches/contributions/pull requests for this issue. Please re-open if necessary.

            nonox Bruno Perel
            nonox Bruno Perel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: