testing-jvm

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Declare missing path sensitivity for TestNGOptions.suiteXmlFiles

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.
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.
Move convention into Java/JavaBase plugins

  1. … 2 more files in changeset.
Move convention into Java/JavaBase plugins

  1. … 2 more files in changeset.
Move convention into Java/JavaBase plugins

  1. … 2 more files in changeset.
Merge remote-tracking branch 'origin/marc/test-framework-auto-detection'

* origin/marc/test-framework-auto-detection:

Make Checkstyle happy

Give JUnit 4 precedence over JUnit Platform and TestNG

Fix tests

Check only files on the classpath

Autodetect TestFramework if none is configure explicitly

Fix property annotations for TestNGOptions

De-incubate testing pre-5.0

- JUnit platform

- Abstract test task properties

  1. … 2 more files in changeset.
Use a non-decorated fork options when creating fork options for worker daemon

WorkerDaemonClients are retained across builds, so any object associated with

it must not contain project state since this will be kept around until the worker

expires.

- Introduce a newDecoratedJavaForkOptions which creates a decorated JavaForkOptionsInternal

- Replace calls to the decorated version of the method with non-decorated versions where appropriate

  1. … 10 more files in changeset.
Use a non-decorated fork options when creating fork options for worker daemon

WorkerDaemonClients are retained across builds, so any object associated with

it must not contain project state since this will be kept around until the worker

expires.

- Introduce a newDecoratedJavaForkOptions which creates a decorated JavaForkOptionsInternal

- Replace calls to the decorated version of the method with non-decorated versions where appropriate

  1. … 10 more files in changeset.
Use a non-decorated fork options when creating fork options for worker daemon

WorkerDaemonClients are retained across builds, so any object associated with

it must not contain project state since this will be kept around until the worker

expires.

- Introduce a newDecoratedJavaForkOptions which creates a decorated JavaForkOptionsInternal

- Replace calls to the decorated version of the method with non-decorated versions where appropriate

  1. … 13 more files in changeset.
Use a non-decorated fork options when creating fork options for worker daemon

WorkerDaemonClients are retained across builds, so any object associated with

it must not contain project state since this will be kept around until the worker

expires.

- Introduce a newDecoratedJavaForkOptions which creates a decorated JavaForkOptionsInternal

- Replace calls to the decorated version of the method with non-decorated versions where appropriate

  1. … 10 more files in changeset.
Use a non-decorated fork options when creating fork options for worker daemon

WorkerDaemonClients are retained across builds, so any object associated with

it must not contain project state since this will be kept around until the worker

expires.

- Introduce a newDecoratedJavaForkOptions which creates a decorated JavaForkOptionsInternal

- Replace calls to the decorated version of the method with non-decorated versions where appropriate

  1. … 14 more files in changeset.
Make Checkstyle happy

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.

Check only files on the classpath

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.

  1. … 9 more files in changeset.
Reduce the dependency on commons-lang

  1. … 5 more files in changeset.
Remove bsh dependency

  1. … 2 more files in changeset.
Revert "Revert "Add debug support to TestLauncher (#9863)""

This reverts commit 17d0ec1ba0dd44df1a6e2e2f8e79c366faa2bee7.

  1. … 39 more files in changeset.
Revert "Add debug support to TestLauncher (#9863)"

This reverts commits 026d9f4f8b33e64a64fd0f9f4c364b4c7cebf26f and fda0f3d58074137a1e9204fbf2762d9f63a0603b.

Temporarily reverted due to a possible performance regression.

  1. … 40 more files in changeset.
Add debug support to TestLauncher (#9863)

  1. … 39 more files in changeset.
Use Property API in JavaDebugOptions

  1. … 14 more files in changeset.
Use Property API in JavaDebugOptions

  1. … 13 more files in changeset.
Use Property API in JavaDebugOptions

  1. … 17 more files in changeset.
Use Property API in JavaDebugOptions

  1. … 13 more files in changeset.
Use Property API in JavaDebugOptions

  1. … 13 more files in changeset.