JUnit test results with a null classname are not correctly handled

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 6.0.0
    • Affects Version/s: 5.14.4.1, 5.15.5
    • Component/s: Tests
    • None
    • Severity 3 - Minor

      Summary

      Bamboo test results show unexpected results when testcase classpath is null

      Steps to Reproduce

      1. Create a build that parses the following test file
        <testsuite errors="0" failures="0" name="name" skips="0" tests="2" time="0.2">
          <testcase classname="classname" file="file" line="1" name="test_class" time="0.1"/>
          <testcase classname="" file="test" line="1" name="test_class" time="0.1"/>
        </testsuite>
        
      2. Run the build and check the results

      Expected Results

      Bamboo will show the two tests as expected in <Bamboo_URL>/browse/PLAN-KEY-XXX/test and <Bamboo_URL>/browse/PLAN-KEY-XXX/test/case/0 .

      Actual Results

      The page <Bamboo_URL>/browse/PLAN-KEY-XXX/test will not show the correct total number for tests:

      The page <Bamboo_URL>/browse/PLAN-KEY-XXX/test/case/0 will show an unespected error:

            Assignee:
            Unassigned
            Reporter:
            Daniel Santos (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: