Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Annotate integ tests failing with instant execution in various projects

removing most of @IgnoreWithInstantExecution annotations

after fixing the @FailsWithInstantExecution rule

and more ci feedback

also make @IgnoreWithInstantExecution require a reason from a fixed set

and add it to the remaining ignores

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -2
    • +1
    ./testing/TestingIntegrationTest.groovy
    • -7
    • +0
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
    • -11
    • +11
    ./testing/fixture/AbstractTestFilteringIntegrationTest.groovy
    • -10
    • +10
    ./testing/testng/TestNGFailFastIntegrationTest.groovy
  1. … 123 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -4
    • +0
    ./jvm/test/JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 35 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -4
    • +0
    ./jvm/test/JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 37 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -4
    • +0
    ./jvm/test/JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 36 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -4
    • +0
    ./jvm/test/JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 36 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -4
    • +0
    ./jvm/test/JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 36 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after second round of CI feedback

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +4
    ./jvm/test/JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 31 more files in changeset.
Fix TestNGStaticLoggingIntegrationTest

IntelliJ automatically removed an *used* import

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +1
    ./testing/testng/TestNGStaticLoggingIntegrationTest.groovy
Annotate integ tests failing with instant execution in :testingJvm

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +9
    ./jvm/test/JUnitComponentUnderTestIntegrationTest.groovy
    • -0
    • +6
    ./jvm/test/JUnitIncrementalTestExecutionTest.groovy
    • -0
    • +13
    ./jvm/test/JUnitStandaloneTestExecutionIntegrationTest.groovy
    • -0
    • +3
    ./testing/IncrementalTestIntegrationTest.groovy
    • -0
    • +2
    ./testing/TestOutputListenerIntegrationTest.groovy
    • -0
    • +7
    ./testing/TestReportIntegrationTest.groovy
    • -0
    • +2
    ./testing/TestTaskIntegrationTest.groovy
    • -0
    • +2
    ./testing/TestTaskJvmArgsProviderIntegrationTest.groovy
    • -0
    • +4
    ./testing/TestingIntegrationTest.groovy
    • -0
    • +7
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
    • -0
    • +12
    ./testing/fixture/AbstractTestFilteringIntegrationTest.groovy
    • -0
    • +2
    ./testing/junit/JUnitCategoriesIntegrationSpec.groovy
    • -0
    • +2
    ./testing/junit/RerunPreviousFailedTestIntegrationTest.groovy
    • -0
    • +3
    ./testing/testng/SampleTestNGIntegrationTest.groovy
  1. … 20 more files in changeset.
Annotate integ tests failing with instant execution in :testingJvm

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +9
    ./jvm/test/JUnitComponentUnderTestIntegrationTest.groovy
    • -0
    • +6
    ./jvm/test/JUnitIncrementalTestExecutionTest.groovy
    • -0
    • +13
    ./jvm/test/JUnitStandaloneTestExecutionIntegrationTest.groovy
    • -0
    • +3
    ./testing/IncrementalTestIntegrationTest.groovy
    • -0
    • +2
    ./testing/TestOutputListenerIntegrationTest.groovy
    • -0
    • +7
    ./testing/TestReportIntegrationTest.groovy
    • -0
    • +2
    ./testing/TestTaskIntegrationTest.groovy
    • -0
    • +2
    ./testing/TestTaskJvmArgsProviderIntegrationTest.groovy
    • -0
    • +4
    ./testing/TestingIntegrationTest.groovy
    • -0
    • +7
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
    • -0
    • +12
    ./testing/fixture/AbstractTestFilteringIntegrationTest.groovy
    • -0
    • +2
    ./testing/junit/JUnitCategoriesIntegrationSpec.groovy
    • -0
    • +2
    ./testing/junit/RerunPreviousFailedTestIntegrationTest.groovy
    • -0
    • +3
    ./testing/testng/SampleTestNGIntegrationTest.groovy
  1. … 20 more files in changeset.
