You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of effort has been made over the past year to include full coverage of testing for the fivetran_utils package to test against all Fivetran dbt packages which reference this package as a dependency. The full coverage feature was achieved within PR #118. This full coverage test essentially runs a dbt compile and dbt run against every single Fivetran dbt package. This is great, and ensures we are testing the packages compile and run with the updates to this package; however, we have found that there are still notable gaps in this design. For example:
We should be able to ensure that when we update a macro it will result in the expected behavior across all destinations
When creating a new macro we should be able to ensure it works as expected and does not conflict with any other macros
We should be able to test basic assertions related to the behavior of the macros and how they should behave in the individual packages.
This feature request is to apply the above tests to the Fivetran Utils package in order to ensure more stable releases and more frequent updates as well.
The text was updated successfully, but these errors were encountered:
Feature Description
A lot of effort has been made over the past year to include full coverage of testing for the fivetran_utils package to test against all Fivetran dbt packages which reference this package as a dependency. The full coverage feature was achieved within PR #118. This full coverage test essentially runs a
dbt compile
anddbt run
against every single Fivetran dbt package. This is great, and ensures we are testing the packages compile and run with the updates to this package; however, we have found that there are still notable gaps in this design. For example:This feature request is to apply the above tests to the Fivetran Utils package in order to ensure more stable releases and more frequent updates as well.
The text was updated successfully, but these errors were encountered: