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-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"

test-plans/java-extension-pack.yaml

@@ -1,21 +1,21 @@
 # Test Plan: Java Extension Pack — Classpath Configuration (from vscode-java-pack.wiki)
 #
-# 来源: wiki Test-Plan.md "Java Extension Pack" 场景
-# 验证: 触发 Java: Configure Classpath 命令 → 配置页面出现
+# Source: wiki Test-Plan.md "Java Extension Pack" scenario
+# Verify: Trigger Java: Configure Classpath command → Configuration page appears
 #
-# 注意: Classpath 配置使用 webview，当前框架对 webview 内部交互支持有限，
-#       仅验证命令可触发和页面出现。
+# Note: Classpath configuration uses webview, current framework has limited support
+#       for webview internal interactions, only verifies command can be triggered and page appears.
 #
-# 前置条件:
-#   - vscode-java 仓库已 clone 到本地
-#   - JDK 已安装且可用
+# Prerequisites:
+#   - vscode-java repository cloned locally
+#   - JDK installed and available
 #
-# 用法: autotest run test-plans/java-extension-pack.yaml
+# Usage: autotest run test-plans/java-extension-pack.yaml
 
-name: "Java Extension Pack — Classpath 配置"
+name: "Java Extension Pack — Classpath Configuration"
 description: |
-  对应 wiki Test Plan 的 Java Extension Pack 场景:
-  触发 Java: Configure Classpath 命令，验证配置页面出现。
+  Corresponds to the Java Extension Pack scenario in the wiki Test Plan:
+  Trigger Java: Configure Classpath command, verify the configuration page appears.
 
 setup:
   extension: "redhat.java"
@@ -26,18 +26,18 @@ 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
 
-  # ── 触发 Classpath 配置命令 ──────────────────────────────
+  # ── Trigger Classpath configuration command ──────────────────
   # wiki: "Trigger the command 'Java: Configure Classpath'"
   - id: "configure-classpath"
-    action: "执行命令 Java: Configure Classpath"
-    verify: "Classpath 配置页面出现（webview 或 settings 页面）"
+    action: "run command Java: Configure Classpath"
+    verify: "Classpath configuration page appears (webview or settings page)"
 
   - id: "verify-page"
-    action: "等待 3 秒"
-    verify: "配置页面加载完成"
+    action: "wait 3 seconds"
+    verify: "Configuration page finished loading"

test-plans/java-fresh-import.yaml

@@ -1,20 +1,20 @@
 # Test Plan: Fresh Import — Spring Petclinic (from vscode-java-pack.wiki)
 #
-# 来源: wiki Test-Plan.md "Fresh import" 场景
-# 验证: 克隆并打开 Spring Petclinic → LS 就绪 → 补全正常
+# Source: wiki Test-Plan.md "Fresh import" scenario
+# Verify: Clone and open Spring Petclinic → LS ready → Completion works
 #
-# 前置条件:
-#   - JDK 已安装且可用
-#   - Maven 已安装
-#   - Git 已安装（用于自动 clone）
+# Prerequisites:
+#   - JDK installed and available
+#   - Maven installed
+#   - Git installed (for automatic clone)
 #
-# 用法: autotest run test-plans/java-fresh-import.yaml
+# Usage: autotest run test-plans/java-fresh-import.yaml
 
 name: "Java Fresh Import — Spring Petclinic"
 description: |
-  对应 wiki Test Plan 的 Fresh Import 场景:
-  自动 clone Spring Petclinic 项目，
-  验证语言服务器正常启动，基本补全功能正常。
+  Corresponds to the Fresh Import scenario in the wiki Test Plan:
+  Automatically clone the Spring Petclinic project,
+  verify Language Server starts normally, basic completion works.
 
 setup:
   extension: "redhat.java"
@@ -25,25 +25,25 @@ setup:
     - url: "https://github.com/spring-projects/spring-petclinic"
       path: "../../spring-petclinic"
   workspace: "../../spring-petclinic"
-  timeout: 300  # 大型 Maven 项目导入可能很慢
+  timeout: 300  # Large Maven project import can be slow
 
 steps:
-  # ── 等待 LS 就绪 ─────────────────────────────────────────
+  # ── Wait for LS ready ───────────────────────────────────────
   # wiki: "Check LS status bar is 👍"
   - id: "ls-ready"
     action: "waitForLanguageServer"
-    verify: "状态栏显示 Java 语言服务器已就绪"
+    verify: "Status bar shows Java Language Server is ready"
     timeout: 300
 
-  # ── 验证补全 ─────────────────────────────────────────────
+  # ── Verify completion ───────────────────────────────────────
   # wiki: "basic language features such as completion works"
   - id: "open-main-class"
-    action: "打开文件 PetClinicApplication.java"
-    verify: "PetClinicApplication.java 已打开"
+    action: "open file PetClinicApplication.java"
+    verify: "PetClinicApplication.java is opened"
     timeout: 15
 
   - id: "verify-completion"
     action: "triggerCompletion"
-    verify: "代码补全正常工作"
+    verify: "Code completion works correctly"
     verifyCompletion:
       notEmpty: true