Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add support for test `@DisplayName` (#13250)

If @DisplayName annotation is attached, output the value to test result XML.

* Recognize contributor

* Add missing `@UsedByScanPlugin` annotations

Co-authored-by: Daiki Hirabayashi <hirabayashi@infoscience.co.jp>

Co-authored-by: Daiki Hirabayashi <gigabowser@hotmail.co.jp>

Signed-off-by: Daiki Hirabayashi <hirabayashi@infoscience.co.jp>

  1. … 12 more files in changeset.
Add missing `@UsedByScanPlugin` annotations

Polish support for `@DisplayName` in tests

In particular, remove the need to pass a `hasDisplayNameAnnotation` flag

around, which is too specific for the test descriptors.

  1. … 4 more files in changeset.
Add dedicated placeholder assertion error type

This commit introduces a dedicated placeholder assertion error

type which is used whenever a subtype of `AssertionError` cannot

be deserialized. Before, we would use the regular `PlaceholderException`,

which happens to discard the fact that it's an `AssertionError`.

The consequence is that IntelliJ IDEA in combination with Spock can't

infer the correct failure kind, and displays a wrong icon (see #12302).

It does not, however, fix the problem that the "Click here to see diff"

link doesn't show up. The reason is that this feature builds on top

of a dedicated subtype of `AssertionError` that the messaging bus

isn't aware of (org.opentest4j.AssertionFailedError and its legacy JUnit

equivalent).

Fixes #12302

  1. … 5 more files in changeset.
Remove hasDisplayNameAnnotation() method from the public API.

Issue: #11445

Signed-off-by: Daiki Hirabayashi <hirabayashi@infoscience.co.jp>

    • -6
    • +0
    ./gradle/api/tasks/testing/TestDescriptor.java
Merge branch 'master' into master

  1. … 7 more files in changeset.
If @DisplayName annotation is attached, output the annotation value to name attribute of testsuite and name attribute of testcase. If @DisplayName annotation is not attached, output the class FQN. In any case, output the class FQN to classname attribute of testcase.

Issue: #11445

Signed-off-by: Daiki Hirabayashi <hirabayashi@infoscience.co.jp>

    • -0
    • +6
    ./gradle/api/tasks/testing/TestDescriptor.java
  1. … 12 more files in changeset.
Fixes for listeners.

    • -1
    • +5
    ./gradle/api/tasks/testing/TestListener.java
  1. … 2 more files in changeset.
Fixes for listeners.

    • -1
    • +5
    ./gradle/api/tasks/testing/TestListener.java
  1. … 2 more files in changeset.
Fixes for listeners.

    • -1
    • +5
    ./gradle/api/tasks/testing/TestListener.java
  1. … 2 more files in changeset.
Fixes for listeners.

    • -1
    • +5
    ./gradle/api/tasks/testing/TestListener.java
  1. … 2 more files in changeset.
Introduce internal `@EventScope` annotation to attach to listener interfaces to declare which scope their events are generated in.

Add some validation to `ListenerManager` to verify that each listener interface is annotated with the correct scope.

    • -1
    • +5
    ./gradle/api/tasks/testing/TestListener.java
  1. … 60 more files in changeset.
Introduce internal `@EventScope` annotation to attach to listener interfaces to declare which scope their events are generated in.

Add some validation to `ListenerManager` to verify that each listener interface is annotated with the correct scope.

    • -1
    • +5
    ./gradle/api/tasks/testing/TestListener.java
  1. … 60 more files in changeset.
Introduce internal `@EventScope` annotation to attach to listener interfaces to declare which scope their events are generated in.

Add some validation to `ListenerManager` to verify that each listener interface is annotated with the correct scope.

    • -1
    • +5
    ./gradle/api/tasks/testing/TestListener.java
  1. … 60 more files in changeset.
Introduce internal `@EventScope` annotation to attach to listener interfaces to declare which scope their events are generated in.

Add some validation to `ListenerManager` to verify that each listener interface is annotated with the correct scope.

    • -1
    • +5
    ./gradle/api/tasks/testing/TestListener.java
  1. … 60 more files in changeset.
Introduce internal `@EventScope` annotation to attach to listener interfaces to declare which scope their events are generated in.

Add some validation to `ListenerManager` to verify that each listener interface is annotated with the correct scope.

    • -1
    • +5
    ./gradle/api/tasks/testing/TestListener.java
  1. … 60 more files in changeset.
Introduce internal `@EventScope` annotation to attach to listener interfaces to declare which scope their events are generated in.

Add some validation to `ListenerManager` to verify that each listener interface is annotated with the correct scope.

    • -1
    • +5
    ./gradle/api/tasks/testing/TestListener.java
  1. … 60 more files in changeset.
Introduce internal `@EventScope` annotation to attach to listener interfaces to declare which scope their events are generated in.

Add some validation to `ListenerManager` to verify that each listener interface is annotated with the correct scope.

    • -1
    • +5
    ./gradle/api/tasks/testing/TestListener.java
  1. … 60 more files in changeset.
Annotate internal APIs used by test-distribution (#13010)

In order to avoid accidentally changing an internal API without

adjusting the test-distribution plugin, they are now annotated with

`@UsedByScanPlugin("test-distribution")`.

  1. … 22 more files in changeset.
Always annotate used type and methods

  1. … 5 more files in changeset.
Annotate internal APIs used by test-distribution

In order to avoid accidentally changing an internal API without

adjusting the test-distribution plugin, they are now annotated with

`@UsedByScanPlugin("test-distribution")`.

  1. … 22 more files in changeset.
Address compiler warnings in 'testing-base' subproject

    • -1
    • +2
    ./gradle/api/tasks/testing/AbstractTestTask.java
  1. … 1 more file in changeset.
Address compiler warnings in 'testing-base' subproject

    • -1
    • +2
    ./gradle/api/tasks/testing/AbstractTestTask.java
  1. … 1 more file in changeset.
Address compiler warnings in 'testing-base' subproject

    • -1
    • +2
    ./gradle/api/tasks/testing/AbstractTestTask.java
  1. … 1 more file in changeset.
Rename 'modularClasspathHandling' -> 'modularity'

  1. … 56 more files in changeset.
Rename 'modularClasspathHandling' -> 'modularity'

  1. … 55 more files in changeset.
Rename 'modularClasspathHandling' -> 'modularity'

  1. … 56 more files in changeset.
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.

  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.

  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.

  1. … 9 more files in changeset.