-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
SAT: unit tests test_state_with_abnormally_large_values
+ add missing future_state_path
#17791
Conversation
NOTE
|
/test connector=connectors/source-surveymonkey
Build PassedTest summary info:
|
/test connector=connectors/source-bigcommerce
Build FailedTest summary info:
|
/test connector=connectors/source-talkdesk-explore
Build FailedTest summary info:
|
/test connector=connectors/source-paystack
Build FailedTest summary info:
|
NOTE
|
I don't expect SAT to pass on alpha connectors are they are also failing on master... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
A question about "The other connector missing future_state_path testing are the following"
- did you audit all the connectors? How did you come up with this list?
A question about: "I don't expect SAT to pass on alpha connectors are they are also failing on master..."
- How did you learn this? I wonder if we should keep a spreadsheet or metabase report about this to help connector developers know what to do if they need to re-publish a connector
@@ -18,7 +18,7 @@ tests: | |||
incremental: | |||
- config_path: "secrets/config.json" | |||
configured_catalog_path: "integration_tests/configured_catalog.json" | |||
# future_state_path: "integration_tests/abnormal_state.json" | |||
future_state_path: "integration_tests/abnormal_state.json" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love to see more tests being enabled!
Quick script parsing the
https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/builds.md |
/publish connector=bases/source-acceptance-test auto-bump-version=false
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=bases/source-acceptance-test auto-bump-version=false
if you have connectors that successfully published but failed definition generation, follow step 4 here |
NOTE
|
/publish connector=bases/source-acceptance-test auto-bump-version=false
if you have connectors that successfully published but failed definition generation, follow step 4 here |
NOTE
|
/publish connector=bases/source-acceptance-test auto-bump-version=false
if you have connectors that successfully published but failed definition generation, follow step 4 here |
NOTE
|
…ng `future_state_path` (airbytehq#17791)
What
Closes #17338
Just a sanity check over our "source should always emit state" testing.
How
test_state_with_abnormally_large_values
to make sure it works as expectedfuture_state_path
toacceptance-test-config.yml
of the following connectors:The other connector missing
future_state_path
testing are the following:It's not possible to check these connector always emit a state when no record is available because their API does not allow querying future data, which is what
test_state_with_abnormally_large_values
is testing.