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

   ### Task Summary
   
   `menu.component.html` reports 72 uncovered lines despite an 81-test spec, 
and the reason is a subtlety worth writing down: **calling 
`component.onClickX()` directly does not cover `(click)="onClickX()"`.** 
Coverage for that line lands on the generated listener body, which only runs 
when the element is actually clicked. The existing suite invokes handlers 
directly throughout, so every listener body in the toolbar is unexecuted.
   
   That matters here more than usual. The toolbar is a row of visually 
near-identical icon buttons — close panels, reset panels, generate report, 
reset zoom, auto layout, add a comment — distinguishable only by which handler 
they call. A copy-paste leaving two of them on the same handler is the 
realistic defect, and it is invisible both on screen and to the current tests.
   
   The template is **not** tooling-blocked: `menu.component.spec.ts` does not 
call `TestBed.overrideComponent` and coverage registers normally (232 lines, 
151 hits), so #7458 does not apply.
   
   Remaining after this: the four display switches (`toggleGrid` / 
`toggleRegion` / `toggleNumWorkers` / `toggleStatus`) live inside the 
`#executionSettings` popover, which ng-zorro instantiates into a CDK overlay 
only on open. Reaching them needs the right `NzPopoverDirective` opened under 
`fakeAsync` and the switches queried through `document` rather than the fixture.
   
   Side finding: the reuse-result button is `[disabled]="true || …"`, so its 
`(click)` can never fire in the running app — dead UI, coverable only via 
`debugElement.triggerEventHandler`.
   
   ### 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