aglinxinyuan opened a new issue, #8289: URL: https://github.com/apache/texera/issues/8289
### Task Summary The Models page landed recently and its detail component is the largest uncovered surface in the frontend: | File | Codecov fully-covered | |---|---| | `model-detail.component.ts` | 197/228 | | `model-detail.component.html` | 203/221 | | `admin-settings.component.html` | 204/214 | | `heatmap-scoring.ts` | 50/54 | `model-detail.component.ts` alone has 31 uncovered lines — its tab wiring, the editable description path, the framework/format selects, the version-and-file listing and the side-resize handler are all unexercised. `heatmap-scoring.ts` is a new file. **Three DOM-query traps are worth recording**, since each produces a confusingly red test rather than an obvious one: - `model-detail.component.html` has **two** `<texera-markdown-description>` instances, and `nz-tabs` keeps already-activated panes alive — so `query(By.directive(...))` returns the Model Card's *non-editable* one and a `descriptionChange` emit goes nowhere. Select on `.editable` instead of taking the first match. The same applies to `nz-select`: there are two on the Settings tab plus one on Versions & Files, so they must be indexed. - Opening an `nz-tooltip` instantiates an overlay host carrying `[@zoomBigMotion]`, which throws without an animations module. A new `describe` needs its own TestBed with `NoopAnimationsModule`. - Tooltip content renders into the CDK overlay on `document.body`, not into `fixture.nativeElement`, so assertions must read from `document.body`. Such a describe also needs its own drain of the `assets/` requests `nz-icon` lazily fetches, before `http.verify()`. Also: `dataset-detail.component.spec.ts` has three top-level describes with *different* helper names and render helpers, so appending at the end of the file does not compile. ### Task Type - [x] Testing / QA ### Was this issue authored using generative AI tooling? Generated-by: Claude Code (Opus 5) -- 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]
