aglinxinyuan opened a new pull request, #6077:
URL: https://github.com/apache/texera/pull/6077

   ### What changes were proposed in this PR?
   
   Add unit test coverage for three `workflow-operator` support utilities, 
selected from the Codecov report. No production-code changes.
   
   | File | Codecov before | Missed lines targeted |
   | --- | --- | --- |
   | `TestOperators.scala` | 26.3% | 56 — every desc-factory helper (CSV/JSONL 
scans, hash-join, keyword-search, aggregate + group-by, AsterixDB source, 
python & python-source UDFs); asserts the returned descriptors' fields |
   | `SpecialPhysicalOpFactory.scala` | 0% | 17 — `newSourcePhysicalOp`: 
decoded-port identity derivation, layer-name interpolation (incl. 
dash→underscore), empty input ports, output port + schema propagation, and the 
no-port-id failure |
   | `FileScanUtils.scala` | 62.9% | 11 — the `extract == true` archive branch 
of `createTuplesFromFile`: zip-entry iteration, `__MACOSX` filtering, 
single-string vs per-line attribute paths |
   
   `TestOperators` is itself a shared test-helper factory (in `src/main`) used 
by many specs, but nothing asserted on its output, so its bodies read as 
uncovered. All tests run in-memory or against local temp files / committed test 
resources.
   
   ### Any related issues, documentation, discussions?
   
   Follow-up to the review feedback on #6043: prioritize tests that fill 
uncovered code paths.
   
   ### How was this PR tested?
   
   - `sbt "WorkflowOperator/testOnly *TestOperatorsSpec 
*SpecialPhysicalOpFactorySpec *FileScanUtilsSpec"` — 16 tests, all green
   - `sbt "WorkflowOperator/Test/scalafmtCheck"` and `sbt 
"WorkflowOperator/scalafixAll --check"` — clean
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Opus 4.8 [1M context])
   


-- 
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