-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Source Hubspot: add integration tests #35945
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
Hey @maxi297 can you please review this PR? Thanks! |
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 like the coverage the tests provide. My concerns are only about expressiveness of the tests and how well they document the behavior. As such, I don't think I have hard blockers but I would like to get a feeling or how we can improve them (even if we don't take action). Feel free to challenge them and I'll approve after!
...yte-integrations/connectors/source-hubspot/unit_tests/integrations/test_engagements_calls.py
Outdated
Show resolved
Hide resolved
...yte-integrations/connectors/source-hubspot/unit_tests/integrations/test_engagements_calls.py
Show resolved
Hide resolved
assert len(output.errors) == 0 | ||
|
||
@HttpMocker() | ||
def test_given_missing_scopes_error_when_read_then_hault(self, http_mocker: HttpMocker): |
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.
The assertion in this test is not so clear to me. What is hault
? What are we validating here except that the requests were performed?
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.
We're validating that the connector stops the sync and does not continue making requests in an infinite loop or something. I've changed the name of the test.
...yte-integrations/connectors/source-hubspot/unit_tests/integrations/test_engagements_calls.py
Show resolved
Hide resolved
airbyte-integrations/connectors/source-hubspot/unit_tests/integrations/test_owners_archived.py
Show resolved
Hide resolved
airbyte-integrations/connectors/source-hubspot/unit_tests/integrations/test_owners_archived.py
Show resolved
Hide resolved
...integrations/connectors/source-hubspot/unit_tests/integrations/test_web_analytics_streams.py
Show resolved
Hide resolved
...integrations/connectors/source-hubspot/unit_tests/integrations/test_web_analytics_streams.py
Show resolved
Hide resolved
...integrations/connectors/source-hubspot/unit_tests/integrations/test_web_analytics_streams.py
Outdated
Show resolved
Hide resolved
...integrations/connectors/source-hubspot/unit_tests/integrations/test_web_analytics_streams.py
Show resolved
Hide resolved
…m:airbytehq/airbyte into ddavydov/source-hubspot-integration-tests
@maxi297 thanks for the review! I've pushed some updates and replied to your comments, please take a look one more time |
…m:airbytehq/airbyte into ddavydov/source-hubspot-integration-tests
…m:airbytehq/airbyte into ddavydov/source-hubspot-integration-tests
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.
Cool! Thanks for addressing my comments. I think those tests are a great addition to the connector code!
What
The issue: https://github.com/airbytehq/airbyte/issues/35188
How
Cover streams defined as empty in acceptance-test-config.yaml with integration tests