aglinxinyuan opened a new pull request, #6076: URL: https://github.com/apache/texera/pull/6076
### What changes were proposed in this PR? Add unit test coverage for the four file-reading scan source **executors**, selected from the Codecov report. No production-code changes. Every test is driven by a local temp file (`file:` URI → `ReadonlyLocalFileDocument`); no live DB/network/S3/Iceberg. | File | Codecov before | Missed lines targeted | | --- | --- | --- | | `ParallelCSVScanSourceOpExec.scala` | 0% | 43 — construct + schema init, `open` byte-range partitioning (both `endOffset` branches + mid-file partial-line skip + header skip), `produceTuple` happy path, short-row null padding, all-null (blank) line discard, `close` | | `JSONLScanSourceOpExec.scala` | 0% | 23 — construct, `produceTuple`, `open` line counting + worker partitioning (both ternary branches), row limit, `close` | | `CSVOldScanSourceOpExec.scala` | 0% | 21 — construct + header-based schema, `open` (header vs no-header start offset), `produceTuple` + limit, `close` null-guard before open | | `ArrowSourceOpExec.scala` | 0% | 30 — construct, `open` success + error-wrapping path, `produceTuple` batch iteration + offset/limit, `close` no-op before open | New specs live in each executor's own package so their `private[...]` constructors are reachable, mirroring the existing `FileScanSourceOpExecSpec` temp-file/URI pattern. ### 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 *ParallelCSVScanSourceOpExecSpec *JSONLScanSourceOpExecSpec *CSVOldScanSourceOpExecSpec *ArrowSourceOpExecSpec"` — 17 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]
