vscode-java-pack/test-plans/java-dependency-viewer.yaml at ec5a5e5eb6aeb708eb246fc6853d77c656eb8085 · 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
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
# Test Plan: Java Dependency Viewer (from vscode-java-pack.wiki)
#
# Source: wiki Test-Plan.md "Java Dependency Viewer" scenario
# Verify: Dependency view displays Sources / JDK Libraries / Maven Dependencies
#
# Prerequisites:
#   - vscode-java repo is cloned locally
#   - JDK is installed and available
#   - Maven is installed
#
# Usage: autotest run test-plans/java-dependency-viewer.yaml

name: "Java Dependency Viewer — Dependency View"
description: |
  Corresponds to the Java Dependency Viewer scenario in the wiki Test Plan:
  Open a Maven project and verify the dependency view displays Sources, JDK Libraries, and Maven Dependencies.

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: "Java workspace has loaded; Explorer shows the project tree and Problems panel is settled"
    # waitForLanguageServer is the authoritative deterministic check — the
    # status bar can still flicker "Java: Searching... 0%" for background
    # indexing right after the LS reports ready, which has historically
    # caused LLM screenshot downgrades. Skip LLM here.
    skipLlmVerify: true
    timeout: 120

  # ── Open dependency view ─────────────────────────────────
  # wiki: "The dependency explorer can show: Sources, JDK libraries, Maven Dependencies"
  # Note: autotest's built-in `openDependencyExplorer` calls a legacy
  # "Java: Focus on Java Dependencies View" command title that doesn't exist
  # in current vscode-java-dependency. Use the actual palette title instead.
  - id: "open-dep-explorer"
    action: "run command Explorer: Focus on Java Projects View"
    verify: "Java Projects view opened in the Explorer side bar"

  - id: "wait-for-tree"
    action: "wait 5 seconds"
    # No `verify:` — passive wait; the next `expandTreeItem` steps assert
    # the tree nodes are present.

  # ── Verify project node ─────────────────────────────────
  - id: "expand-project"
    action: "expandTreeItem salut"
    verify: "salut project node expanded; child nodes visible"

  # ── Verify Maven Dependencies node ──────────────────────
  # Verify Maven Dependencies BEFORE expanding JRE so the node is in viewport
  # (JRE has many children which can push Maven Dependencies out of view).
  - id: "verify-maven-deps"
    action: "expandTreeItem Maven Dependencies"
    verify: "Maven Dependencies node visible and expandable"
    timeout: 15

  # ── Verify JDK Libraries node ───────────────────────────
  # The wiki uses "JDK Libraries" as the category name but the actual
  # tree label rendered by vscode-java-dependency is "JRE System Library".
  # The verify text deliberately accepts either label so the LLM doesn't
  # downgrade on a vocabulary mismatch.
  - id: "verify-jdk"
    action: "expandTreeItem JRE System Library"
    verify: "JDK / JRE system library node is visible under the project in the Java Projects view"