Repository navigation
Add namespace test in destination acceptance test - #10793
Conversation
|
/test connector=connectors/destination-snowflake
|
|
/test connector=connectors/destination-bigquery
|
| @@ -0,0 +1,51 @@ | |||
| [ | |||
| { | |||
| "id": "s1-1", | |||
There was a problem hiding this comment.
nitpick: can these IDs be a little more descriptive (e.g. all_caps) to make them easier to cross-reference? right now if a test fails, it'll just log that case s1-1 failed, and then the developer would need to find this file to understand why.
There was a problem hiding this comment.
Done. I also updated the exception message to ask people to look into the namespace_test_case.json for details.
|
/test connector=connectors/destination-snowflake
|
|
/test connector=connectors/destination-bigquery
|
We don't want to introduce changes that will affect existing connections for now.
|
/test connector=connectors/destination-bigquery-denormalized
|
|
/test connector=connectors/destination-bigquery
|
|
/test connector=connectors/destination-snowflake
|
|
/test connector=connectors/destination-bigquery
|
|
/test connector=connectors/destination-bigquery-denormalized
|
|
/test connector=connectors/destination-bigquery-denormalized
|
|
/test connector=connectors/destination-bigquery-denormalized
|
|
/test connector=connectors/destination-bigquery
|
|
/test connector=connectors/destination-snowflake
|
What
How
Recommended reading order
DestinationAcceptanceTest.javanamespace_test_cases.jsonSnowflakeInternalStagingDestinationAcceptanceTest.java🚨 User Impact 🚨