[CT-3539] [Feature] Input following generic test name is ignored - hides incorrectly configured tests about dbt-core HOT 2 OPEN

Thanks for opening this @d-cole

I see what you are saying that this will use YAML anchors and aliases to re-use a where filter when you run dbt build or dbt test:

models:
  - name: my_model

    my_filter: &where_filter
      where: "id is not null"

    columns:
      - name: id
        tests:
          - not_null: *where_filter

But if the last line is changed to omit the :, then the where filter won't be applied:

          - not_null *where_filter

I'm going to change this to a feature request and label it as "help wanted".

Acceptance criteria

• A test name like not_null something_extra_here raises a warning
• The warning should indicate that "something_extra_here" will be ignored and suggest adding a colon after not_null

from dbt-core.

Acceptance criteria
A test name like not_null something_extra_here raises a warning
The warning should indicate that "something_extra_here" will be ignored and suggest adding a colon after not_null

Sounds good. Thank you @dbeatty10!!

from dbt-core.