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

    • -0
    • +101
    ./gradle/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. 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>

  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. … 3 more files in changeset.
Fix executing Specs tests via JUnit Platform and Vintage engine

Prior to this commit, the JUnitPlatformTestExecutionListener parsed the

unique ID to determine the class and method name for TestIdentifiers

without children but with a ClassSource. This occurs when a Spock test

class uses `@Unroll` on all its test methods. However, other testing

frameworks such as Specs2 don't provide a unique ID that is parseable

which lead to the methodName being null which cause a failure during

serialization. The effect was that tests hung because the build VM

was waiting for the worker to finish the tests it started.

The Spock-specific workaround in our listener is now replaced with a

more robust one that always uses the methodName provided by the JUnit

Platform instead of parsing it.

  1. … 1 more file in changeset.
Fix executing Specs tests via JUnit Platform and Vintage engine

Prior to this commit, the JUnitPlatformTestExecutionListener parsed the

unique ID to determine the class and method name for TestIdentifiers

without children but with a ClassSource. This occurs when a Spock test

class uses `@Unroll` on all its test methods. However, other testing

frameworks such as Specs2 don't provide a unique ID that is parseable

which lead to the methodName being null which cause a failure during

serialization. The effect was that tests hung because the build VM

was waiting for the worker to finish the tests it started.

The Spock-specific workaround in our listener is now replaced with a

more robust one that always uses the methodName provided by the JUnit

Platform instead of parsing it.

    • -0
    • +72
    ./gradle/testing/junit/Specs2IntegrationTest.groovy
  1. … 1 more file in changeset.
Fix executing Specs tests via JUnit Platform and Vintage engine

Prior to this commit, the JUnitPlatformTestExecutionListener parsed the

unique ID to determine the class and method name for TestIdentifiers

without children but with a ClassSource. This occurs when a Spock test

class uses `@Unroll` on all its test methods. However, other testing

frameworks such as Specs2 don't provide a unique ID that is parseable

which lead to the methodName being null which cause a failure during

serialization. The effect was that tests hung because the build VM

was waiting for the worker to finish the tests it started.

The Spock-specific workaround in our listener is now replaced with a

more robust one that always uses the methodName provided by the JUnit

Platform instead of parsing it.

  1. … 1 more file in changeset.
Fix executing Specs tests via JUnit Platform and Vintage engine

Prior to this commit, the JUnitPlatformTestExecutionListener parsed the

unique ID to determine the class and method name for TestIdentifiers

without children but with a ClassSource. This occurs when a Spock test

class uses `@Unroll` on all its test methods. However, other testing

frameworks such as Specs2 don't provide a unique ID that is parseable

which lead to the methodName being null which cause a failure during

serialization. The effect was that tests hung because the build VM

was waiting for the worker to finish the tests it started.

The Spock-specific workaround in our listener is now replaced with a

more robust one that always uses the methodName provided by the JUnit

Platform instead of parsing it.

  1. … 1 more file in changeset.
Give JUnit 4 precedence over JUnit Platform and TestNG

For backwards compatibility, JUnit 4 takes precendence over TestNG and

JUnit Platform since groovy-all ships with dependencies on both. In the

latter case, JUnit Platform is used if both junit-vintage-engine and

JUnit 4 are on the classpath.

    • -27
    • +55
    ./gradle/testing/TestFrameworkAutoDetectionIntegrationTest.groovy
  1. … 1 more file in changeset.
Autodetect TestFramework if none is configure explicitly

When the TestFramework of a Test task is not configured explicitly it

used to default to `useJUnit()`. Now, the task's classpath is inspected

for a junit-platform-engine.jar or testng.jar. If one of them is found,

the task uses the JUnit Platform or TestNG to execute tests,

respectively.

Since we have internal dependencies on the JUnit Platform and TestNG,

all Test tasks in our own build are configured to `useJUnit()` and

explicitly.

    • -0
    • +108
    ./gradle/testing/TestFrameworkAutoDetectionIntegrationTest.groovy
    • -0
    • +18
    ./gradle/testing/TestTaskIntegrationTest.groovy
  1. … 11 more files in changeset.
Fix for change to int tests.

Fix for change to int tests.

Fix for change to int tests.

Fix for change to int tests.

Remove an unnecessary `@IgnoreIf` from a bunch of tests.

  1. … 16 more files in changeset.
Remove an unnecessary `@IgnoreIf` from a bunch of tests.

    • -11
    • +13
    ./gradle/testing/TestReportIntegrationTest.groovy
  1. … 16 more files in changeset.
Remove an unnecessary `@IgnoreIf` from a bunch of tests.

  1. … 16 more files in changeset.
Remove an unnecessary `@IgnoreIf` from a bunch of tests.

    • -11
    • +13
    ./gradle/testing/TestReportIntegrationTest.groovy
  1. … 16 more files in changeset.
Upgrade commons-lang{->3} replacing packages

  1. … 175 more files in changeset.
Update Spock framework to 1.3

  1. … 24 more files in changeset.
Update Spock framework to 1.3

  1. … 24 more files in changeset.
Removed `ExecutionResult.executedTasks` and `skippedTasks` properties. Tests should use the assertion methods instead.

  1. … 5 more files in changeset.
Removed `ExecutionResult.executedTasks` and `skippedTasks` properties. Tests should use the assertion methods instead.

  1. … 5 more files in changeset.
Removed `ExecutionResult.executedTasks` and `skippedTasks` properties. Tests should use the assertion methods instead.

  1. … 5 more files in changeset.
Removed `ExecutionResult.executedTasks` and `skippedTasks` properties. Tests should use the assertion methods instead.

  1. … 5 more files in changeset.
Change more tests.

  1. … 39 more files in changeset.
Change more tests.

  1. … 17 more files in changeset.
Change more tests.

  1. … 13 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -12
    • +12
    ./gradle/testing/TestReportIntegrationTest.groovy
  1. … 95 more files in changeset.