Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Run tests against JUnit 4.13-beta-2

    • -6
    • +7
    ./testing/fixture/JUnitCoverage.groovy
Rollback to 5.3.1

    • -2
    • +2
    ./testing/fixture/JUnitCoverage.groovy
Fix handling of aborted containers with completed children

When a container `TestIdentifier` was reported as finished, we reported

all of its children as skipped, regardless whether they already had been

completed previously. Now, we only report unstarted children as skipped.

Resolves #8685.

    • -2
    • +2
    ./testing/fixture/JUnitCoverage.groovy
    • -0
    • +53
    ./testing/junit/JUnitAbortedTestClassIntegrationTest.groovy
  1. … 3 more files in changeset.
Fix handling of aborted containers with completed children

When a container `TestIdentifier` was reported as finished, we reported

all of its children as skipped, regardless whether they already had been

completed previously. Now, we only report unstarted children as skipped.

Resolves #8685.

    • -2
    • +2
    ./testing/fixture/JUnitCoverage.groovy
    • -0
    • +53
    ./testing/junit/JUnitAbortedTestClassIntegrationTest.groovy
  1. … 3 more files in changeset.
Fix handling of aborted containers with completed children

When a container `TestIdentifier` was reported as finished, we reported

all of its children as skipped, regardless whether they already had been

completed previously. Now, we only report unstarted children as skipped.

Resolves #8685.

    • -2
    • +2
    ./testing/fixture/JUnitCoverage.groovy
    • -0
    • +53
    ./testing/junit/JUnitAbortedTestClassIntegrationTest.groovy
  1. … 3 more files in changeset.
Fix for previous commit.

    • -3
    • +1
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
Simplify tests that look for rich content in the console output.

    • -2
    • +2
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
  1. … 16 more files in changeset.
Simplify tests that look for rich content in the console output.

    • -2
    • +2
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
  1. … 16 more files in changeset.
Simplify tests that look for rich content in the console output.

    • -3
    • +5
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
  1. … 13 more files in changeset.
Simplify tests that look for rich content in the console output.

    • -2
    • +2
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
  1. … 16 more files in changeset.
Simplify tests that look for rich content in the console output.

    • -2
    • +2
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
  1. … 16 more files in changeset.
Simplify tests that look for rich content in the console output.

    • -2
    • +2
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
  1. … 16 more files in changeset.
Simplify tests that look for rich content in the console output.

    • -2
    • +2
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
  1. … 16 more files in changeset.
Simplify tests that look for rich content in the console output.

    • -3
    • +5
    ./testing/fixture/AbstractJvmFailFastIntegrationSpec.groovy
  1. … 13 more files in changeset.
Update references to 1.6 compatibility to 1.7

    • -7
    • +7
    ./jvm/test/JUnitComponentUnderTestIntegrationTest.groovy
  1. … 20 more files in changeset.
Update references to 1.6 compatibility to 1.7

    • -7
    • +7
    ./jvm/test/JUnitComponentUnderTestIntegrationTest.groovy
  1. … 20 more files in changeset.
Add test output only once to cache artifact

Both reports have been added to the cached artifact by accident, since

the reports are declared as nested parameters via `enabledReports` on

the `ReportContainer` and the getters on `TestTaskReports`.

The annotated getters on `TestTaskReports` also prevented the test task

to be up-to-date when only the configuration for disabled reports

changed.

    • -0
    • +24
    ./testing/IncrementalTestIntegrationTest.groovy
  1. … 1 more file in changeset.
spelling: uninstantiable

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

spelling: parentheses

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

    • -1
    • +1
    ./testing/junit/JUnitLoggingOutputCaptureIntegrationTest.groovy
  1. … 1 more file in changeset.
Support multiple concurrent executions of same TestNG class

When the same test class is executed concurrently, we now only report

the first start and the last completion of the test class. Previously,

the test class was reported as started multiple times but only reported

as completed once.

