hxuanyu/intellij-sdk-code-samples
1
0
Fork 0
mirror of https://github.com/JetBrains/intellij-sdk-code-samples.git synced 2025-07-29 17:57:53 +08:00
Code Issues Packages Projects Releases Wiki Activity

tests_prerequisites.md: update according to Gradle workflow

Browse Source
This commit is contained in:
Yann Cébron 2020-04-16 18:03:58 +02:00
parent 15bc819da9
commit 9203a5d78d
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
tutorials/writing_tests_for_plugins/tests_prerequisites.md
View File

@ -6,8 +6,9 @@ title: 1. Tests Prerequisites
This page discusses the steps to configure a plugin project for creating tests. This page discusses the steps to configure a plugin project for creating tests.
## 1.1. Create a Folder for Tests ## 1.1. Create a Folder for Tests
Open the plugin project and under the `src` directory create a separate folder `test`. Open the plugin project, and under the `src` directory create a separate folder `test`.
Under `test`, create the `java` folder for test source code, and the folder `testData` for test resources. Under `test`, create the `java` folder for test source code, and the folder `testData` for test data files and reimport the Gradle project.
```text ```text
└── src └── src
├── main ├── main
@ -17,16 +18,14 @@ Under `test`, create the `java` folder for test source code, and the folder `tes
├── java ├── java
└── testData └── testData
``` ```
Mark the `java` folder as a test source root via the context menu `Mark Directory As` → `Test Source Root`.
Similarly, mark the `testData` folder as a test resource root via the context menu `Mark Directory As` → `Test Resources Root`.
## 1.2. Set the Run Configuration Parameters ## 1.2. Set the Run Configuration Parameters
Because some of the tests use Java files as test data, the tests need to mock up the project SDK. Because some of the tests use Java files as test data, the tests need to mock up the project SDK.
IntelliJ IDEA does everything automatically when the utility class [`LightJavaCodeInsightFixtureTestCase`](upsource:///java/testFramework/src/com/intellij/testFramework/fixtures/LightJavaCodeInsightFixtureTestCase.java) is used as the basis for the tests. IntelliJ IDEA does everything automatically when the utility class [`LightJavaCodeInsightFixtureTestCase`](upsource:///java/testFramework/src/com/intellij/testFramework/fixtures/LightJavaCodeInsightFixtureTestCase.java) is used as the basis for the tests.
The system properties are defined in the `build.gradle` file using the snippet shown below. The system properties are defined in the `build.gradle` file using the snippet shown below.
The "/path/to/community/" is set to the absolute path to the root directory of the local intellij-community source on the machine running the tests. The `/path/to/community/` is set to the absolute path to the root directory of the local intellij-community source on the machine running the tests.
For example, on macOS the "path/to/community/" might be `/Users/<user name>/Documents/<community source root>/` For example, on macOS the `path/to/community/` might be `/Users/<user name>/Documents/<IJ community source root>/`
```groovy ```groovy
test { test {
systemProperty "idea.home.path", "/path/to/community/" systemProperty "idea.home.path", "/path/to/community/"