Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom test name does not show in report html file #1224

Open
yatsky opened this issue Oct 11, 2023 · 2 comments · May be fixed by #1374
Open

Custom test name does not show in report html file #1224

yatsky opened this issue Oct 11, 2023 · 2 comments · May be fixed by #1374
Labels
Bug Something isn't working Triage 👀

Comments

@yatsky
Copy link

yatsky commented Oct 11, 2023

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 yatsky added Bug Something isn't working Triage 👀 labels Oct 11, 2023
@sharma-vaibhav1
Copy link

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.

@yatsky
Copy link
Author

yatsky commented Jan 5, 2024

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

@yatsky yatsky linked a pull request Jan 16, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Triage 👀
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants