vscode-java-pack/test-plans/java-extension-pack.yaml at 7166587296f0fcd0147410c56c633c28aaaeed4b · microsoft/vscode-java-pack · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
# Test Plan: Java Extension Pack — Classpath Configuration (from vscode-java-pack.wiki)
#
# Source: wiki Test-Plan.md "Java Extension Pack" scenario
# Verify: Trigger Java: Configure Classpath command → Configuration page appears
#
# Note: Classpath configuration uses webview, current framework has limited support
#       for webview internal interactions, only verifies command can be triggered and page appears.
#
# Prerequisites:
#   - vscode-java repository cloned locally
#   - JDK installed and available
#
# Usage: autotest run test-plans/java-extension-pack.yaml

name: "Java Extension Pack — Classpath Configuration"
description: |
  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"
  extensions:
    - "vscjava.vscode-java-pack"
  vscodeVersion: "stable"
  workspace: "../../vscode-java/test/resources/projects/maven/salut"
  timeout: 90

steps:
  # ── Wait for LS ready ───────────────────────────────────────
  - id: "ls-ready"
    action: "waitForLanguageServer"
    verify: "Status bar shows Java Language Server is ready"
    timeout: 120

  # ── Trigger Classpath configuration command ──────────────────
  # wiki: "Trigger the command 'Java: Configure Classpath'"
  - id: "configure-classpath"
    action: "run command Java: Configure Classpath"
    verify: "Classpath configuration page appears (webview or settings page)"

  - id: "verify-page"
    action: "wait 3 seconds"
    verify: "Configuration page finished loading"