mengw15 opened a new issue, #6746:
URL: https://github.com/apache/texera/issues/6746

   ### Task Summary
   
   `MenuComponent` sits at codecov ~70% (81 uncovered lines) — the toolbar's 
button-behavior, toggle, and version-display logic is largely untested. Extend 
the spec, mocking the injected services. jsdom/Vitest; see 
`frontend/TESTING.md`.
   
   ### Behavior to add
   
   **MenuComponent** 
(`frontend/src/app/workspace/component/menu/menu.component.ts`, codecov ~70% — 
EXTEND)
   
   Inject doubles for the workflow/action services (`WorkflowActionService`, 
`WorkflowWebsocketService`, `ExecuteWorkflowService`, etc. — use `vi.fn()` / 
existing stubs; no real websocket). Cover:
   
   - Run-button state: `getRunButtonBehavior` / `applyRunButtonBehavior` — 
assert the computed behavior (run / pause / resume / kill) for representative 
execution states; `hasOperators` reflects the graph.
   - Toggles: `toggleGrid` / `toggleStatus` / `toggleRegion` / 
`toggleNumWorkers` — each flips its flag and/or calls the corresponding service.
   - Click handlers: `onClickAutoLayout` / `onClickDeleteAllOperators` / 
`onClickCreateNewWorkflow` / `onClickExportWorkflow` / 
`onClickExportExecutionResult` / `onClickGenerateReport` / `onClickResetPanels` 
/ `onClickClosePanels` / `onClickAddCommentBox` — assert each delegates to the 
expected service/emitter.
   - Name editing: `onWorkflowNameChange` / `adjustWorkflowNameWidth` — assert 
the persisted name / width update.
   
   Out of scope: the `registerXxxHandler` subscription wiring and `runWorkflow` 
/ `handleKill` / `handleCheckpoint` execution side-effects if they require a 
live websocket — scope to the pure/delegating branches.
   
   ### Task Type
   
   - [ ] Refactor / Cleanup
   - [ ] DevOps / Deployment / CI
   - [x] Testing / QA
   - [ ] Documentation
   - [ ] Performance
   - [ ] Other
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to