| name | uitest |
| description | Write, update, run, or debug vscode-java-dependency (Project Manager for Java) UI/E2E tests using AutoTest YAML plans. Use when the user asks for a UI test, E2E test, VS Code UI validation, Java Projects tree/view test, referenced-library test, or autotest plan. |
UI/E2E tests with AutoTest
Use this skill to add or update UI/E2E coverage for vscode-java-dependency (Project Manager for Java).
The repository uses @vscjava/vscode-autotest: YAML plans in test/e2e-plans/*.yaml launch VS Code, install the Extension Pack for Java (vscjava.vscode-java-pack) plus a local VSIX of this extension, execute user-facing actions against the Java Projects view, capture screenshots, and write test-results/<plan>/results.json.
Prerequisites (local)
- Node.js >= 18 and JDK 21+ installed and on
PATH (JDK 21 is required to build the jdtls.ext OSGi bundle).
- Close any running VS Code instance before running a plan locally; a running instance can block AutoTest from launching its own VS Code.
- Workspace fixtures are in-repo — no external clones are needed. Plans reference
../maven (test/maven, a maven-archetype-quickstart project) or ../invisible (test/invisible, an unmanaged-folder project).
Workflow
- Identify the scenario and search
test/e2e-plans/*.yaml for an existing plan that already covers the area (project explorer, view modes, classpath, export jar, new types, file operations, delete, copy paths, refresh, build lifecycle, autorefresh).
- Update the existing plan when possible. Create a new
test/e2e-plans/java-dep-<scenario>.yaml only when no existing plan fits.
- Use stable AutoTest actions and deterministic verifiers. Do not add raw Playwright tests or screenshot-only checks.
