java-gradle.yaml

# Test Plan: Gradle Project (from vscode-java-pack.wiki)
#
# Source: wiki Test-Plan.md "Gradle" scenario
# Verify: Open Gradle project → LS ready → no errors → Java file editing experience works
#
# Note: Uses the eclipse.jdt.ls subprojects test project (Gradle 8.5),
#       because vscode-java's simple-gradle uses Gradle 4.10.2 which is incompatible with modern JDKs.
#
# Prerequisites:
#   - eclipse.jdt.ls repo is cloned locally
#   - JDK is installed and available
#
# Usage: autotest run test-plans/java-gradle.yaml

name: "Java Gradle Project — Basic Gradle Project Editing"
description: |
  Corresponds to the Gradle scenario in the wiki Test Plan:
  Open a Gradle 8.5 project, verify the language server starts without errors,
  and Java file editing experience works (diagnostics, completion).

setup:
  extension: "redhat.java"
  extensions:
    - "vscjava.vscode-java-pack"
  vscodeVersion: "stable"
  workspace: "../../eclipse.jdt.ls/org.eclipse.jdt.ls.tests/projects/gradle/subprojects"
  timeout: 180  # Gradle project import can be slow (needs to download Gradle distribution)

steps:
  # ── Step 1: Wait for Language Server ready ──────────────
  # wiki: "check the status bar icon is 👍, and there should be
  #        no errors/problems in the problems view."
  - id: "ls-ready"
    action: "waitForLanguageServer"
    verify: "Gradle workspace has loaded; Problems panel shows no errors"
    verifyProblems:
      errors: 0
    timeout: 300
    skipLlmVerify: true  # waitForLanguageServer is authoritative; LLM only sees the same status bar

  # ── Step 2: Open Foo.java and verify editing experience ─
  # wiki: "Open Foo.java file, make sure the editing experience
  #        is correctly working including diagnostics, code completion
  #        and code action"
  - id: "open-foo"
    action: "open file Test1.java"
    verify: "Test1.java file is opened in the editor"
    timeout: 15

  - id: "verify-completion"
    action: "triggerCompletionAt endOfMethod"
    verifyCompletion:
      notEmpty: true
    waitBefore: 3
    # No `verify:` — the on-screen completion menu can lag behind the
    # internal completion API on slower CI runners (screenshot may capture
    # the "Loading..." indicator while the items are already in the list).
    # Deterministic verifyCompletion above is authoritative.

  # Verify the editor can type and save normally
  - id: "goto-line"
    action: "goToLine 2"
    verify: "Cursor moved to line 2"

  - id: "goto-end"
    action: "goToEndOfLine"

  - id: "type-comment"
    action: "typeInEditor // gradle test marker"
    verifyEditor:
      contains: "// gradle test marker"

  - id: "save-file"
    action: "saveFile"
    verify: "File saved"