Since upgrading to 0.18.0, the descriptions in the...
# ask-elementary-ai
c
Since upgrading to 0.18.0, the descriptions in the report are not showing anymore with a "No description is configured for this test" message even for the tests included in dbt but the description column in the elementary table is still filled. How can I fix this issue ?
k
A message from kapa.ai
Based on the knowledge sources provided, I don't see specific information about version 0.18.0 having an issue with test descriptions not showing in the report. However, I can provide some guidance on how to properly configure test descriptions in Elementary Data based on the available information. Test descriptions in Elementary can be added in a few different ways: 1. For tests defined in YAML files, you can add descriptions under the
meta
tag:
Copy code
yaml tests:   - unique:       meta:         description: "This is the test description"
2. For singular tests defined as SQL files, you can add descriptions in the config block:
Copy code
sql {{ config(severity = 'error', tags=["test"], meta = {         "description": "This is the test description"     })}}
If you're seeing "No description is configured for this test" despite having descriptions in your tables, it might be related to how Elementary is retrieving or displaying this information in the newer version. Since you mentioned that the description column in the Elementary table is still filled, you might want to try: 1. Running a full refresh of the Elementary tables:
Copy code
dbt run --select elementary --full-refresh
2. Ensuring your test descriptions are properly formatted in the meta section as shown above 3. Checking if there are any specific configuration changes needed for version 0.18.0 If the issue persists, it might be worth opening an issue on the [Elementary GitHub repository](https://github.com/elementary-data/elementary/issues) as this could be a bug in the newer version. I hope this helps! Let me know if you need further assistance. I'm sorry I couldn't find more specific information about this issue in version 0.18.0 in the knowledge sources provided. I'm sorry I couldn't find more specific information about this issue in version 0.18.0 in the knowledge sources provided.
n
Hey @Charlie! Let me check if this is a bug in 0.18.0.