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

No new tests found should be treated as empty results


      Modern build tools like gradle (https://gradle.org/) are smart enough to only rebuild the parts of the project which have been modified.

      When building these projects and only a readme or other none code affecting part has been changed, the build fails with a

      ERROR: Test reports were found but none of them are new. Did tests run?

      even though the build was OK!

      There is a flag allowEmptyResults which overrides when no tests are found. Not finding any new tests should also be categorized as no tests found, but as of today there is no way of overriding this!

      This PR changes the behaviour of  the allowEmptyResults flag, so that old tests are treated as no found tests, thus allowing to use the flag to to avoid the error...

      PR: https://github.com/jenkinsci/junit-plugin/pull/81 


            Unassigned Unassigned
            bjorn_frantzen Bjorn Frantzen
            3 Vote for this issue
            7 Start watching this issue