You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@flink.apache.org by GitBox <gi...@apache.org> on 2026/07/13 14:54:09 UTC
[GH] (flink/master): Workflow run "npm_and_yarn in /flink-runtime-web/web-dashboard for esbuild, @angular-devkit/build-angular - Update #1458838585" is working again!
The GitHub Actions job "npm_and_yarn in /flink-runtime-web/web-dashboard for esbuild, @angular-devkit/build-angular - Update #1458838585" on flink.git/master has succeeded.
Run started by GitHub user dependabot[bot] (triggered by dependabot[bot]).
Head commit for run:
f5bb04d03b34d9ad570fb6656abc53cb966463ac / Purushottam Sinha <ps...@confluent.io>
[FLINK-40035][runtime-web] Add Vitest smoke tests for the web-dashboard
The web-dashboard had no automated tests, leaving lint and the production
build as the only guardrails against breakage during Angular/ng-zorro
upgrades. Add a Vitest-based test setup with smoke-level component specs for
high-traffic views, and run them in CI.
- Wire Vitest via Angular's @angular/build:unit-test builder (the default
test runner in Angular 21; Karma is deprecated). Tests run in jsdom, so no
browser is needed in CI. Add tsconfig.spec.json and src/test-setup.ts with
the jsdom stubs ng-zorro/CDK require (matchMedia, ResizeObserver,
IntersectionObserver).
- Migrate the build and serve targets from
@angular-devkit/build-angular:browser-esbuild to @angular/build:application
and :dev-server, which the unit-test builder requires and which is the
Angular 21 default. Output stays flat under web/ so packaging is unchanged.
Remove the now-unused @angular-devkit/build-angular.
- Add smoke specs covering rendering and basic interactions for the Overview
statistic cards, the Task Manager list, and the Job Exceptions view.
- Add test / test:ci npm scripts and include test:ci in ci-check so the specs
run as part of the existing Maven frontend build.
Generated-by: Claude Code (claude-opus-4-8)
Report URL: https://github.com/apache/flink/actions/runs/29259846739
With regards,
GitHub Actions via GitBox