So the issue is an underlying DB issue - not a test issue.. What happened was that a view (that had tests on it) was not able to be created since one of the "feeding" tables had a schema issue. The way I found to fix it is to create a macro to test if the "feeding" tables exists or not (upstream to the view's tests). That way we are able get slack alerts about our view's upstream tables. Without that we were not getting alerts because the failure was not a dbt/elementary test failure, but rather a DB issue. Thanks!

By the way, your question about the model failure is in place but we are currently transforming the feeding tables to a separate DB, so we are considering the current view as a source, as it will soon be uploaded to the DB as source.