[FEATURE] Make navigation to failed test results easier

[FrankTub]

Tell us about the problem you're trying to solve

When helping business users navigate in the re_data UI I believe it would be helpfull to display the dbt test name on the Lineage fingertab similar to what is displayed as the message on the Alert fingertab. In our use case we run multiple tests on the same table and this can be very confusing for business users as to where they need to click in the UI to find the results of their failed test.

They follow the following steps.

• Navigate to the re_data UI, this opens up on the Alert fingertab (1).
• They look for their failed test in the message column and click on it.
• They are navigated to the Lineage tab, to the Tests tab of Lineage.
• They have to chose of which tests they want to see their result, but the test name column does not contain any descriptive name (2). (Note that in this example it is clear since only one failed test is there, but still the naming of these tests is confusing)

(1)

(2)

Describe the solution you’d like

My preferred solution would be that end users can be navigated from the Alert tab directly to the Tests fingertab, they are not interested in the Lineage tab at all. They want to look at why their test failed and they need data for that from the Tests fingertab to understand why.

If that is not possible I would like to have more descriptives names for a test on the Lineage fingertab so that an user can identify on which test to click to get their test results.

Describe the alternative you’ve considered or used

Not a clue how to work around this issue so suggestions are welcome.

[mateuszklimek]

@FrankTub Thanks for pointing this out; I agree with this being a bit confusing and understand it would be good to link to test failures. Let me think a bit how to make it consistent with what happens when you click on Anomalies.

I also wonder about one thing, assuming your business users want to debug mostly failed tests, wouldn't the workflow which starts with the Test tab instead of the Alerts table work for them?

[FrankTub]

@mateuszklimek , my ideal situation would be that I send automatic alerts to end users for their failed tests, then they receive in that mail a direct link to the location where they can find the results of why their test failed and possibly some historical data of that failed test like you display on that tab already.

Haven't taken a look at enabling alerting sufficient to know if anything close to it would work. But that would be the ideal scenario.

I think you are right about the following.

I also wonder about one thing, assuming your business users want to debug mostly failed tests, wouldn't the workflow which starts with the Test tab instead of the Alerts table work for them?

Here it is only hard for end users to understand where they need to click to get their failed test results, since the test_name does not reveal any relevant information to them.

[FrankTub]

@mateuszklimek , just gave it another thought and realized the following.

All I'm trying to do is alert users that some specific tests have failed and I want them to be able to solve it themselves. To do so they need some data. Ideally they would receive a link in the mail directly to the data, or receive the data in the mail itself. I understand that it would be hard to do so, but that would be the ideal scenario.

In our case we host the re_data UI in a S3 bucket in AWS, so we would need a link that we can customize to point to our specific location next to the message in the mail that the test has failed or something.