Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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.

Invert dependency between getDisplayName() and getClassDisplayName()

Invert dependency between getDisplayName() and getClassDisplayName()

Invert dependency between getDisplayName() and getClassDisplayName()

Update released version to latest snapshot

Update version to 6.2

Clean accepted API changes

Merge remote-tracking branch 'origin/master-test' into release-test

Publish 6.0-20191012230026+0000

Update released version to latest snapshot

Update version to 6.2

Clean accepted API changes

Merge remote-tracking branch 'origin/master-test' into release-test

Use single-threaded access for VFS mutation

Use single-threaded access for VFS mutation

Use single-threaded access for VFS mutation

Use single-threaded access for VFS mutation

Use single-threaded access for VFS mutation

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>

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>

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>

Use JaCoCo 0.8.5 by default

Signed-off-by: Evgeny Mandrikov <mandrikov@gmail.com>

    • -1
    • +1
    /subprojects/docs/src/docs/dsl/org.gradle.testing.jacoco.plugins.JacocoPluginExtension.xml
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>

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>

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>

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>

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>

Use display name in test logging

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

getDisplayName() and getClassDisplayName() are moved from

TestDescriptorInternal to TestDescriptor making them available in

beforeTest and afterTest callbacks.

Fixes: #10983

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

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>

Simplify BuildOperationTrace after resolution of #4241