aglinxinyuan opened a new issue, #7769: URL: https://github.com/apache/texera/issues/7769
### Task Summary A cluster of small amber files sits well below the module average, and three of them have no spec at all: | File | Coverage | |---|---| | `.../coordinator/promisehandlers/DebugCommandHandler.scala` | 33.3% | | `.../coordinator/promisehandlers/ConsoleMessageHandler.scala` | 33.3% | | `.../web/resource/SystemMetadataResource.scala` | **0%** | | `.../worker/promisehandlers/StartHandler.scala` | 73.9% | | `.../worker/promisehandlers/PrepareCheckpointHandler.scala` | 61.9% | | `.../engine/architecture/common/PekkoActorRefMappingService.scala` | 85.7% | All six are reachable with no cluster, no Docker and no network. Four sibling files in the same size range were assessed and should be **left alone**; recording them so nobody re-derives it: - **`PekkoActorService`** — its two uncovered lines are the whole bodies of `sendToSelfOnce` and `ask`, and both have **zero call sites** anywhere (main, test, bench, scripts). Dead code, not a coverage gap. - **`WorkflowMessage`** — `case _ => 200L` is unreachable: the trait is `sealed` with a single subtype in the file, so only `null` reaches the default arm. Its other line is a case-class declaration whose uncovered branches are scalac-generated `equals`/`copy`/`productElement`. - **`RecoveryPayload`** — the classes are already constructed by `AmberMessageEnvelopesSpec`; the remainder is purely scalac-generated members. Nothing hand-written could be deleted to make a new test fail. - **`ComputingUnitWorker`** — the uncovered lines are `main`'s body, and `AmberRuntime.startActorWorker` binds a cluster seed at `:2552` and mutates `AmberConfig.masterNodeAddr`, which is global state in a shared test JVM. `parseArgs` is already fully covered. One measurement note worth knowing: a line with instructions covered but **no branch taken** is reported as *missed*, not *partial*, so some of these files' "missed" counts are branch gaps rather than unexecuted code. Also do not plan coverage on `logger.info`/`logger.debug` bodies here — amber has no `logback-test.xml`, the root logger governs, and CI sets `TEXERA_SERVICE_LOG_LEVEL=WARN`, so those interpolations execute locally but not in the run that produces the reported number. ### 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]
