[bug] [1.3.2] tests on sources do not render

[push2prod]

because sources are not natively rendered as models(only by using the experimental feature) i think tests on sources do not render as well.
I tried rendering the sources as dummy operators and trying the AFTER_ALL test behavior but nothing seemed to work.
it would be very convenient to test sources right before running to avoid any problems with dbt pipelines and would greatly appreciate a patch.

we're using local mode with manifest file without any selectors with airflow 2.5.2(if it matters).

[dosubot]

Hey @push2prod, great to see you around again! Hope you're doing well.

Thank you for bringing this to our attention. It seems like you're encountering an issue with tests on sources not rendering when using Cosmos with the DBT Manifest File method.

From the context provided, Cosmos uses multiple methods to render tests on sources, and one of them is loading from a DBT Manifest File. This method directly loads the DBT graph from the manifest file. However, it seems like this method might not be working as expected in your case.

The process Cosmos follows to render tests on sources when using the DBT Manifest File method involves several steps, including loading the manifest file, parsing it to extract nodes, sources, and exposures, filtering nodes based on the selection and exclusion criteria, and updating nodes with test information.

If the tests on sources are not rendering, it could be due to a variety of reasons. Here are a few things you could check:

1. Manifest Availability: Ensure that the manifest file is available and the path is correctly specified in the project configuration. If the manifest file is not available, Cosmos will raise a CosmosLoadDbtException.

2. Execution Path: Make sure that the execution configuration's project path is set. If not, Cosmos will raise a CosmosLoadDbtException.

3. Selector Support: Cosmos does not support selectors when loading dbt projects using the DBT Manifest File method. If a selector is provided in the RenderConfig, Cosmos will raise a CosmosLoadDbtException.

4. Node Filtering: Check the selection and exclusion criteria specified in the RenderConfig. Cosmos filters nodes based on these criteria. If the tests on sources are not included in the selection or are excluded, they will not be rendered.

5. Test Information: Cosmos updates nodes with test information by marking nodes as having tests if they are dependencies of test nodes. Ensure that the tests on sources are correctly defined as dependencies of the relevant nodes.

If you've checked all of these and the issue persists, it would be helpful if you could provide more information about your setup and the exact steps you're following. This will help us better understand the issue and find a suitable solution.

For reference, you can find more details about the DBT Manifest File method and the process Cosmos follows to render tests on sources in the cosmos/dbt/graph.py file and the tests/dbt/test_graph.py file.

Sources

• tests/dbt/test_graph.py
• cosmos/dbt/graph.py

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

[tatiana]

@push2prod Please, could you share a reproducible example of DAG of what you tried to do, what you saw, and confirm if you'd like to see the tests bundled in task groups, together with the sources, or rendered by the end of the TaskGroup/DAG?