You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
93.5% lines, 6 missed — and 0 of 8 branches, 5 of 9 functions
The template's branch and function figures are the real gap; its line percentage hides it.
Worth establishing before writing anything, because both guesses turn out to be wrong in instructive ways:
preset.service.ts is live, not another workflow-snapshot.service.ts. It is injected by preset-wrapper.component.ts and operator-property-edit-frame.component.ts, and its user/config endpoint is served by UserConfigResource.scala.
The template is NOT an Template coverage does not register for components whose spec calls TestBed.overrideComponent #7458 case. The existing spec uses imports: [ConsoleFrameComponent, ...] with no overrideComponent, and the coverage map proves bindings execute counted — the *ngFor statement shows 124 hits. This is a partly-untested template, not a lost source map, so the remedy is to extend the existing TestBed rather than append a fresh one.
Traps here:
The settings dropdown's menu is projected into a CDK overlay wired in ngAfterViewInit behind an auditTime(150). The fixture must be created insidefakeAsync — created in a plain beforeEach, the timers escape tick() and the overlay never attaches, so a test asserting on its contents finds zero elements and can be written to "pass" vacuously.
Toggling two switches off at once hides a swap. Asserting timestamp and source independently is what makes an exchange of their [(ngModel)] bindings detectable.
Four uncovered items are unreachable and should be left alone — see below; two of them are production defects, and a test would cement them.
Task Summary
Two small frontend targets, both live and both partly untested:
workspace/service/preset/preset.service.tsworkspace/component/result-panel/console-frame/console-frame.component.htmlThe template's branch and function figures are the real gap; its line percentage hides it.
Worth establishing before writing anything, because both guesses turn out to be wrong in instructive ways:
preset.service.tsis live, not anotherworkflow-snapshot.service.ts. It is injected bypreset-wrapper.component.tsandoperator-property-edit-frame.component.ts, and itsuser/configendpoint is served byUserConfigResource.scala.imports: [ConsoleFrameComponent, ...]with nooverrideComponent, and the coverage map proves bindings execute counted — the*ngForstatement shows 124 hits. This is a partly-untested template, not a lost source map, so the remedy is to extend the existing TestBed rather than append a fresh one.Traps here:
ngAfterViewInitbehind anauditTime(150). The fixture must be created insidefakeAsync— created in a plainbeforeEach, the timers escapetick()and the overlay never attaches, so a test asserting on its contents finds zero elements and can be written to "pass" vacuously.[(ngModel)]bindings detectable.Task Type