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

[md] formatting

Browse Source
This commit is contained in:
Anna Bulenkova 2015-04-15 15:17:45 +02:00
parent a5f41c4640
commit bf9cdff1f3
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
testing_plugins.md
View File

@ -17,11 +17,13 @@ Most of the tests in the IntelliJ IDEA codebase are *model-level functional test
* Most of the tests take a source file or a set of source files as input data, execute a feature, and then compare the output with expected results (which can be specified as another set of source files, as special markup in the input file, or directly in the test code).
The biggest benefit of this test approach is that tests are very stable and require very little maintenance once they have been written, no matter how much the underlying implementation is refactored or rewritten. In a product with 10+ years of lifetime that has gone through a large number of internal refactorings, we find that this benefit greatly outweighs the downsides of slower test execution and more difficult debugging of failures (compared to more isolated unit tests).
The biggest benefit of this test approach is that tests are very stable and require very little maintenance once they have been written, no matter how much the underlying implementation is refactored or rewritten.
In a product with 10+ years of lifetime that has gone through a large number of internal refactorings, we find that this benefit greatly outweighs the downsides of slower test execution and more difficult debugging of failures (compared to more isolated unit tests).
Another consequence of our testing approach is what our test framework does not provide:
* We do not provide a recommended approach to mocking. We have a few tests in our codebase that use JMock, but in general we find it difficult to mock all of the interactions with IntelliJ IDEA components that your plugin class will need to have, and we recommend working with real components instead.
* We do not provide a recommended approach to mocking.
We have a few tests in our codebase that use JMock, but in general we find it difficult to mock all of the interactions with IntelliJ IDEA components that your plugin class will need to have, and we recommend working with real components instead.
* We do not provide a general-purpose framework for Swing UI testing. You can try using tools such as
[FEST](http://fest.easytesting.org/) or
@ -37,9 +39,7 @@ Internally, we use manual testing for testing our Swing UIs.
* [Testing Highlighting](testing_highlighting.html)
## Tutorial
Check out
[this](writing_tests_for_plugins.html)
step-by-step tutorial teaching how to write and run automated tests for your custom language plugin (source code included).
[this step-by-step tutorial](writing_tests_for_plugins.html)
teaching how to write and run automated tests for your custom language plugin (source code included).