Based on the knowledge sources, Elementary is designed to include both elementary-specific tests and generic dbt tests in its reports, as long as the setup is correct. If your generic dbt test (even a custom SQL test in the

tests/

directory) is running and results are present in the

elementary_test_results

table, it should appear in the report. However, there are a few common reasons why generic dbt tests might not show up in the Elementary report: 1. Profile and Schema Mismatch: The most frequent issue is a mismatch between the schema or profile used by dbt and the one used by Elementary's CLI (

edr report

). Both must point to the same schema where the

elementary_test_results

table is populated. Double-check that your

profiles.yml

has an

elementary

profile pointing to the correct schema, and that you are not accidentally using different targets or profiles between running

dbt test

and

edr report

[see this discussion](https://slack.com/archives/C02CTC89LAX/p1683764076675589). 2. Test Definition Location: If your generic test is defined in a way that Elementary cannot associate it with a model (for example, if it's a standalone SQL file not linked to a model in your project), it may not be picked up in the report. Tests defined in the

tests/

directory should still be recognized, but ensure they are properly referenced in your dbt project [see this related thread](https://slack.com/archives/C02CTC89LAX/p1717077482316179). 3. Invocation/Run Timing: If you run tests in separate invocations (e.g., running elementary tests and generic dbt tests in different commands), the report may only show results from the latest invocation by default. You can try using the

--days-back

flag with

edr report

to include results from multiple recent runs [see this answer](https://slack.com/archives/C02CTC89LAX/p1704446422070929). 4. Elementary Version or Bug: There have been cases where certain versions of Elementary had bugs that filtered out some test results, especially for custom or less common test types. Upgrading to the latest version may resolve such issues [see this example](https://slack.com/archives/C02CTC89LAX/p1698307907124219). Summary of steps to troubleshoot: - Ensure both

dbt test

and

edr report

use the same target/profile and schema. - Confirm your custom test is properly referenced and appears in

elementary_test_results

. - Try running

edr report --days-back 2

to include more recent test runs. - Make sure you are using an up-to-date version of Elementary. If after these checks your generic dbt test still does not appear in the report, it may be due to a limitation or bug not fully documented in the sources above. In that case, sharing your

edr.log

and

dbt.log

with the Elementary support team is recommended for further debugging. Let me know if you need help checking your configuration or logs!