Hey, Can we define severity for elementary tests in module level, without affecting dbt originated tests serverity? Current

severity

field is being used for both dbt tests as well as elementary tests Thank you for your guidance

Hey Fayiz! 🙂 The

severity

configuration is per test, so it shouldn't affect different tests. Can you explain what you want to achieve in your project? We'll be happy to help figure it out.

@Noya Offer we have a lot of elementary tests configured for different project. Since we did not override severity, the value severity is error. In earlier elementary version(0.12.1), there was a bug such that even if elementary models are failing , downstream models were not being skipped. It got resolved in 0.16.1. Now suddenly all downstream models are being skipped. So team is trying to find out a way to define severity of elementary tests at module level, but it should not affect dbt originated tests

Thanks for the clarification, understood! 🙂 Unfortunately, in

dbt_project.yml

, module-level changes do not provide the option for more detailed configurations, such as using tags or filtering by package. There's a different solution you can use - since all elementary tests have the

elementary-test

tag by default, you can exclude them when running

dbt build

and the

dbt test

them seperately. Would that help?