Skip to content

[YAML] Basic integration testing framework. #29113

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 12 commits into from
Mar 29, 2024
Merged

Conversation

robertwb
Copy link
Contributor

The tests themselves are defined in yaml as a series of pipelines, possibly with some setup code.

One of the key features of this framework is that if muliple providers vend the same transform each will be tested to ensure they have consistent behavior.


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)

Build python source distribution and wheels
Python tests
Java tests
Go tests

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

The tests themselves are defined in yaml as a series of pipelines, possibly with
some setup code.

One of the key features of this framework is that if multiple providers vend the
same transform each will be tested to ensure they have consistent behavior.
@codecov
Copy link

codecov bot commented Oct 23, 2023

Codecov Report

Attention: Patch coverage is 0% with 111 lines in your changes are missing coverage. Please review.

Project coverage is 38.32%. Comparing base (65c3e8e) to head (772fba2).
Report is 25 commits behind head on master.

❗ Current head 772fba2 differs from pull request most recent head 10e0535. Consider uploading reports for the commit 10e0535 to get more accurate results

Files Patch % Lines
sdks/python/apache_beam/yaml/integration_tests.py 0.00% 102 Missing ⚠️
sdks/python/apache_beam/yaml/yaml_provider.py 0.00% 7 Missing ⚠️
sdks/python/apache_beam/testing/util.py 0.00% 2 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           master   #29113       +/-   ##
===========================================
- Coverage   71.46%   38.32%   -33.14%     
===========================================
  Files         710      687       -23     
  Lines      104795   101794     -3001     
===========================================
- Hits        74887    39017    -35870     
- Misses      28277    61197    +32920     
+ Partials     1631     1580       -51     
Flag Coverage Δ
python 29.93% <0.00%> (-51.34%) ⬇️

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

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

Copy link
Contributor

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.

@github-actions github-actions bot added the stale label Dec 23, 2023
Copy link
Contributor

This pull request has been closed due to lack of activity. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.

@github-actions github-actions bot closed this Dec 31, 2023
@robertwb robertwb reopened this Mar 27, 2024
@robertwb robertwb marked this pull request as ready for review March 27, 2024 19:29
Copy link
Contributor

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

@github-actions github-actions bot removed the stale label Mar 28, 2024
Copy link
Contributor

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

R: @shunping for label python.

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

@robertwb robertwb merged commit f7319a6 into apache:master Mar 29, 2024
72 of 73 checks passed
hjtran pushed a commit to hjtran/beam that referenced this pull request Apr 4, 2024
The tests themselves are defined in yaml as a series of pipelines, possibly with
some setup code.

One of the key features of this framework is that if multiple providers vend the
same transform each will be tested to ensure they have consistent behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants