chore: translate all test plans from Chinese to English

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: wenytang-ms

test-plans/java-basic-editing.yaml

@@ -1,54 +1,54 @@
 # Test Plan: Java Basic Editing (from vscode-java-pack.wiki)
 #
-# 来源: wiki Test-Plan.md "Basic" 场景 (Steps 1-5)
-# 验证: 打开 Eclipse 项目 → 语言服务器就绪 → 代码片段 → Code Action 修复错误
+# Source: wiki Test-Plan.md "Basic" scenario (Steps 1-5)
+# Verify: Open Eclipse project → Language Server ready → Code snippet → Code Action fixes error
 #
-# 前置条件:
-#   - vscode-java 仓库已 clone 到本地
-#   - JDK 已安装且可用
+# Prerequisites:
+#   - vscode-java repository cloned locally
+#   - JDK installed and available
 #
-# 用法: autotest run test-plans/java-basic-editing.yaml
+# Usage: autotest run test-plans/java-basic-editing.yaml
 
-name: "Java Basic Editing — 诊断、代码片段、Code Action"
+name: "Java Basic Editing — Diagnostics, Code Snippets, Code Action"
 description: |
-  对应 wiki Test Plan 的 Basic 场景前 5 步:
-  打开 simple-app Eclipse 项目，验证语言服务器启动，
-  使用 class 代码片段修复 Foo.java，通过 Code Action 补全缺失方法，
-  最终编译无错误。
+  Corresponds to the first 5 steps of the Basic scenario in the wiki Test Plan:
+  Open the simple-app Eclipse project, verify Language Server starts up,
+  use class code snippet to fix Foo.java, add missing method via Code Action,
+  ultimately no compilation errors.
 
 setup:
   extension: "redhat.java"
   extensions:
     - "vscjava.vscode-java-pack"
-  # 如果需要测试扩展开发版本，取消注释:
+  # To test extension dev version, uncomment:
   # extensionPath: "../../vscode-java"
   vscodeVersion: "stable"
   workspace: "../../vscode-java/test/resources/projects/eclipse/simple-app"
-  timeout: 60  # Java LS 启动较慢，需要足够等待时间
+  timeout: 60  # Java LS starts slowly, needs sufficient wait time
 
 steps:
-  # ── Step 1: 打开项目 ──────────────────────────────────────
+  # ── Step 1: Open project ──────────────────────────────────
   - id: "project-loaded"
-    action: "等待 5 秒"
-    verify: "项目文件树可见"
+    action: "wait 5 seconds"
+    verify: "Project file tree is visible"
 
-  # ── Step 2: 语言服务器就绪 + 诊断 ────────────────────────
+  # ── Step 2: Language Server ready + diagnostics ──────────
   # wiki: "After the language server is initialized, check the status bar
   #        icon is 👍, and the problems view has two errors."
   - id: "ls-ready"
     action: "waitForLanguageServer"
-    verify: "状态栏显示 Java 语言服务器已就绪（👍 图标）"
+    verify: "Status bar shows Java Language Server is ready (👍 icon)"
     verifyProblems:
       errors: 2
     timeout: 120
 
-  # ── Step 3: 修复 Foo.java（写入 class 代码骨架）────────────
+  # ── Step 3: Fix Foo.java (write class skeleton) ─────────────
   # wiki: "Select Foo.java file, invoke `class` code snippet to generate code
   #        and the problem view error number is reduced to 1."
-  # 注意: Foo.java 是空文件，使用磁盘修改写入 class 骨架（snippet 在空文件中不稳定）
+  # Note: Foo.java is an empty file, using disk modification to write class skeleton (snippet is unstable in empty files)
   - id: "open-foo"
-    action: "打开文件 Foo.java"
-    verify: "Foo.java 文件已在编辑器中打开"
+    action: "open file Foo.java"
+    verify: "Foo.java file is opened in the editor"
     timeout: 15
 
   - id: "write-class-body"
@@ -59,20 +59,20 @@ steps:
       errors: 1
     timeout: 30
 
