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

test pages: link tutorial/code samples on all pages

Browse Source
This commit is contained in:
Yann Cébron 2025-04-03 15:26:48 +02:00
parent f390c298de
commit 701f501ecc
6 changed files with 16 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
topics/basics/testing_plugins/light_and_heavy_tests.md
View File

@ -1,9 +1,11 @@
<!-- Copyright 2000-2024 JetBrains s.r.o. and contributors. Use of this source code is governed by the Apache 2.0 license. --> <!-- Copyright 2000-2025 JetBrains s.r.o. and contributors. Use of this source code is governed by the Apache 2.0 license. -->
# Light and Heavy Tests # Light and Heavy Tests
<link-summary>Introduction to light tests reusing a single project for multiple tests, and heavy tests creating a new project for each test.</link-summary> <link-summary>Introduction to light tests reusing a single project for multiple tests, and heavy tests creating a new project for each test.</link-summary>
<include from="testing_plugins.md" element-id="testSamples"/>
<include from="tests_and_fixtures.md" element-id="testFrameworkDependencies"/> <include from="tests_and_fixtures.md" element-id="testFrameworkDependencies"/>
Plugin tests run in a real, rather than mocked, IntelliJ Platform environment and use real implementations for most application and project [services](plugin_services.md). Plugin tests run in a real, rather than mocked, IntelliJ Platform environment and use real implementations for most application and project [services](plugin_services.md).

4
topics/basics/testing_plugins/test_project_and_testdata_directories.md
View File

@ -1,9 +1,11 @@
<!-- Copyright 2000-2023 JetBrains s.r.o. and contributors. Use of this source code is governed by the Apache 2.0 license. --> <!-- Copyright 2000-2025 JetBrains s.r.o. and contributors. Use of this source code is governed by the Apache 2.0 license. -->
# Test Project and Testdata Directories # Test Project and Testdata Directories
<link-summary>Adding test data to test projects used during tests execution.</link-summary> <link-summary>Adding test data to test projects used during tests execution.</link-summary>
<include from="testing_plugins.md" element-id="testSamples"/>
<include from="tests_and_fixtures.md" element-id="testFrameworkDependencies"/> <include from="tests_and_fixtures.md" element-id="testFrameworkDependencies"/>
The test fixture creates a *test project* environment. The test fixture creates a *test project* environment.

4
topics/basics/testing_plugins/testing_highlighting.md
View File

@ -1,9 +1,11 @@
<!-- Copyright 2000-2024 JetBrains s.r.o. and contributors. Use of this source code is governed by the Apache 2.0 license. --> <!-- Copyright 2000-2025 JetBrains s.r.o. and contributors. Use of this source code is governed by the Apache 2.0 license. -->
# Testing Highlighting # Testing Highlighting
<link-summary>Testing highlighting the code highlighted with various APIs.</link-summary> <link-summary>Testing highlighting the code highlighted with various APIs.</link-summary>
<include from="testing_plugins.md" element-id="testSamples"/>
<include from="tests_and_fixtures.md" element-id="testFrameworkDependencies"/> <include from="tests_and_fixtures.md" element-id="testFrameworkDependencies"/>
When writing plugin tests, a common task is testing various kinds of highlighting (inspections, annotators, parser error highlighting, etc.). When writing plugin tests, a common task is testing various kinds of highlighting (inspections, annotators, parser error highlighting, etc.).

3
topics/basics/testing_plugins/testing_plugins.md
View File

@ -36,11 +36,12 @@ Check out [](integration_tests_intro.md) tutorial that guides through setup proc
<snippet id="testSamples"> <snippet id="testSamples">
> Check out [this step-by-step tutorial](writing_tests_for_plugins.md) teaching how to write and run automated tests for your custom language plugin. > Check out [this step-by-step tutorial](writing_tests_for_plugins.md) teaching how to write and run automated tests for your custom language plugin.
>
> Also, code samples > Also, code samples
> [comparing_string_references_inspection](%gh-sdk-samples-master%/comparing_string_references_inspection) > [comparing_string_references_inspection](%gh-sdk-samples-master%/comparing_string_references_inspection)
> and [conditional_operator_intention](%gh-sdk-samples-master%/conditional_operator_intention) demonstrate using tests. > and [conditional_operator_intention](%gh-sdk-samples-master%/conditional_operator_intention) demonstrate using tests.
> >
{style="note"} {style="note" title="Testing Tutorial and Code Samples"}
</snippet> </snippet>

2
topics/basics/testing_plugins/tests_and_fixtures.md
View File

@ -4,6 +4,8 @@
<link-summary>Main approaches for implementing tests.</link-summary> <link-summary>Main approaches for implementing tests.</link-summary>
<include from="testing_plugins.md" element-id="testSamples"/>
The IntelliJ Platform testing infrastructure is not tied to any specific test framework. The IntelliJ Platform testing infrastructure is not tied to any specific test framework.
In fact, the IntelliJ IDEA Team uses [JUnit](https://junit.org), [TestNG](https://testng.org), and [Cucumber](https://cucumber.io/) for testing different parts of the project. In fact, the IntelliJ IDEA Team uses [JUnit](https://junit.org), [TestNG](https://testng.org), and [Cucumber](https://cucumber.io/) for testing different parts of the project.
However, most of the tests are written using JUnit 3. However, most of the tests are written using JUnit 3.

4
topics/basics/testing_plugins/writing_tests.md
View File

@ -1,9 +1,11 @@
<!-- Copyright 2000-2023 JetBrains s.r.o. and contributors. Use of this source code is governed by the Apache 2.0 license. --> <!-- Copyright 2000-2025 JetBrains s.r.o. and contributors. Use of this source code is governed by the Apache 2.0 license. -->
# Writing Tests # Writing Tests
<link-summary>Introduction to implementing tests.</link-summary> <link-summary>Introduction to implementing tests.</link-summary>
<include from="testing_plugins.md" element-id="testSamples"/>
<include from="tests_and_fixtures.md" element-id="testFrameworkDependencies"/> <include from="tests_and_fixtures.md" element-id="testFrameworkDependencies"/>
In most cases, once you have the necessary files copied to the test project and loaded into the in-memory editor, writing the test itself involves invoking your plugin code and has few dependencies on the test framework. In most cases, once you have the necessary files copied to the test project and loaded into the in-memory editor, writing the test itself involves invoking your plugin code and has few dependencies on the test framework.