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

Identify where java unit test coverage is poor

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Critical Critical
    • blueocean-plugin
    • None
    • Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2, Blue Ocean 1.1-beta4

          [JENKINS-43671] Identify where java unit test coverage is poor

          James Dumay created issue -
          James Dumay made changes -
          Epic Link New: JENKINS-36178 [ 172150 ]
          James Dumay made changes -
          Link New: This issue relates to JENKINS-43083 [ JENKINS-43083 ]
          James Dumay made changes -
          Description New: Requirements https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit
          James Dumay made changes -
          Summary Original: Identify where unit test coverage is poor New: Identify where java unit test coverage is poor
          James Dumay made changes -
          Priority Original: Minor [ 4 ] New: Critical [ 2 ]
          James Dumay made changes -
          Assignee Original: Ivan Meredith [ imeredith ] New: Vivek Pandey [ vivek ]

          James Dumay added a comment - - edited

          vivek I would like you to go through all our java modules and identify where we could improve test coverage. We should have tickets in your queue for improving that coverage so that we do not rely on the ATH to pick up problems. For example, creation backend has almost no tests and I would expect the coverage for that to be rather high.

          I expect that we want to set a minimum coverage (90%?) for each of our modules and have the build fail if we go below that amount.

          imeredith is working from this document to improve the ATH situation for logged in scenarios such as creation, editing and personalization.

          James Dumay added a comment - - edited vivek I would like you to go through all our java modules and identify where we could improve test coverage. We should have tickets in your queue for improving that coverage so that we do not rely on the ATH to pick up problems. For example, creation backend has almost no tests and I would expect the coverage for that to be rather high. I expect that we want to set a minimum coverage (90%?) for each of our modules and have the build fail if we go below that amount. imeredith is working from this document to improve the ATH situation for logged in scenarios such as creation, editing and personalization.
          James Dumay made changes -
          Link New: This issue relates to JENKINS-43740 [ JENKINS-43740 ]
          Michael Neale made changes -
          Sprint Original: Blue Ocean - 1.1-beta-1 [ 291 ] New: Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2 [ 291, 306 ]

            vivek Vivek Pandey
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: