[ 
https://issues.apache.org/jira/browse/FLINK-40601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated FLINK-40601:
-----------------------------------
    Labels: pull-request-available  (was: )

> Web dashboard: finish Vitest coverage for core services and job-detail drawer
> -----------------------------------------------------------------------------
>
>                 Key: FLINK-40601
>                 URL: https://issues.apache.org/jira/browse/FLINK-40601
>             Project: Flink
>          Issue Type: Technical Debt
>          Components: Runtime / Web Frontend
>            Reporter: Purushottam Sinha
>            Priority: Minor
>              Labels: pull-request-available
>
> FLINK-40117 and FLINK-40600 added Vitest specs for the highest-traffic web 
> dashboard views, but 67 of 102 testable source files 
> (components/services/pipes/directives/guards) still have zero spec coverage, 
> leaving core state and the job-inspection UI unverified against regressions.
> Gaps:
> * No specs for core services: {{job.service.ts}}, {{status.service.ts}}, 
> {{overview.service.ts}}, {{job-manager.service.ts}}, {{config.service.ts}}.
> * The entire job-detail drawer tree is untested: accumulators, backpressure, 
> chart, detail, flamegraph, subtasks, taskmanagers, watermarks (8 files) under 
> {{pages/job/overview/*}}.
> * {{dagre.component.ts}} (job graph), 
> {{job-chart.component.ts}}/{{.service.ts}}, {{flame-graph.component.ts}}, and 
> {{submit.component.ts}} (job submission) have none.
> * Asymmetric coverage: {{task-manager}} logs/stdout/thread-dump/profiler 
> pages have specs, the equivalent {{job-manager}} pages do not.
> * Top-level shells ({{job-detail}}, {{application-detail}}, 
> {{job.component}}, {{application.component}}) are untested.
> We should add specs for the five core services first, then the job-detail 
> drawer tree following the FLINK-40600 pattern, then mirror the 
> {{task-manager}} logs/stdout/thread-dump/profiler specs onto {{job-manager}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to