Fixes #7878.

    • -0
    • +36
    ./testing/testng/TestNGIntegrationTest.groovy
  1. … 1 more file in changeset.
Increase number of test classes executing in parallel

Improve readability of test

    • -36
    • +42
    ./testing/TestListenerBuildOperationAdapterIntegrationTest.groovy
Polishing

  1. … 7 more files in changeset.
Add support for executing test classes in parallel via JUnit Platform

Fixes #6453.

    • -12
    • +28
    ./testing/TestListenerBuildOperationAdapterIntegrationTest.groovy
    • -2
    • +2
    ./testing/fixture/JUnitCoverage.groovy
    • -6
    • +6
    ./testing/fixture/JUnitMultiVersionIntegrationSpec.groovy
    • -13
    • +0
    ./testing/junit/JUnitIntegrationTest.groovy
    • -5
    • +12
    ./testing/junit/JUnitSmokeMultiVersionIntegrationSpec.groovy
  1. … 7 more files in changeset.
Finalize the value of any task `@Input` property whose getter returns a property instance, at the start of execution of the task.

This means that the property value will not change once the task has started execution, so that the same value is always used during fingerprinting, cache key calculation, validation, when queried by a task action, and so on.

This behaviour only applies to `@Input` properties in this commit. This was just a place to start. Other properties will be added in later commits.

Changes to the property are ignored once the value is finalized implicitly in this way and generate a deprecation warning instead of failing, as would happen after `finalizeValue()` is called. This allows a migration path for task types that can add a new property to represent some input and keep their existing lenient (but now deprecated) behaviour for an existing property backed by the new property. It might prove better to flip this around, let's see.

    • -1
    • +1
    ./jvm/test/JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 61 more files in changeset.
Try to execute unparseable test class files

Instead of failing the build when a test class file cannot be parsed,

e.g. if it's compiled for a JVM that is not yet supported by the

version of ASM that we use, we now assume it's a test class and pass

it to the testing framework which usually ignores classes that are not

tests.

Related issue: #7059

    • -2
    • +2
    ./testing/fixture/JUnitMultiVersionIntegrationSpec.groovy
    • -1
    • +32
    ./testing/junit/JUnitIntegrationTest.groovy
    • -0
    • +15
    ./testing/testng/TestNGIntegrationTest.groovy
  1. … 4 more files in changeset.
Try to execute unparseable test class files

Instead of failing the build when a test class file cannot be parsed,

e.g. if it's compiled for a JVM that is not yet supported by the

version of ASM that we use, we now assume it's a test class and pass

it to the testing framework which usually ignores classes that are not

tests.

Related issue: #7059

    • -2
    • +2
    ./testing/fixture/JUnitMultiVersionIntegrationSpec.groovy
    • -1
    • +32
    ./testing/junit/JUnitIntegrationTest.groovy
    • -0
    • +15
    ./testing/testng/TestNGIntegrationTest.groovy
  1. … 4 more files in changeset.
Remove log message that cannot be actioned by user

    • -2
    • +0
    ./testing/TestEnvironmentIntegrationTest.groovy
  1. … 1 more file in changeset.
Verify tests running in modular Java can access SLF4j

    • -1
    • +18
    ./testing/TestEnvironmentIntegrationTest.groovy
  1. … 7 more files in changeset.
Allow testing with `java.system.class.path` and SLF4j

The core `Slf4jLoggingConfigurer` assumes that the Gradle implementation

of `org.slf4j.ILoggerFactory` is being used. This is not the case when

tests are run using a custom system classloader (by setting the

`java.system.class.loader` system property).

Previously, this would result in a `ClassCastException` when attempting

to configure the logger. This change makes `Slf4jLoggingConfigurer` lenient

in this case, opting not to configure the underlying logger rather than

fail.

Fixes #2657

    • -0
    • +17
    ./testing/TestEnvironmentIntegrationTest.groovy
  1. … 4 more files in changeset.