-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[CT-1921] Improve coverage of previous state test #6753
Labels
repo ci/cd
Testing and continuous integration for dbt-core + adapter plugins
tech_debt
Behind-the-scenes changes, with little direct impact on end-user functionality
Comments
github-actions
bot
changed the title
Improve coverage of previous state test
[CT-1921] Improve coverage of previous state test
Jan 26, 2023
jtcohen6
added
repo ci/cd
Testing and continuous integration for dbt-core + adapter plugins
tech_debt
Behind-the-scenes changes, with little direct impact on end-user functionality
Team:Language
labels
Jan 26, 2023
Thanks for opening @gshank! Agree, this would help us catch bugs like: |
2 tasks
5 tasks
6 tasks
This was completed some time ago. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
repo ci/cd
Testing and continuous integration for dbt-core + adapter plugins
tech_debt
Behind-the-scenes changes, with little direct impact on end-user functionality
We attempt to test that manifests created in previous versions of dbt Core will work with the current version when doing a state modified selector, in test_previous_version_state.py. The project used for this comparison does not include all varieties of nodes or node-like objects that have changed, including sources. In addition, there should be a test of a disabled version of every node that can be disabled.
The text was updated successfully, but these errors were encountered: