Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-945

Clover charts are inaccurate on days that builds did not occur

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 2.0.1
    • 1.0-rc2
    • Telemetry / Reporting
    • None

    • 1.0rc2 standalone / linux / jdk 1.5.0_11

      See attached screenshot.

      On days that a build does not occur, the clover charts show 0% coverage. This creates the false perception that somehow the test coverage actually went to 0% on those days, which is of course not the case.

      Expected behavior: on days where builds do not happen, the test coverage stays constant in the chart.

      Steps to replicate:

      1) Set up a new project and build plan for a codebase that is integrated with Clover. Make sure that the project has greater than 0% coverage. For example sake, we'll say that initial coverage is at 50%.
      2) On day one, build the project. Notice the clover chart shows 50% coverage
      3) On day two, do not build the project. Notice the clover chart drops to 0% coverage (lines of code chart goes to 0 too)
      4) On day three, without making any modifications to the code, manually build the project. Notice that the coverage and lines of code charts jump right back to their previous values.

        1. Picture 1.png
          Picture 1.png
          81 kB
        2. Picture 2.png
          Picture 2.png
          88 kB

            [BAM-945] Clover charts are inaccurate on days that builds did not occur

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 1442811 ] New: JAC Bug Workflow v3 [ 3383958 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Bamboo Workflow 2016 v1 [ 1420348 ] New: Bamboo Workflow 2016 v1 - Restricted [ 1442811 ]
            Marek Went (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2014 v2 [ 618192 ] New: Bamboo Workflow 2016 v1 [ 1420348 ]
            Marek Parfianowicz made changes -
            Link New: This issue is duplicated by BAM-699 [ BAM-699 ]
            James Dumay made changes -
            Workflow Original: Bamboo Workflow 2014 [ 604233 ] New: Bamboo Workflow 2014 v2 [ 618192 ]
            James Dumay made changes -
            Workflow Original: Bamboo Workflow 2010 [ 204060 ] New: Bamboo Workflow 2014 [ 604233 ]
            MarkC made changes -
            Workflow Original: reviewflow [ 165960 ] New: Bamboo Workflow 2010 [ 204060 ]
            MarkC made changes -
            Workflow Original: jira [ 77802 ] New: reviewflow [ 165960 ]
            MarkC made changes -
            Fix Version/s New: 2.0.1 [ 13762 ]
            Assignee New: MarkC [ mark@atlassian.com ]
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            MarkC made changes -
            Assignee Original: edwin [ edwin@atlassian.com ]

              mark@atlassian.com MarkC
              c0fe2c4aa12c Chris Beams
              Affected customers:
              3 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: