-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update testing structure for dbt Labs testing support - postgres #1721
base: master
Are you sure you want to change the base?
Conversation
After installing dependencies I get the following results from the command
I have a postgres target set up for elementary_tests but the test_dbt_runner failures end up raising this and I'm not sure how to proceed.
or
I'm also unsure where the missing files for the e2e tests should be coming from. Any help getting these tests passing would be appreciated! |
Hi @emmyoop !
As I understand it, I think it makes more sense for you to run the integration tests of the first (which is also done with In any case, really cool initiative and appreciate the effort here. Thanks, |
Resolves: #1700
This only adds support for testing with postgres. Postgres is run inside the GitHub runner and I do not need to worry about getting credentials for the various warehouses set up this way.
To add additional adapter testing support in the future, you will just need to modify
Why Do We Need These Changes
As explained in #1700, by setting up tox as a standard entry-point, the Core development team at dbt Labs can include this package's integration tests (along with other popular dbt packages) as part of our continuous development & delivery of dbt.