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
The current dbt flowis dbt run then dbt test, but what if tests ran as part of dbt run, where after each model was built, the tests ran. Then we can halt processing models downstream from the failed ones.
Describe alternatives you've considered
No obvious alternatives here.
Additional context
Would be relevant across the board.
Who will this benefit?
Anyone who uses tests and wants to preserve correct models over up-to-date ones
Are you interested in contributing this feature?
Not at this time.
The text was updated successfully, but these errors were encountered:
@friendofasquid I'm all about this! It's very much the goal of #2743. Rather than changing the behavior of the existing run or test tasks, it proposes a new task type that would do just the thing you suggest, as well as seeding seeds, snapshottint snapshots, and so on. That's something I hope to attempt in the next few months.
I'm going to close this as a duplicate in the meantime, but I'm tremendously appreciative of your opening it, as it's good to confirm that this is something people want.
Describe the feature
The current dbt flowis
dbt run
thendbt test
, but what if tests ran as part ofdbt run
, where after each model was built, the tests ran. Then we can halt processing models downstream from the failed ones.Describe alternatives you've considered
No obvious alternatives here.
Additional context
Would be relevant across the board.
Who will this benefit?
Anyone who uses tests and wants to preserve correct models over up-to-date ones
Are you interested in contributing this feature?
Not at this time.
The text was updated successfully, but these errors were encountered: