Allow table name override for custom DBT tests referencing multiple models

[LaurensDeBaets]

Is your feature request related to a problem? Please describe.
When using custom DBT tests that reference multiple models like this:

{{ config(
     severity = 'warn',
     warn_if  = '>0',
     store_failures=true,
     tags="my-test"
) }}

SELECT *
FROM {{ ref("table_X") }}
LEFT JOIN {{ ref("table_Y") }}

The test doesn't show up in the dashboard , supposedly because both the table_name and model_unique_id fields from the elementary_test_results table are null. model_unique_id can be overridden using the override_primary_test_model_id config parameter, however to the best of my knowledge there is no such thing for table name.

Describe the solution you'd like
Either the option to override the table_name or another way to have DBT tests referencing multitple models show up in the dashboard.

Describe alternatives you've considered
A working alternative is to build a new view or table containing the DBT test query, and then making a SELECT * query on that table or view as a test. Downsides of this are that it is not as clean and creates abundant views or tables and code.

Would you be willing to contribute this feature?
Yes!

[NoyaOffer]

Hey @LaurensDeBaets ! Thank you for this, we'll check it out.