hxuanyu/intellij-sdk-code-samples
1
0
Fork 0
mirror of https://github.com/JetBrains/intellij-sdk-code-samples.git synced 2025-07-28 01:07:49 +08:00
Code Issues Packages Projects Releases Wiki Activity
intellij-sdk-code-samples/topics/basics/testing_plugins/integration_tests/integration_tests.md
Maxim Kolmakov 4c3104c2e3
Second part of integration tests tutorial: UI (#1432) 
* Integration tests: UI interactions and components

* Fix images

* Add references to the main page

* Update content_updates.md to avoid first section mentioning since there will be second and third.

* Review fixes:
- <control> for elements
- new lines
- link to JCEF

* Review fixes:
- crop image

* Update topics/basics/testing_plugins/integration_tests/integration_tests_ui.md

Co-authored-by: Karol Lewandowski <karol86@gmail.com>

* Update topics/basics/testing_plugins/integration_tests/integration_tests_ui.md

Co-authored-by: Karol Lewandowski <karol86@gmail.com>

* Update topics/basics/testing_plugins/integration_tests/integration_tests_ui.md

Co-authored-by: Karol Lewandowski <karol86@gmail.com>

* Update topics/basics/testing_plugins/integration_tests/integration_tests_ui.md

Co-authored-by: Karol Lewandowski <karol86@gmail.com>

* Update topics/basics/testing_plugins/integration_tests/integration_tests_ui.md

Co-authored-by: Karol Lewandowski <karol86@gmail.com>

* Update topics/basics/testing_plugins/integration_tests/integration_tests_ui.md

Co-authored-by: Karol Lewandowski <karol86@gmail.com>

* Update image

* Make the last test more clear

* Apply formatting

* Add label

* Add general info about keyboard presses.

* Refactor section about attributes

---------

Co-authored-by: Karol Lewandowski <karol86@gmail.com>
Co-authored-by: Yann Cébron <yann.cebron@jetbrains.com>
2025-03-24 13:21:12 +01:00

973 B
Raw Blame History

Integration Tests

Tutorial on how to create UI and functional integration tests

There are several important reasons to create integration tests, including:

  • Testing complex scenarios: Some scenarios, particularly UI interactions, cannot be effectively covered by unit tests alone.
  • Full product testing: Integration tests run against the complete product rather than isolated components. This helps identify issues that unit tests might miss, such as module interaction problems, classpath conflicts, and plugin declaration issues.
  • User story validation: Integration tests typically mirror real user scenarios, ensuring plugin works reliably from start to finish.
  3. API Interaction (will be available soon)