🧪 Add tests for deidentify_write_stream in spark_streaming.py - #21
Conversation
Adds new mock test functions in `openmed/tests/unit/integrations/test_spark_streaming.py` that cover `deidentify_write_stream`, its fluent configuration chain on `SparkDeidentifyStreamBuilder`, and `write_deidentified_stream`. This bumps coverage for `openmed/integrations/spark_streaming.py` across lines 310-508 without spinning up a real Spark context. Co-authored-by: zrt219 <199104500+zrt219@users.noreply.github.com>
The latest updates on your projects. Learn more about Vercel for GitHub.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
🎯 What: The testing gap in
spark_streaming.pywheredeidentify_write_stream, theSparkDeidentifyStreamBuilderfluent builder, andwrite_deidentified_streamwere entirely untested.📊 Coverage: Mock-based testing was added to test:
deidentify_write_streamfunction returning theSparkDeidentifyStreamBuilder.SparkDeidentifyStreamBuilder..start()and.sink().write_deidentified_stream.✨ Result: Test coverage improved across the file, bringing ~65 lines across the fluent builder under coverage and ensuring robust protection without the overhead of spinning up real mock Spark contexts.
PR created automatically by Jules for task 9811911099087954334 started by @zrt219