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

Build Failure Analyzer: output of tests not escaped on build results page

      We had the 'Treat failed test cases' checkbox enabled and so test outputs are written on the build page.
      In one of those case the test output contained HTML source - which wasn't escaped and so used as part of the page DOM.
      As this was an overly blocking the whole page, this was kind of annoying.

      I've now updated to 1.17.0, but still not better for the existing builds.

          [JENKINS-37891] Build Failure Analyzer: output of tests not escaped on build results page

          kutzi added a comment -

          That was part of the test output

          org.openqa.selenium.WebDriverException: Element is not clickable at point (161.9499969482422, 437.41668701171875). Other element would receive the click: <div style="position: fixed; top: 0px; left: 0px; bottom: 0px; right: 0px; background-color: rgba(85, 85, 85, 0.8); z-index: 999999999; overflow-x: auto; overflow-y: scroll; visibility: visible; margin-left: 0px; display: block;" class="usabilla__overlay"></div>
          

          kutzi added a comment - That was part of the test output org.openqa.selenium.WebDriverException: Element is not clickable at point (161.9499969482422, 437.41668701171875). Other element would receive the click: <div style="position: fixed; top: 0px; left: 0px; bottom: 0px; right: 0px; background-color: rgba(85, 85, 85, 0.8); z-index: 999999999; overflow-x: auto; overflow-y: scroll; visibility: visible; margin-left: 0px; display: block;" class="usabilla__overlay"></div>

            t_westling Tomas Westling
            kutzi kutzi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: