|
| 1 | +# Test platform |
| 2 | + |
| 3 | +## Windows 10/maxOS/Linux |
| 4 | + |
| 5 | +# Scenarios |
| 6 | + |
| 7 | +## Basic |
| 8 | + 1. Open .\resources\eclipse\simple-app. After the language server is initialized, check the status bar icon is :thumbsup:, and the problems view has two errors. |
| 9 | + 2. Select Foo.java file, invoke `class` code snippet to generate code as below and the problem view error number is reduced to 1. |
| 10 | + |
| 11 | + ```java |
| 12 | + package app; |
| 13 | + |
| 14 | + /** |
| 15 | + * Foo |
| 16 | + */ |
| 17 | + public class Foo { |
| 18 | + |
| 19 | + |
| 20 | + } |
| 21 | + ``` |
| 22 | +3. Click the remain error in the diagnostic window, the code action icon should pop up both on the problems view and the side bar of the editor. Select the code action of `Create method 'call()' in type 'Foo'` to fix the error. |
| 23 | +4. Save all the files, and invoke VSCode command "Java: Force Java compilation". There should be no errors. |
| 24 | +5. Typing the following file of code into the App.main method, the completion should work for File and there should be two errors in the problem view. |
| 25 | + ```java |
| 26 | + File f = new File("demo.txt"); |
| 27 | + ``` |
| 28 | +6. Invoke the context menu command `Source Action...` ==> `Organize Imports`, there should be only one warning remains in the problem view. |
| 29 | + |
| 30 | +## Maven |
| 31 | + 1. Open .\resources\maven\salut. After the language server is initialized, check the status bar icon is :thumbsup:, and the problems views has several warnings but without errors. |
| 32 | + 2. Editing experience is correctly working including diagnostics, code completion and code actions. |
| 33 | + |
| 34 | +## Maven - Multimodule |
| 35 | +1. Open .\resources\maven\multimodule. After the language server is initialized, check the status bar icon is :thumbsup:, and there should be no errors/warning in the problems view. |
| 36 | +2. Open Foo.java file, make sure the editing experience is correctly working including diagnostics, code completion and code action on both modules. |
| 37 | + - module1\Foo.java |
| 38 | + - module2\Foo.java |
| 39 | + |
| 40 | +## Gradle |
| 41 | + 1. Open .\resources\gradle\simple-gradle. After the language server is initialized, check the status bar icon is :thumbsup:, and there should be no errors/problems in the problems view. |
| 42 | + 2. Open Foo.java file, make sure the editing experience is correctly working including diagnostics, code completion and code action |
| 43 | + |
| 44 | +## Maven - Java 11 |
| 45 | +1. Install JDK 11, and change the VSCode java.home to the JDK 11 path. |
| 46 | +2. Open .\resources\maven\salut-java11. After the language server is initialized, check the status bar icon is :thumbsup:, and there should be no errors/problems in the problems view. |
| 47 | +3. Open Bar.java, make sure the editing experience is correctly working including diagnostics, code completion and code action |
| 48 | + |
| 49 | +## Gradle - Java 11 |
| 50 | +1. Install JDK 11. |
| 51 | +2. Open .\resources\gradle\gradle-11. After the language server is initialized, check the status bar icon is :thumbsup:, and there should be no errors/problems in the problems view. |
| 52 | +2. Open Foo.java file, make sure the editing experience is correctly working including diagnostics, code completion and code action. |
| 53 | + |
| 54 | +## Single file |
| 55 | +1. Open/Create an empty folder |
| 56 | +2. Add a new Java file, name it Test.java. Check the language server is initialized, and the status bar icon is :thumbsup: after that. |
| 57 | +3. Type code snippet `class` to generate the class body, type `main` to generate the main methods. |
| 58 | +4. In the Test.java file, make sure the editing experience is correctly working including diagnostics, code completion and code action. |
0 commit comments