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

    • -5
    • +0
    ./testing/DecoratingTestDescriptor.java
    • -5
    • +0
    ./testing/processors/TestMainAction.java
  1. … 3 more files in changeset.
Remove unused imports

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.

    • -5
    • +0
    ./testing/DecoratingTestDescriptor.java
    • -5
    • +0
    ./testing/processors/TestMainAction.java
  1. … 3 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.

    • -5
    • +0
    ./testing/DecoratingTestDescriptor.java
    • -5
    • +0
    ./testing/processors/TestMainAction.java
  1. … 3 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.

    • -5
    • +0
    ./testing/DecoratingTestDescriptor.java
    • -5
    • +0
    ./testing/processors/TestMainAction.java
  1. … 3 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
    • +7
    ./testing/logging/StackTraceFilter.java
  1. … 7 more files in changeset.
Change the various `Report` implementations to be abstract and remove some wiring.

Also fix the class generator to handle an abstract getter from a super class whose return type is not supported for managed properties, but which is overridden by another getter whose return type is supported (eg a `Provider<T>` getter overridden by a `Property<T>` getter).

  1. … 5 more files in changeset.
Change the various `Report` implementations to be abstract and remove some wiring.

Also fix the class generator to handle an abstract getter from a super class whose return type is not supported for managed properties, but which is overridden by another getter whose return type is supported (eg a `Provider<T>` getter overridden by a `Property<T>` getter).

  1. … 5 more files in changeset.
Change the various `Report` implementations to be abstract and remove some wiring.

Also fix the class generator to handle an abstract getter from a super class whose return type is not supported for managed properties, but which is overridden by another getter whose return type is supported (eg a `Provider<T>` getter overridden by a `Property<T>` getter).

  1. … 5 more files in changeset.
Change the various `Report` implementations to be abstract and remove some wiring.

Also fix the class generator to handle an abstract getter from a super class whose return type is not supported for managed properties, but which is overridden by another getter whose return type is supported (eg a `Provider<T>` getter overridden by a `Property<T>` getter).

  1. … 5 more files in changeset.
Add properties on `Report` and subtypes to allow wiring using `Providers`. Specifically, add `Report.activated` to replace `enabled` and `outputLocation` to replace destination.

Change the Java base plugin to use these properties instead of convention mapping to attach conventions for the test report locations.

  1. … 25 more files in changeset.
Add properties on `Report` and subtypes to allow wiring using `Providers`. Specifically, add `Report.activated` to replace `enabled` and `outputLocation` to replace destination.

Change the Java base plugin to use these properties instead of convention mapping to attach conventions for the test report locations.

  1. … 12 more files in changeset.
Add properties on `Report` and subtypes to allow wiring using `Providers`. Specifically, add `Report.activated` to replace `enabled` and `outputLocation` to replace destination.

Change the Java base plugin to use these properties instead of convention mapping to attach conventions for the test report locations.

  1. … 25 more files in changeset.
Add properties on `Report` and subtypes to allow wiring using `Providers`. Specifically, add `Report.activated` to replace `enabled` and `outputLocation` to replace destination.

Change the Java base plugin to use these properties instead of convention mapping to attach conventions for the test report locations.

  1. … 12 more files in changeset.
Expose getDisplayName

Fixes: #11035

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

  1. … 2 more files in changeset.
Expose getDisplayName

Fixes: #11035

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

  1. … 2 more files in changeset.
Expose getDisplayName

Fixes: #11035

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

  1. … 2 more files in changeset.
Expose getDisplayName

Fixes: #11035

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

  1. … 2 more files in changeset.
Expose getDisplayName

Fixes: #11035

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

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

This reverts commit e04ef3476cd3927bb972a60e7184332d6e29876c.

    • -14
    • +0
    ./testing/DefaultTestClassDescriptor.java
  1. … 2 more files in changeset.
Revert "Fix edge case for class display names"

This reverts commit e04ef3476cd3927bb972a60e7184332d6e29876c.

    • -14
    • +0
    ./testing/DefaultTestClassDescriptor.java
  1. … 2 more files in changeset.
Revert "Fix edge case for class display names"

This reverts commit e04ef3476cd3927bb972a60e7184332d6e29876c.

    • -14
    • +0
    ./testing/DefaultTestClassDescriptor.java
  1. … 2 more files in changeset.
Restore behavior for TestNG case

    • -1
    • +1
    ./testing/logging/AbstractTestLogger.java
Restore behavior for TestNG case

    • -1
    • +1
    ./testing/logging/AbstractTestLogger.java
Restore behavior for TestNG case

    • -1
    • +1
    ./testing/logging/AbstractTestLogger.java
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.

    • -0
    • +14
    ./testing/DefaultTestClassDescriptor.java
  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.

    • -0
    • +14
    ./testing/DefaultTestClassDescriptor.java
  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.

    • -0
    • +14
    ./testing/DefaultTestClassDescriptor.java
  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.

    • -0
    • +14
    ./testing/DefaultTestClassDescriptor.java
  1. … 2 more files in changeset.
Invert dependency between getDisplayName() and getClassDisplayName()

    • -2
    • +2
    ./testing/DefaultTestClassDescriptor.java