The GitHub Actions job "Required Checks" on
texera.git/feat/reenable-excluded-specs has succeeded.
Run started by GitHub user Yicong-Huang (triggered by Yicong-Huang).
Head commit for run:
50c4119bdcbe6203ea907daabfa6f70f9a158ffe / github-actions[bot]
<github-actions[bot]@users.noreply.github.com>
chore(frontend): re-enable previously excluded specs that pass under standalone
After the standalone-component migration (PR #4873) and the Vitest
runner switch (PR #4862, now merged), many of the specs that were
excluded from the Vitest run in #4862 compile and pass cleanly.
Removed exclusions for the 24 specs that now pass:
- All previously-excluded service specs that reach the auth/modal
chain (workflow-websocket, execute-workflow, udf-debug,
user-config, operator-menu, workflow-console,
operator-reuse-cache-status, workflow-result-export,
workflow-result, etc.)
- The done-callback specs (workflow-result already rewritten;
download / preset bodies stub `done`/`fail` until #4861 follow-ups)
The remaining 48 component / service specs are still excluded — they
have TestBed setups configured against the old NgModule scope. Each
needs its TestBed `imports`/`providers` adapted to the standalone
graph. Tracked as follow-ups under #4861.
Mechanical fixes applied along the way:
- 2 `xit(` → `it.skip(`
- 4 `.toHaveBeenCalledOnceWith(` → `.toHaveBeenCalledExactlyOnceWith(`
- 3 `.mockReturnValue()` (no arg) → `.mockReturnValue(undefined)`
(Vitest requires the value, Jasmine's `.and.returnValue()` allowed empty)
- One partial-mock `as any` cast on a code-debugger.spec
- `done`/`fail` stubs in download / preset specs whose tests are
`it.skip`'d pending async/await rewrites
Local result: 21 passed / 3 skipped (24 test files); 150 passed / 8
skipped / 2 todo (160 tests). Up from 14 / 109 on the migration
baseline.
Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Report URL: https://github.com/apache/texera/actions/runs/25292994080
With regards,
GitHub Actions via GitBox