-  # ── Step 4: 创建缺失方法 call() ──────────────────────────
+  # ── Step 4: Create missing method call() ─────────────────
   # wiki: "Select 'Create method call() in type Foo' to fix the error."
-  # 直接通过磁盘修改添加 call() 方法（Code Action 在自动化中不稳定）
+  # Directly add call() method via disk modification (Code Action is unstable in automation)
   - id: "add-call-method"
     action: "insertLineInFile src/app/Foo.java 4     public void call() {}\n"
     verifyProblems:
       errors: 0
     timeout: 30
 
-  # ── Step 5: 保存并验证无错误 ─────────────────────────────
+  # ── Step 5: Save and verify no errors ────────────────────
   # wiki: "Save all the files... There should be no errors."
   - id: "save-all"
-    action: "执行命令 File: Save All"
-    verify: "所有文件已保存，编译无错误"
+    action: "run command File: Save All"
+    verify: "All files saved, no compilation errors"
     verifyProblems:
       errors: 0
     timeout: 30

test-plans/java-basic-extended.yaml

@@ -1,21 +1,21 @@
 # Test Plan: Java Basic Editing Extended (from vscode-java-pack.wiki)
 #
-# 来源: wiki Test-Plan.md "Basic" 场景 (Steps 6-9)
-# 验证: 代码补全 → Organize Imports → Rename Symbol → New Java File
+# Source: wiki Test-Plan.md "Basic" scenario (Steps 6-9)
+# Verify: Code completion → Organize Imports → Rename Symbol → New Java File
 #
-# 注意: 此 test plan 假设 Basic steps 1-5 已通过（java-basic-editing.yaml）,
-#       即项目已编译无错误。
+# Note: This test plan assumes Basic steps 1-5 have passed (java-basic-editing.yaml),
+#       i.e. the project compiles without errors.
 #
-# 前置条件:
-#   - vscode-java 仓库已 clone 到本地
-#   - JDK 已安装且可用
+# Prerequisites:
+#   - vscode-java repository cloned locally
+#   - JDK installed and available
 #
-# 用法: autotest run test-plans/java-basic-extended.yaml
+# Usage: autotest run test-plans/java-basic-extended.yaml
 
-name: "Java Basic Extended — 补全、Organize Imports、Rename"
+name: "Java Basic Extended — Completion, Organize Imports, Rename"
 description: |
-  对应 wiki Test Plan 的 Basic 场景 Steps 6-9:
-  验证代码补全、Organize Imports、Rename 功能。
+  Corresponds to Steps 6-9 of the Basic scenario in the wiki Test Plan:
+  Verify code completion, Organize Imports, and Rename functionality.
 
 setup:
   extension: "redhat.java"
@@ -26,24 +26,24 @@ setup:
   timeout: 60
 
 steps:
-  # ── 等待 LS 就绪 ─────────────────────────────────────────
+  # ── Wait for LS ready ───────────────────────────────────────
   - id: "ls-ready"
     action: "waitForLanguageServer"
-    verify: "状态栏显示 Java 语言服务器已就绪"
+    verify: "Status bar shows Java Language Server is ready"
     timeout: 120
 
-  # ── Step 6: 输入 File 代码验证补全 ──────────────────────
+  # ── Step 6: Type File code and verify completion ──────────
   # wiki: "Typing 'File f = new File(\"demo.txt\");' into App.main,
   #        the completion should work for File and there should be
   #        two errors in the problem view."
   - id: "open-app"
-    action: "打开文件 App.java"
-    verify: "App.java 文件已在编辑器中打开"
+    action: "open file App.java"
+    verify: "App.java file is opened in the editor"
     timeout: 10
 
   - id: "goto-main-body"
     action: "goToLine 6"
-    verify: "光标在 main 方法体内"
+    verify: "Cursor is inside the main method body"
 
   - id: "goto-end"
     action: "goToEndOfLine"
@@ -53,7 +53,7 @@ steps:
     verifyEditor:
       contains: "File f = new File"
 
-  # 保存文件让 LS 感知变更（typeInEditor 可能不触发 didChange）
+  # Save the file so LS picks up changes (typeInEditor may not trigger didChange)
   - id: "save-before-organize"
     action: "saveFile"
     verifyProblems:
