JUnitStandaloneTestExecutionIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Expect deprecation warnings in tests

    • -0
    • +1
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 55 more files in changeset.
Expect deprecation warnings in tests

    • -0
    • +1
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 53 more files in changeset.
Expect deprecation warnings in tests

    • -0
    • +1
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 54 more files in changeset.
Expect deprecation warnings in tests

    • -0
    • +1
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 43 more files in changeset.
Expect deprecation warnings in tests

    • -0
    • +1
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 60 more files in changeset.
Expect deprecation warnings in tests

    • -0
    • +1
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 55 more files in changeset.
Expect deprecation warnings in tests

    • -0
    • +1
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 55 more files in changeset.
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -13
    • +13
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 872 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -4
    • +0
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 36 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -4
    • +0
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 38 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -4
    • +0
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 37 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -4
    • +0
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 37 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -4
    • +0
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 37 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after second round of CI feedback

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +4
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 32 more files in changeset.
Annotate integ tests failing with instant execution in :testingJvm

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +13
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 34 more files in changeset.
Annotate integ tests failing with instant execution in :testingJvm

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +13
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 34 more files in changeset.
Replace 'Matchers' with 'CoreMatchers'

So we do not require 'org.hamcrest:hamcrest-library' as additional

dependency anymore. Which was only available for most of the tests

because it leaked onto the test compile classpath.

    • -2
    • +2
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 162 more files in changeset.
Use 'implementation' dependencies everywhere

    • -2
    • +2
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 286 more files in changeset.
Use 'implementation' dependencies everywhere

    • -2
    • +2
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 283 more files in changeset.
Use 'implementation' dependencies everywhere

    • -2
    • +2
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 286 more files in changeset.
Use 'implementation' dependencies everywhere

    • -2
    • +2
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 284 more files in changeset.
Use 'implementation' dependencies everywhere

    • -2
    • +2
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 285 more files in changeset.
Use 'implementation' dependencies everywhere

    • -2
    • +2
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 285 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
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 61 more files in changeset.
Change int tests to use relevant fixture methods to express their expectations about the build log output.

    • -3
    • +2
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 22 more files in changeset.
Review and improve tests that require exact ordering of tasks

    • -2
    • +2
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 23 more files in changeset.
Capture inability to customise JUnit version per binary

Leaving `@Ignore`d test case for future reference.

    • -0
    • +24
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
Make sure that we have a separate report directory for each binary variant of the component under test

Story: gradle/langos#113

    • -3
    • +3
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 3 more files in changeset.
Minimize impact by reverting unnecessary changes

+review REVIEW-5796

    • -11
    • +11
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 1 more file in changeset.
Property extraction in software model now respect the JavaBean spec

Use `java.beans.Introspector.decapitalize(..)` instead of

`o.a.commons.lang.StringUtils.uncapitalize(..)` for property names

extraction.

Rename `JUnitTestSuiteSpec.getJUnitVersion()` to

`JUnitTestSuiteSpec.getjUnitVersion()`

Slightly deviate from the spec: if the property name part of a

get/setter method name starts with more than one lowercase char, we

don't consider it as a property method. This is to allow method names

like `Some gettingStarted()`, `void settings(Some some)`

or `boolean isidore()`.

Add/adapt test coverage.

Add mention in release notes under potential breaking changes section.

+review REVIEW-5796

    • -11
    • +11
    ./JUnitStandaloneTestExecutionIntegrationTest.groovy
  1. … 12 more files in changeset.