Include output of all failed suites in HTML report (#11262)

Prior to this commit, only the output of the root `TestDescriptor` was

included in the HTML report even though all failed suites were included

with their exceptions.

    • -1
    • +39
    ./testing/TestReportIntegrationTest.groovy
  1. … 8 more files in changeset.
Include output of all failed suites in HTML report

Prior to this commit, only the output of the root `TestDescriptor` was

included in the HTML report even though all failed suites were included

with their exceptions.

    • -1
    • +40
    ./testing/TestReportIntegrationTest.groovy
  1. … 8 more files in changeset.
Include output of all failed suites in HTML report

Prior to this commit, only the output of the root `TestDescriptor` was

included in the HTML report even though all failed suites were included

with their exceptions.

    • -1
    • +39
    ./testing/TestReportIntegrationTest.groovy
  1. … 8 more files in changeset.
Include output of all failed suites in HTML report

Prior to this commit, only the output of the root `TestDescriptor` was

included in the HTML report even though all failed suites were included

with their exceptions.

    • -1
    • +39
    ./testing/TestReportIntegrationTest.groovy
  1. … 8 more files in changeset.
Restore package prefix in case the test is run with JUnit 4.x as pointed out by @marcphilipp

    • -3
    • +6
    ./testing/junit/JUnitConsoleLoggingIntegrationTest.groovy
Fix failing more tests

    • -3
    • +3
    ./testing/junit/JUnitConsoleLoggingIntegrationTest.groovy
Adopt tests to new behavior

    • -1
    • +1
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
    • -26
    • +1
    ./testing/junitplatform/JUnitPlatformLoggingIntegrationTest.groovy
Adopt tests to new behavior

    • -1
    • +1
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
    • -26
    • +1
    ./testing/junitplatform/JUnitPlatformLoggingIntegrationTest.groovy
Adopt tests to new behavior

    • -1
    • +1
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
    • -26
    • +1
    ./testing/junitplatform/JUnitPlatformLoggingIntegrationTest.groovy
Revert "Fix edge case for class display names"

This reverts commit e04ef3476cd3927bb972a60e7184332d6e29876c.

  1. … 2 more files in changeset.
Revert "Fix edge case for class display names"

This reverts commit e04ef3476cd3927bb972a60e7184332d6e29876c.

  1. … 2 more files in changeset.
Revert "Fix edge case for class display names"

This reverts commit e04ef3476cd3927bb972a60e7184332d6e29876c.

  1. … 2 more files in changeset.
Fix edge case for class display names

Simply using the class display name in test logging does not work,

because JUnit platform returns only the simple class name from

TestIdentifier.getDisplayName(). This results in the fully qualified

package name being cut off for top level classes.

This change adds some logic that tried to find out whether the display

name has been explicitly se tor not. If so then the class display name

will we use. If not the fully qualified class name will be used for top

level classes and the simple class name will be used for inner classes.

There is still one corner case that is not supported with this solution:

A user could set the simple class name as display name in order to remove

the package name from the output. Since there is no way to tell whether

this was explicitly configured by the user or not by looking at the

TestIdentifier, there does not seem to be a way to support this.

  1. … 2 more files in changeset.
Fix edge case for class display names

Simply using the class display name in test logging does not work,

because JUnit platform returns only the simple class name from

TestIdentifier.getDisplayName(). This results in the fully qualified

package name being cut off for top level classes.

This change adds some logic that tried to find out whether the display

name has been explicitly se tor not. If so then the class display name

will we use. If not the fully qualified class name will be used for top

level classes and the simple class name will be used for inner classes.

There is still one corner case that is not supported with this solution:

A user could set the simple class name as display name in order to remove

the package name from the output. Since there is no way to tell whether

this was explicitly configured by the user or not by looking at the

TestIdentifier, there does not seem to be a way to support this.

  1. … 2 more files in changeset.
Fix edge case for class display names

Simply using the class display name in test logging does not work,

because JUnit platform returns only the simple class name from

TestIdentifier.getDisplayName(). This results in the fully qualified

package name being cut off for top level classes.

This change adds some logic that tried to find out whether the display

name has been explicitly se tor not. If so then the class display name

will we use. If not the fully qualified class name will be used for top

level classes and the simple class name will be used for inner classes.

There is still one corner case that is not supported with this solution:

A user could set the simple class name as display name in order to remove

the package name from the output. Since there is no way to tell whether

this was explicitly configured by the user or not by looking at the

TestIdentifier, there does not seem to be a way to support this.

  1. … 2 more files in changeset.
Add more test cases

Some tests are still failing, this need discussion on how to handle

class display names.

Co-authored-by: Mark Nordhoff <mark.nordhoff@freenet.de>

    • -8
    • +67
    ./testing/junitplatform/JUnitPlatformLoggingIntegrationTest.groovy
Add more test cases

Some tests are still failing, this need discussion on how to handle

class display names.

Co-authored-by: Mark Nordhoff <mark.nordhoff@freenet.de>

    • -8
    • +67
    ./testing/junitplatform/JUnitPlatformLoggingIntegrationTest.groovy
Add more test cases

Some tests are still failing, this need discussion on how to handle

class display names.

Co-authored-by: Mark Nordhoff <mark.nordhoff@freenet.de>

    • -8
    • +67
    ./testing/junitplatform/JUnitPlatformLoggingIntegrationTest.groovy
Use display name in test logging

Test logging now logs the display name if it is available.

Fixes: #10983

Co-authored-by: Mark Nordhoff <mark.nordhoff@freenet.de>

    • -1
    • +1
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
    • -3
    • +6
    ./testing/junit/JUnitConsoleLoggingIntegrationTest.groovy
    • -0
    • +101
    ./testing/junitplatform/JUnitPlatformLoggingIntegrationTest.groovy
  1. … 3 more files in changeset.
Use display name in test logging

Test logging now logs the display name if it is available.

Fixes: #10983

Co-authored-by: Mark Nordhoff <mark.nordhoff@freenet.de>

    • -1
    • +1
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
    • -3
    • +6
    ./testing/junit/JUnitConsoleLoggingIntegrationTest.groovy
    • -0
    • +101
    ./testing/junitplatform/JUnitPlatformLoggingIntegrationTest.groovy
  1. … 4 more files in changeset.