Support different versions of dbt in our test matrix #965
Labels
area:testing
Related to testing, like unit tests, integration tests, etc
dbt:test
Primarily related to dbt test command or functionality
epic-assigned
execution:virtualenv
Related to Virtualenv execution environment
Milestone
Context
At the moment, we have:
And we want to introduce dbt to the test matrix.
This would increase significantly the amount of tests being run, without a clear benefit.
Goal
Have one set of integration & unit tests for:
This would reduce the amount of Python versions we are checking against.
Have integration & unit tests for the following combinations:
Acceptance criteria
It may be worth having an independent virtual env for dbt, to avoid conflicts similar to #944.
Another alternative may be to use constraints, as proposed in #965.
Suppose we decide to have separate virtualenvs for Airflow and db. In that case, we will still have to have at least one integration test with dbt and Airflow in the same venv to validate the behaviour of
InvocationMode.DBT_RUNNER
: https://astronomer.github.io/astronomer-cosmos/getting_started/execution-modes.html#invocation-modes.The text was updated successfully, but these errors were encountered: