Unit Testing in Beam Blog Post

[svetakvsundhar]

This blog posts details opinionated examples and practices for unit testing in Beam. Examples use the Python SDK.

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• [ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• [ ] Update CHANGES.md with noteworthy changes.
• [ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[svetakvsundhar]

R: @liferoad R: @rszper R: @damccorm cc: https://github.com/surjits254

[github-actions[bot]]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control

[svetakvsundhar]

Thanks for the feedback. To address the code running as intended, I plan to create a colab notebook with the runnable snippets, and link it to the blog post (as well as check it in to the Beam repo). Will create after the holiday.

[damccorm]

SGTM - at that point we may be able to ignore the date related comments anyways and just validate that it does indeed render the blog

[svetakvsundhar]

I've added a colab notebook and tested these examples locally. PTAL, once we have a consensus on the notebook examples, I will update the blog post and address the other comments.

[svetakvsundhar]

Hi @robertwb thanks for taking a look! The blog and the colab notebook are actually currently out of sync so that we could test runnable examples. Once aligned on those, I was going to update the blog. Anyhow, I will take a look at the comments and see where they apply.

[github-actions[bot]]

This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the [email protected] list. Thank you for your contributions.