Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Pull module path calculation into Test task (#12685)

This way, the JvmTestExecutionSpec already carries the final

classpath and module path. This makes is easier to create alternative

test worker implementations based on the spec.

    • -3
    • +3
    ./worker/ForkingTestClassProcessorTest.groovy
  1. … 10 more files in changeset.
Pull module path calculation into Test task

This way, the JvmTestExecutionSpec already carries the final

classpath and module path. This makes is easier to create alternative

test worker implementations based on the spec.

    • -3
    • +3
    ./worker/ForkingTestClassProcessorTest.groovy
  1. … 10 more files in changeset.
Adjust tests following changes to internal interfaces

    • -4
    • +22
    ./worker/ForkingTestClassProcessorTest.groovy
  1. … 2 more files in changeset.
Adjust tests following changes to internal interfaces

    • -4
    • +22
    ./worker/ForkingTestClassProcessorTest.groovy
  1. … 2 more files in changeset.
Force AbstractTestDirectoryProvider to use Class (#12431)

Closes https://github.com/gradle/gradle-private/issues/2988

This PR adds `className` to `AbstractTestDirectoryProvider` so there'll be no more `unknown-test-class`.

    • -1
    • +1
    ./junit/result/Binary2JUnitXmlReportGeneratorSpec.groovy
  1. … 405 more files in changeset.
Fix tests

    • -1
    • +1
    ./junit/result/Binary2JUnitXmlReportGeneratorSpec.groovy
  1. … 370 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.

    • -0
    • +15
    ./junit/result/TestReportDataCollectorSpec.groovy
  1. … 7 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.

    • -0
    • +15
    ./junit/result/TestReportDataCollectorSpec.groovy
  1. … 7 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.

    • -0
    • +15
    ./junit/result/TestReportDataCollectorSpec.groovy
  1. … 7 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.

    • -0
    • +15
    ./junit/result/TestReportDataCollectorSpec.groovy
  1. … 7 more files in changeset.
Retain stacktrace when test method is inherited

By default Gradle is trying to find "test class name" in the stacktrace (which is smart!), however,

there are cases when test class name never appears in the stacktrace.

For instance, it might happen when test class uses inheritance.

The inheritance is typically used to test over different implementations.

The fix is to retain the stacktrace in case none of the lines match.

fixes #11220

Signed-off-by: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>

    • -0
    • +20
    ./logging/FullExceptionFormatterTest.groovy
    • -11
    • +43
    ./logging/ShortExceptionFormatterTest.groovy
  1. … 6 more files in changeset.
Fix failing test

    • -17
    • +17
    ./logging/AbstractTestLoggerTest.groovy
Revert "Fix edge case for class display names"

This reverts commit e04ef3476cd3927bb972a60e7184332d6e29876c.

    • -18
    • +2
    ./DefaultTestClassDescriptorTest.groovy
  1. … 2 more files in changeset.
Revert "Fix edge case for class display names"

This reverts commit e04ef3476cd3927bb972a60e7184332d6e29876c.

    • -18
    • +2
    ./DefaultTestClassDescriptorTest.groovy
  1. … 2 more files in changeset.
Revert "Fix edge case for class display names"

This reverts commit e04ef3476cd3927bb972a60e7184332d6e29876c.

    • -18
    • +2
    ./DefaultTestClassDescriptorTest.groovy
  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.

    • -2
    • +18
    ./DefaultTestClassDescriptorTest.groovy
  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.

    • -2
    • +18
    ./DefaultTestClassDescriptorTest.groovy
  1. … 1 more file 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.

    • -2
    • +18
    ./DefaultTestClassDescriptorTest.groovy
  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.

    • -2
    • +18
    ./DefaultTestClassDescriptorTest.groovy
  1. … 2 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>

    • -17
    • +17
    ./logging/AbstractTestLoggerTest.groovy
  1. … 5 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>

    • -17
    • +17
    ./logging/AbstractTestLoggerTest.groovy
  1. … 6 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>

    • -17
    • +17
    ./logging/AbstractTestLoggerTest.groovy
  1. … 5 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>

    • -17
    • +17
    ./logging/AbstractTestLoggerTest.groovy
  1. … 5 more files in changeset.
Support surrogate pairs in SimpleXmlWriter

fixes #10770

Signed-off-by: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>

  1. … 4 more files in changeset.
Support surrogate pairs in SimpleXmlWriter

fixes #10770

Signed-off-by: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>

  1. … 4 more files in changeset.
Fix test

    • -2
    • +2
    ./worker/ForkingTestClassProcessorTest.groovy
Keep pineapple as a WORKER module

    • -2
    • +2
    ./worker/ForkingTestClassProcessorTest.groovy
  1. … 3 more files in changeset.
Revert "Add pineapple to worker classpath"

This reverts commit 500d2e6f28792688f6d7bb472a706d2e49ad2f7e.

    • -2
    • +2
    ./worker/ForkingTestClassProcessorTest.groovy
  1. … 3 more files in changeset.
Add pineapple to worker classpath

    • -2
    • +2
    ./worker/ForkingTestClassProcessorTest.groovy
  1. … 3 more files in changeset.
Add pineapple to worker classpath

    • -2
    • +2
    ./worker/ForkingTestClassProcessorTest.groovy
  1. … 4 more files in changeset.