@@ -63,8 +63,8 @@ steps:
 
   # ── Step 7: Organize Imports ────────────────────────────
   # wiki: "Invoke 'Source Action...' => 'Organize Imports'"
-  # 注意: Organize Imports 对 File 类可能弹出选择对话框（多个候选类），
-  # 这里通过磁盘修改直接添加 import 来验证等效行为。
+  # Note: Organize Imports may pop up a selection dialog for File class (multiple candidates),
+  # here we add the import directly via disk modification to verify equivalent behavior.
   - id: "add-import"
     action: "insertLineInFile src/app/App.java 2 import java.io.File;"
     verifyEditor:
@@ -73,8 +73,8 @@ steps:
   # ── Step 8: Rename Symbol ───────────────────────────────
   # wiki: "Open Foo.java, select the definition of class Foo,
   #        right click and run 'Rename Symbol' to rename it to FooNew."
-  # 注意: Rename 需要通过 Command Palette 触发 F2
+  # Note: Rename needs to be triggered via Command Palette (F2)
   - id: "open-foo-for-rename"
-    action: "打开文件 Foo.java"
-    verify: "Foo.java 文件已在编辑器中打开"
+    action: "open file Foo.java"
+    verify: "Foo.java file is opened in the editor"
     timeout: 10

test-plans/java-debugger.yaml

@@ -1,21 +1,21 @@
 # Test Plan: Debugger for Java (from vscode-java-pack.wiki)
 #
-# 来源: wiki Test-Plan.md "Debugger for Java" 场景
-# 验证: 启动调试 → 断点命中 → 单步调试 → 变量查看 → 程序输出
+# Source: wiki Test-Plan.md "Debugger for Java" scenario
+# Verify: Start debugging → Breakpoint hit → Step through → Variable inspection → Program output
 #
-# 使用 simple-app 项目（有 main 方法的 App.java）
+# Uses simple-app project (App.java with main method)
 #
-# 前置条件:
-#   - vscode-java 仓库已 clone 到本地
-#   - JDK 已安装且可用
+# Prerequisites:
+#   - vscode-java repository cloned locally
+#   - JDK installed and available
 #
-# 用法: autotest run test-plans/java-debugger.yaml
+# Usage: autotest run test-plans/java-debugger.yaml
 
-name: "Java Debugger — 断点调试"
+name: "Java Debugger — Breakpoint Debugging"
 description: |
-  对应 wiki Test Plan 的 Debugger for Java 场景:
-  打开 simple-app 项目，设置断点，启动调试，
-  验证断点命中和程序输出。
+  Corresponds to the Debugger for Java scenario in the wiki Test Plan:
+  Open the simple-app project, set breakpoints, start debugging,
+  verify breakpoint hit and program output.
 
 setup:
   extension: "redhat.java"
@@ -26,38 +26,38 @@ setup:
   timeout: 60
 
 steps:
-  # ── 等待 LS 就绪 ─────────────────────────────────────────
+  # ── Wait for LS ready ───────────────────────────────────────
   - id: "ls-ready"
     action: "waitForLanguageServer"
-    verify: "状态栏显示 Java 语言服务器已就绪"
+    verify: "Status bar shows Java Language Server is ready"
     timeout: 120
 
-  # ── 打开 App.java ────────────────────────────────────────
+  # ── Open App.java ──────────────────────────────────────────
   - id: "open-app"
-    action: "打开文件 App.java"
-    verify: "App.java 文件已在编辑器中打开"
+    action: "open file App.java"
+    verify: "App.java file is opened in the editor"
     timeout: 15
 
-  # ── 设置断点 ─────────────────────────────────────────────
+  # ── Set breakpoint ──────────────────────────────────────────
   # wiki: "verify if the breakpoint is hit"
-  # App.java 第 5 行是 System.out.println("Hello Java");
+  # App.java line 5 is System.out.println("Hello Java");
   - id: "set-breakpoint"
     action: "setBreakpoint 5"
