[derrickaw]

Fixes #37980 and some minor typos.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.81%. Comparing base (76f6e6d) to head (9cd5926).
⚠️ Report is 394 commits behind head on master.

Additional details and impacted files

@@              Coverage Diff              @@
##             master   #40617       +/-   ##
=============================================
+ Coverage     56.16%   79.81%   +23.64%     
=============================================
  Files          1124      494      -630     
  Lines        178336    83581    -94755     
  Branches       1489        0     -1489     
=============================================
- Hits         100170    66710    -33460     
+ Misses        75645    16871    -58774     
+ Partials       2521        0     -2521     

Flag	Coverage Δ
go	?
java	?
python	79.81% <ø> (+0.25%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[derrickaw]

/gemini review

[github-actions]

📋 Review Summary

This PR updates the Beam YAML testing documentation to explicitly note that both --tests and --test CLI flags are supported, fixes minor typos in the documentation, and expands unit test coverage in main_test.py to verify argument parsing and test execution for both flag variants.

🔍 General Feedback

• The unit test additions in sdks/python/apache_beam/yaml/main_test.py cleanly validate both --tests and --test flags via _parse_arguments and run_tests.
• Documentation updates and typo fixes in website/www/site/content/en/documentation/sdks/yaml-testing.md are clear and accurate.

---

💡 Tip: Comment /gemini review on this pull request to trigger a new Gemini code review.

[github-actions]

Assigning reviewers:

R: @chamikaramj for label yaml.
Backup reviewer: Abacn (if the main reviewer is unresponsive, you can escalate to them by tagging their username)

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[damccorm]

Why do we have 2 different ways of doing this? Could you add some context?

[derrickaw]

1. Originally --test was added.
2. Then docs were added stating --tests was to be used.
3. Another person added --tests and kept the backward compatible --test.
4. This PR completes the cycle with improved testing for both flags and update documentation.

[damccorm]

Ok - I think the alias is fine (it probably would've been better to just update the docs, but that ship has sailed). But instead of alluding to both in our docs, lets just pick one and make sure all of our docs use that. I don't care which one we choose, but I think mentioning both (or switching back and forth) will just confuse users and lead them to wonder which one they should choose.

Keeping the main_test.py change is fine

[derrickaw]

Ok removed the --test change. Thanks

[chamikaramj]

waiting on author