CustomVersionListerIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove unnecessary @Unroll annotations from "dependencyManagement"

    • -3
    • +0
    ./CustomVersionListerIntegrationTest.groovy
  1. … 160 more files in changeset.
Test fixes for strictness.

    • -0
    • +2
    ./CustomVersionListerIntegrationTest.groovy
  1. … 13 more files in changeset.
Test fixes for strictness.

    • -0
    • +1
    ./CustomVersionListerIntegrationTest.groovy
  1. … 17 more files in changeset.
Test fixes for strictness.

    • -0
    • +1
    ./CustomVersionListerIntegrationTest.groovy
  1. … 17 more files in changeset.
Change `AbstractIntegrationSpec` to fail when a test runs a build that fails with more than one exception and does not verify the number of exceptions in the failure using `assertHasFailures()`.

This is to avoid additional exceptions unintentionally being introduced, for example when a failure starts being thrown because of configuration cache problems alongside the expected failure.

    • -0
    • +3
    ./CustomVersionListerIntegrationTest.groovy
  1. … 81 more files in changeset.
Change `AbstractIntegrationSpec` to fail when a test runs a build that fails with more than one exception and does not verify the number of exceptions in the failure using `assertHasFailures()`.

This is to avoid additional exceptions unintentionally being introduced, for example when a failure starts being thrown because of configuration cache problems alongside the expected failure.

    • -0
    • +3
    ./CustomVersionListerIntegrationTest.groovy
  1. … 81 more files in changeset.
Change `AbstractIntegrationSpec` to fail when a test runs a build that fails with more than one exception and does not verify the number of exceptions in the failure using `assertHasFailures()`.

This is to avoid additional exceptions unintentionally being introduced, for example when a failure starts being thrown because of configuration cache problems alongside the expected failure.

    • -0
    • +3
    ./CustomVersionListerIntegrationTest.groovy
  1. … 81 more files in changeset.
Add @ToBeFixedForInstantExecution to CustomVersionListerIntegrationTest

because of the GenerateGraphTask in ResolveTestFixture that has a Configuration field

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

    • -0
    • +8
    ./CustomVersionListerIntegrationTest.groovy
Annotate tests to account for new reported problems

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

    • -2
    • +0
    ./CustomVersionListerIntegrationTest.groovy
  1. … 48 more files in changeset.
Annotate tests to account for new reported problems

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

    • -1
    • +0
    ./CustomVersionListerIntegrationTest.groovy
  1. … 48 more files in changeset.
Annotate tests to account for new reported problems

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

    • -2
    • +0
    ./CustomVersionListerIntegrationTest.groovy
  1. … 49 more files in changeset.
Annotate tests to account for new reported problems

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

    • -2
    • +0
    ./CustomVersionListerIntegrationTest.groovy
  1. … 49 more files in changeset.
Annotate tests to account for new reported problems

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

    • -2
    • +0
    ./CustomVersionListerIntegrationTest.groovy
  1. … 49 more files in changeset.
@RequiredFeature can be used as a repeated annotation

If used for a single feature, avoid annotation noise by not using the

composite annotation. This also avoids the confusion that the

@RequiredFeature annotation cannot be used independently

(no compile error but does not work).

I made the @RequiredFeatures annotation package-private as it is

only required by the compiler and the runner now.

Signed-off-by: Benjamin Muskalla <bmuskalla@gradle.com>

    • -9
    • +6
    ./CustomVersionListerIntegrationTest.groovy
  1. … 43 more files in changeset.
@RequiredFeature can be used as a repeated annotation

If used for a single feature, avoid annotation noise by not using the

composite annotation. This also avoids the confusion that the

@RequiredFeature annotation cannot be used independently

(no compile error but does not work).

I made the @RequiredFeatures annotation package-private as it is

only required by the compiler and the runner now.

Signed-off-by: Benjamin Muskalla <bmuskalla@gradle.com>

    • -9
    • +6
    ./CustomVersionListerIntegrationTest.groovy
  1. … 43 more files in changeset.
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

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

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

removing most of @IgnoreWithInstantExecution annotations

after fixing the @FailsWithInstantExecution rule

and more ci feedback

also make @IgnoreWithInstantExecution require a reason from a fixed set

and add it to the remaining ignores

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

    • -3
    • +2
    ./CustomVersionListerIntegrationTest.groovy
  1. … 126 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

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

    • -0
    • +5
    ./CustomVersionListerIntegrationTest.groovy
  1. … 93 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

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

    • -0
    • +5
    ./CustomVersionListerIntegrationTest.groovy
  1. … 93 more files in changeset.
Annotate integ tests failing with instant execution in :dependencyManagement

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

    • -0
    • +5
    ./CustomVersionListerIntegrationTest.groovy
  1. … 93 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -3
    • +1
    ./CustomVersionListerIntegrationTest.groovy
  1. … 95 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

    • -3
    • +1
    ./CustomVersionListerIntegrationTest.groovy
  1. … 32 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

    • -3
    • +1
    ./CustomVersionListerIntegrationTest.groovy
  1. … 32 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

    • -3
    • +1
    ./CustomVersionListerIntegrationTest.groovy
  1. … 32 more files in changeset.
spelling: identifier

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

    • -1
    • +1
    ./CustomVersionListerIntegrationTest.groovy
  1. … 2 more files in changeset.
Add more test coverage for version listers

In particular with regards to errors and offline mode.

    • -0
    • +115
    ./CustomVersionListerIntegrationTest.groovy
  1. … 1 more file in changeset.
Add support for custom lister on Maven repositories

So far providing a custom lister was only available on Ivy repositories.

With this change, the capability is now migrated to our internal abstract

repository, which makes it possible to use it in both Maven and Ivy.

It's worth noting that only listing is wired now, and it will be possible

to use component metadata suppliers too with Maven repository in a

subsequent commit.

    • -0
    • +269
    ./CustomVersionListerIntegrationTest.groovy
  1. … 5 more files in changeset.