elementary icon indicating copy to clipboard operation
elementary copied to clipboard

Custom test name does not show in report html file

Open yatsky opened this issue 1 year ago • 3 comments

Describe the bug The Test name column in HTML file does not reflect custom test name set in the yaml config. To Reproduce Steps to reproduce the behavior:

Given the following yaml config

version: 2

sources:
    - name: example_schema
      tables:
        - name: example_table
          meta:
            elementary:
              timestamp_column: "timestamp_column"
          tests:
            - elementary.volume_anomalies:
                name: "example table is stable"
                where_expression: "timestamp_column between dateadd(day, -10, current_date()) and current_date()"
                anomaly_sensitivity: 2
                backfill_days: 7
                days_back: 10

Run dbt test in the console and we get correct output.

08:23:59 1 of 3 START test example table is stable ........................ [RUN]

However, in the final HTML report, the test name is not correctly reflected.

image

Expected behavior The custom test name should be relected in the Test name column in the final HTML file.

Screenshots Attached above.

Environment (please complete the following information):

  • edr Version: 0.11.0
  • dbt package Version: 0.11.1

Additional context See original Slack conversation: https://elementary-community.slack.com/archives/C02CTC89LAX/p1696829659325819

yatsky avatar Oct 11 '23 09:10 yatsky

Hi @oravi @Maayan-s Can we please prioritise this bug fix as it causes confusion in the UI. All similar tests with different names appear the same.

sharma-vaibhav1 avatar Nov 27 '23 14:11 sharma-vaibhav1

Happy new year team. Just checking to see if there's any traction on this? thanks

yatsky avatar Jan 05 '24 03:01 yatsky

Hi @yatsky ! Thanks a lot for this contribution and sorry for the delay in our response. We'll look into it as soon as we can - intuitively it requires verifying on our end that it doesn't break other behaviors and works with previous dbt versions (we support dbt 1.3.0 and above today).

Thanks, Itamar

haritamar avatar May 27 '24 11:05 haritamar