kotlin-fork

Files

T

Sergey Igushkin d456ae58b6 Remove usages of com.intellij.* utils from kotlin-build-common, KT-31106

As Gradle may under certain conditions reorder the buildscript
classpath artifacts, we need to ensure that the `kotlin-build-common`
module, which duplicates some of the classes that are shaded and packed
into `kotlin-compiler-embeddable`, does not call `com.intellij.*`
classes.

Replace the `com.intellij.*` utils that were called on the execution
path with our own implementations.

Issue #KT-31106 Fixed

2019-04-24 15:51:13 +03:00

src/test

Remove usages of com.intellij.* utils from kotlin-build-common, KT-31106

2019-04-24 15:51:13 +03:00

build.gradle.kts

Kapt: Fix NPE on JDK 10-11 (KT-26203)

2019-04-11 17:46:19 +03:00

Readme.md

Create Readme.md

2018-02-14 16:27:11 +03:00

Readme.md

Gradle Plugin Integration Tests

This module contains integration tests for libraries/tools/kotlin-gradle-plugin (and the subplugins mentioned there).

How to run

There are three Gradle tasks that run the tests:

Run all tests with the oldest possible Gradle version for each test:
```
./gradlew :kotlin-gradle-plugin-integration-tests:test
```
Run with the new Gradle release, choose only the tests that support this Gradle version:
```
./gradlew :kotlin-gradle-plugin-integration-tests:testAdvanceGradleVersion
```
Run the incremental compilation tests generated from the JPS ones
```
./gradlew :kotlin-gradle-plugin-integration-tests:testFromJps
```

The tests that use the Gradle plugins DSL (PluginsDslIT) also require the Gradle plugin marker artifacts to be installed:

./gradlew -Pdeploy_version=1.2-test :kotlin-gradle-plugin:plugin-marker:install :kotlin-noarg:plugin-marker:install :kotlin-allopen:plugin-marker:install
./gradlew -Pdeploy_version=1.2-test :kotlin-gradle-plugin-integration-tests:test

How to work with the tests

When you create a new test, figure out which Gradle versions it is supposed to run on. Then, when you instantiate a test project, specify one of:

project("someProjectName", GradleVersionRequired.None) or just project("someProjectName") – the test can run on the whole range of the supported Gradle versions;
project("someProjectName", GradleVersionRequired.AtLeast("X.Y")) – the test is supposed to run on Gradle version X.Y and newer (e.g. it tests integration with a Gradle feature that was released in version X.Y);
project("someProjectName", GradleVersionRequired.Exact("X.Y")) – the test is supposed to run only with Gradle version X.Y (e.g. it tests a workaround for that version or records some special behavior that is not reproducible with newer versions).

⚠️ When your tests target multiple Gradle versions, make sure they pass when run with both tasks test and testAdvanceGradleVersion (see above). In the IDE, you can modify a test run configuration to use a Gradle task other than test.

You can check a Gradle version that the test runs with using Project.testGradleVersionAtLeast("X.Y") and Project.testGradleVersionBelow("X.Y").

Since Gradle output layouts differ from version to version, you can access classes and resources output directories using the functions that adapt to the Gradle version that is used for each test:

CompiledProject.kotlinClassesDir() with optional arguments for subproject and source set, and its Java counterpart CompiledProject.javaClassesDir() (note that Gradle versions below 4.0 use the same directory for both)
Project.resourcesDir() (with optional arguments for subproject and source set) for the resources directory;
Project.classesDir(), which is a general way to get the output directory for a specific subproject, source set, and language.

Readme.md Unescape Escape

Gradle Plugin Integration Tests

How to run

How to work with the tests

Readme.md