Skip to content

ci: add autotest cases and pipeline#1619

Merged
chagong merged 1 commit into
mainfrom
ci-pr-ui-autotest
May 11, 2026
Merged

ci: add autotest cases and pipeline#1619
chagong merged 1 commit into
mainfrom
ci-pr-ui-autotest

Conversation

@wenytang-ms
Copy link
Copy Markdown
Contributor

No description provided.

@wenytang-ms wenytang-ms changed the title ci: add autotest cases ci: add autotest cases and pipeline May 11, 2026
@chagong chagong merged commit 32fdaab into main May 11, 2026
3 checks passed
Copilot AI pushed a commit that referenced this pull request May 11, 2026
Co-authored-by: chagong <831821+chagong@users.noreply.github.com>
chagong added a commit that referenced this pull request May 11, 2026
…9 + @vscode-elements/elements (#1616)

* Migrate webviews from React 16 + react-bootstrap to React 19 + @vscode-elements/elements

- Upgrade React 16.14.0 to React 19.x with react-jsx transform
- Replace deprecated @vscode/webview-ui-toolkit with @vscode-elements/elements (Lit-based)
- Replace react-bootstrap components with native HTML + custom SCSS
- Add custom Bootstrap-equivalent utility classes in vscode.scss
- Add TypeScript declarations for vscode-elements web components
- Migrate all webview entry points to React 19 createRoot API
- Convert class components to functional components
- Update webpack config for React 19 compatibility
- Fix tas-client version compatibility (override to ~0.2.33)

* fix: derive AWT action at render time without mutating shared groups array

* fix: add fallback for --design-unit CSS variable

@vscode-elements/elements does not define --design-unit (was provided
by @vscode/webview-ui-toolkit). Add fallback value of 4 so spacing
utilities (mr-*, ml-*, pt-*, etc.) resolve correctly.

* fix(test-plans): use self-contained Maven fixture for resolve-unknown-type plan (#1617)

The plan previously pointed at redhat-developer/vscode-java's salut Maven fixture, which configures maven-compiler-plugin with <source>1.7</source>/<target>1.7</target>. On the CI runners (which install only JDK 21) this puts the workspace in a state where JDT reports compliance warnings on the pom but skips full semantic analysis on the Java source -- the inserted `Gson gson;` field never produces a `Gson cannot be resolved to a type` diagnostic, so navigateToError can never find the error and applyCodeAction `Resolve unknown type` is unreachable.

Older versions of @vscjava/vscode-autotest masked this failure mode by silently pressing Enter on whatever the first Code Action happened to be; once that fallback was removed upstream the plan started reliably failing in scheduled runs (e.g. actions/runs/25419116469).

Add a minimal self-owned Maven fixture under test-fixtures/maven-resolve-type that explicitly targets JDK 11 (<release>11</release>), matching the JDK installed by the workflow. Locally this brings navigateToError from a 30s timeout to ~8s and the full plan to 6/6 passing.

Co-authored-by: copilot <copilot@local>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: chagong <831821+chagong@users.noreply.github.com>

* ci: add autotest cases (#1619)
Co-authored-by: chagong <831821+chagong@users.noreply.github.com>

---------

Co-authored-by: wenyt <75360946+wenytang-ms@users.noreply.github.com>
Co-authored-by: copilot <copilot@local>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: chagong <831821+chagong@users.noreply.github.com>
@chagong chagong deleted the ci-pr-ui-autotest branch May 11, 2026 06:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants