Search Options

Results per page
Sort
Preferred Languages
Advance

Results 71 - 76 of 76 for GradleRunner (0.31 sec)

  1. platforms/extensibility/test-kit/src/integTest/groovy/org/gradle/testkit/runner/GradleRunnerMechanicalFailureIntegrationTest.groovy

            and:
            def output = OutputScrapingExecutionResult.from(t.message, "")
            def taskHeader = gradleVersion >= GradleVersion.version("4.0") ? "\n> Task :helloWorld" : ":helloWorld"
            // GradleRunner disables FS watching on Windows by passing a command line argument, so the arguments are different for Windows and other operating systems
            // See GradleRunner's Javadoc.
    Registered: Wed Jun 12 18:38:38 UTC 2024
    - Last Modified: Thu Nov 16 22:36:52 UTC 2023
    - 6.6K bytes
    - Viewed (0)
  2. platforms/documentation/docs/src/docs/userguide/core-plugins/java_gradle_plugin.adoc

    It automatically adds the `gradleTestKit()` dependency to the `testImplementation` configuration and generates a plugin classpath manifest file consumed by a `GradleRunner` instance if found.
    Please refer to <<test_kit.adoc#sub:test-kit-automatic-classpath-injection,Automatic classpath injection with the Plugin Development Plugin>> for more on its usage, configuration options and samples.
    
    
    Registered: Wed Jun 12 18:38:38 UTC 2024
    - Last Modified: Mon Nov 27 17:53:42 UTC 2023
    - 6.6K bytes
    - Viewed (0)
  3. platforms/documentation/docs/src/docs/userguide/authoring-builds/plugins/testing_gradle_plugins.adoc

    include::sample[dir="snippets/developingPlugins/testingPlugins/groovy/url-verifier-plugin",files="build.gradle[tags=source-set-config]"]
    ====
    
    Functional tests for Gradle plugins use an instance of `GradleRunner` to execute the build under test.
    `GradleRunner` is an API provided by TestKit, which internally uses the Tooling API to execute the build.
    
    Registered: Wed Jun 12 18:38:38 UTC 2024
    - Last Modified: Mon Mar 18 22:49:20 UTC 2024
    - 16K bytes
    - Viewed (0)
  4. platforms/extensibility/plugin-use/src/integTest/groovy/org/gradle/plugin/use/AlreadyOnClasspathPluginUseIntegrationTest.groovy

                                ${testKitSpec.childProjectBuildScript ?: ""}
                            \"\"\".stripIndent()
    
                            //when:
                            def runner = GradleRunner.create()
                                .withGradleInstallation(new File("${TextUtil.normaliseFileSeparators(distribution.gradleHomeDir.absolutePath)}"))
    Registered: Wed Jun 12 18:38:38 UTC 2024
    - Last Modified: Thu Nov 16 22:36:52 UTC 2023
    - 16.2K bytes
    - Viewed (0)
  5. platforms/documentation/docs/src/docs/userguide/releases/upgrading/upgrading_version_6.adoc

    To avoid problems with these file locks, `<<test_kit#test_kit,TestKit>>` disables file system watching for builds executed on Windows via `GradleRunner`.
    If you'd like to override the default behavior, you can enable file system watching by passing `--watch-fs` to `GradleRunner.withArguments()`.
    
    ==== Removal of the legacy `maven` plugin
    
    The `maven` plugin has been removed.
    You should use the `maven-publish` plugin instead.
    Registered: Wed Jun 12 18:38:38 UTC 2024
    - Last Modified: Mon Apr 01 15:00:23 UTC 2024
    - 44.8K bytes
    - Viewed (0)
  6. platforms/documentation/docs/src/docs/userguide/optimizing-performance/configuration_cache.adoc

    To enable configuration caching in your tests, you can pass the `--configuration-cache` argument to link:{javadocPath}/org/gradle/testkit/runner/GradleRunner.html[GradleRunner] or use one of the other methods described in <<configuration_cache.adoc#config_cache:usage:enable,Enabling the configuration cache>>.
    
    You need to run your tasks twice.
    Once to prime the configuration cache.
    Registered: Wed Jun 12 18:38:38 UTC 2024
    - Last Modified: Fri Mar 29 16:24:12 UTC 2024
    - 71.1K bytes
    - Viewed (0)
Back to top