-    verify: "在第 5 行设置了断点"
+    verify: "Breakpoint set on line 5"
 
-  # ── 启动调试 ─────────────────────────────────────────────
+  # ── Start debugging ────────────────────────────────────────
   - id: "start-debug"
     action: "startDebugSession"
-    verify: "调试会话已启动，调试工具栏可见"
+    verify: "Debug session started, debug toolbar is visible"
     timeout: 30
 
-  # ── 验证调试控制台输出 ────────────────────────────────────
+  # ── Verify debug console output ──────────────────────────────
   # wiki: "program output is as expected"
   - id: "wait-for-output"
-    action: "等待 5 秒"
-    verify: "程序运行并输出结果"
+    action: "wait 5 seconds"
+    verify: "Program runs and produces output"
 
-  # ── 停止调试 ─────────────────────────────────────────────
+  # ── Stop debugging ─────────────────────────────────────────
   - id: "stop-debug"
     action: "stopDebugSession"
-    verify: "调试会话已停止"
+    verify: "Debug session stopped"

test-plans/java-dependency-viewer.yaml

@@ -1,19 +1,19 @@
 # Test Plan: Java Dependency Viewer (from vscode-java-pack.wiki)
 #
-# 来源: wiki Test-Plan.md "Java Dependency Viewer" 场景
-# 验证: 依赖视图展示 Sources / JDK Libraries / Maven Dependencies
+# Source: wiki Test-Plan.md "Java Dependency Viewer" scenario
+# Verify: Dependency view shows Sources / JDK Libraries / Maven Dependencies
 #
-# 前置条件:
-#   - vscode-java 仓库已 clone 到本地
-#   - JDK 已安装且可用
-#   - Maven 已安装
+# Prerequisites:
+#   - vscode-java repository cloned locally
+#   - JDK installed and available
+#   - Maven installed
 #
-# 用法: autotest run test-plans/java-dependency-viewer.yaml
+# Usage: autotest run test-plans/java-dependency-viewer.yaml
 
-name: "Java Dependency Viewer — 依赖视图"
+name: "Java Dependency Viewer — Dependency View"
 description: |
-  对应 wiki Test Plan 的 Java Dependency Viewer 场景:
-  打开 Maven 项目，验证依赖视图可以展示 Sources、JDK Libraries、Maven Dependencies。
+  Corresponds to the Java Dependency Viewer scenario in the wiki Test Plan:
+  Open a Maven project, verify the dependency view can show Sources, JDK Libraries, and Maven Dependencies.
 
 setup:
   extension: "redhat.java"
@@ -24,24 +24,24 @@ setup:
   timeout: 90
 
 steps:
-  # ── 等待 LS 就绪 ─────────────────────────────────────────
+  # ── Wait for LS ready ───────────────────────────────────────
   - id: "ls-ready"
     action: "waitForLanguageServer"
-    verify: "状态栏显示 Java 语言服务器已就绪"
+    verify: "Status bar shows Java Language Server is ready"
     timeout: 120
 
-  # ── 打开依赖视图 ─────────────────────────────────────────
+  # ── Open dependency view ───────────────────────────────────
   # wiki: "The dependency explorer can show: Sources, JDK libraries, Maven Dependencies"
   - id: "open-dep-explorer"
     action: "openDependencyExplorer"
-    verify: "Java 依赖视图已打开"
+    verify: "Java dependency view is opened"
 
-  # ── 验证 Sources 节点可见 ────────────────────────────────
+  # ── Verify Sources node is visible ─────────────────────────
   - id: "verify-sources"
-    action: "等待 3 秒"
-    verify: "Sources 节点可见"
+    action: "wait 3 seconds"
+    verify: "Sources node is visible"
 
-  # ── 展开 Sources 查看内容 ────────────────────────────────
+  # ── Expand Sources to view contents ────────────────────────
   - id: "expand-sources"
-    action: "展开 salut 节点"
-    verify: "salut 项目节点已展开，可以看到子节点"
+    action: "expand salut tree item"
+    verify: "salut project node is expanded, child nodes are visible"