mengw15 opened a new issue, #7364:
URL: https://github.com/apache/texera/issues/7364
### Task Summary
`ResultPanelComponent`'s **template** is at ~45%
(`result-panel.component.html`, 28 uncovered lines) while its class file is
already ~99%. The panel chrome (header actions, per-frame branches) is not
rendered by the spec. Bring the template to full coverage. Vitest/jsdom; see
`frontend/TESTING.md`.
### Behavior to add
Extend `result-panel.component.spec.ts` so each template branch renders,
then run the coverage report and cover the remaining red lines. The uncovered
constructs are `(click)` handlers (e.g. `closePanel()`), interpolated tooltips
(e.g. the close button's `operatorTitle` variant), `*ngFor` lists and `*ngIf`
branches.
Approach:
- `fixture.detectChanges()` after each state change.
- Render the panel in each state it switches on: with and without a selected
`operatorTitle` (both tooltip interpolations), each result-frame type the panel
can show, and empty vs populated tab lists so the `*ngFor` expands.
- Fire the header actions through the DOM (`By.css` query +
`triggerEventHandler("click", …)`) and assert the resulting state / service
call, rather than calling the methods directly.
Assert on rendered text and element presence, never on layout or geometry
(zeros under jsdom).
### 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]
