chore(frontend): re-enable spec files that pass under standalone migration

[Yicong-Huang]

What changes were proposed in this PR?

Drop the spec exclusion entries in tsconfig.spec.json and angular.json's test target for the specs that now compile and pass cleanly. Plus a handful of mechanical Jasmine → Vitest cleanups.

Newly running — 7 additional test files / 41 additional tests. Previously-excluded service specs that compile and pass under the standalone-component graph:

• udf-debug.service.spec.ts
• operator-menu.service.spec.ts
• workflow-console.service.spec.ts
• workflow-result-export.service.spec.ts
• workflow-result.service.spec.ts
• operator-reuse-cache-status.service.spec.ts
• workflow-websocket.service.spec.ts

Still excluded — 48 component / service specs whose TestBed setups still need to be ported from the old NgModule (declarations: [...]) shape to the standalone-component (imports: [Standalone]) shape. Comments in tsconfig.spec.json document this; each batch is a follow-up. The list still includes execute-workflow.service.spec.ts, user.service.spec.ts, user-config.service.spec.ts, coeditor-presence.service.spec.ts, download.service.spec.ts, preset.service.spec.ts — these compile but fail at runtime against the new TestBed expectations.

Mechanical cleanups along the way

• 2 xit( → it.skip(
• 4 .toHaveBeenCalledOnceWith( → .toHaveBeenCalledExactlyOnceWith(
• 3 .mockReturnValue() (no-arg) → .mockReturnValue(undefined) (Vitest requires the value)
• One partial-mock as any cast in code-debugger.spec
• done/fail stubs in download / preset specs whose tests are it.skip'd pending async/await rewrites

Local result

Test Files  21 passed | 3 skipped (24)
     Tests  150 passed | 8 skipped | 2 todo (160)

Any related issues, documentation, discussions?

Closes #4864.

How was this PR tested?

yarn run test:ci exits 0 locally; CI exercises the same path.

Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Opus 4.7 (1M context)

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 46.68%. Comparing base (47ef2f5) to head (00ba0d8).

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #4878      +/-   ##
============================================
- Coverage     47.64%   46.68%   -0.97%     
- Complexity     2148     2150       +2     
============================================
  Files           817      843      +26     
  Lines         25975    27322    +1347     
  Branches       2343     2533     +190     
============================================
+ Hits          12377    12756     +379     
- Misses        12849    13791     +942     
- Partials        749      775      +26     

Flag	Coverage Δ
frontend	38.58% <ø> (-6.73%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Yicong-Huang]

The drop of the coverage is expected! This PR enables many existing test cases, and the coverage of those test cases are poor. We can improve them later.

[Copilot]

Pull request overview

This PR updates the frontend Vitest/Angular unit-test configuration to re-enable a subset of previously excluded spec files under the standalone-migration test builder, along with a few mechanical Jasmine→Vitest matcher/skip cleanups in affected specs.

Changes:

• Refines tsconfig.spec.json and angular.json test exclusions from broad globs to a curated list of still-problematic specs.
• Applies small Vitest compatibility edits in several spec files (e.g., xit → it.skip, mockReturnValue(undefined), matcher updates).
• Adds local done/fail stubs in skipped specs to keep TypeScript type-checking happy.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
frontend/src/tsconfig.spec.json	Reworks spec exclusion list and documents remaining standalone/TestBed migration blockers.
frontend/angular.json	Updates unit-test builder exclusion list to mirror the remaining blocked specs.
frontend/src/app/workspace/service/preset/preset.service.spec.ts	Adds done/fail stubs for skipped-test type-checking.
frontend/src/app/dashboard/service/user/download/download.service.spec.ts	Adds done/fail stubs for skipped-test type-checking.
frontend/src/app/workspace/component/workflow-editor/context-menu/context-menu/context-menu.component.spec.ts	Updates mockReturnValue() calls to mockReturnValue(undefined) for Vitest typing.
frontend/src/app/workspace/component/property-editor/operator-property-edit-frame/operator-property-edit-frame.component.spec.ts	Converts xit to it.skip.
frontend/src/app/workspace/component/code-editor-dialog/code-debugger.component.spec.ts	Adjusts a partial mock assignment with an as any cast.
frontend/src/app/dashboard/component/user/user-workflow/user-workflow.component.spec.ts	Updates a commented-out skipped-test marker to it.skip.
frontend/src/app/dashboard/component/user/user-workflow/user-workflow-list-item/user-workflow-list-item.component.spec.ts	Updates spy matcher to toHaveBeenCalledExactlyOnceWith.
frontend/src/app/common/formly/preset-wrapper/preset-wrapper.component.spec.ts	Updates commented-out matcher text to toHaveBeenCalledExactlyOnceWith.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Yicong-Huang]

Copilot caught a real inconsistency in the PR description. Fixed:

• The list of Newly running specs originally included execute-workflow, user-config, and user.service — those are still excluded because they compile but fail at runtime against the new TestBed expectations.
• Updated the body so the Newly running list matches the actual passing set, and the still-excluded list explicitly names those files with the reason.

The exclusion lists in tsconfig.spec.json and angular.json are correct as-is for this PR's scope. Re-enabling those four needs per-spec TestBed updates, which are the follow-up batches.

Thanks for the catch.

[mengw15]

LGTM