tests: Add new options to OpenLineage test operator#67195
Merged
Conversation
afa9b1a to
f86a3ee
Compare
mobuchowski
approved these changes
May 20, 2026
Contributor
mobuchowski
left a comment
There was a problem hiding this comment.
Thanks for improving the testing environment!
f86a3ee to
07b7fca
Compare
Collaborator
Author
|
Test failures are unrelated, from main, all from |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some changes to the operator used in system tests only !
Added possibility to assert lack of event, count of events (exact, >= and <=), added ability to specify optional fields and fields that need to be absent. Fast_fail mode is no longer default, we'll see errors for all events. Added a way to compare multiple actual events (added way to sort them) against exact list of expected events - useful for mapped tasks.
Adjusted operators to take advantage of those new changes (and some recent OL changes, like inlet/outlet translation), adjusted templates as well.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.