-
Notifications
You must be signed in to change notification settings - Fork 179
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
Remove simple snapshot tests. #158
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
51 changes: 0 additions & 51 deletions
51
...ntegration/simple_snapshot_test/check-snapshots-expected/check_snapshots_test_current.sql
This file was deleted.
Oops, something went wrong.
16 changes: 0 additions & 16 deletions
16
...s/integration/simple_snapshot_test/check-snapshots-query-tag-expected/check_query_tag.sql
This file was deleted.
Oops, something went wrong.
33 changes: 0 additions & 33 deletions
33
tests/integration/simple_snapshot_test/check-snapshots/check_cols_cycle.sql
This file was deleted.
Oops, something went wrong.
18 changes: 0 additions & 18 deletions
18
tests/integration/simple_snapshot_test/custom-snapshot-macros/custom.sql
This file was deleted.
Oops, something went wrong.
12 changes: 0 additions & 12 deletions
12
tests/integration/simple_snapshot_test/invalidate_snowflake.sql
This file was deleted.
Oops, something went wrong.
85 changes: 0 additions & 85 deletions
85
tests/integration/simple_snapshot_test/macros/test_no_overlaps.sql
This file was deleted.
Oops, something went wrong.
Empty file.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, ok, this is concerning!
I took a deeper dive in, and I see that the snapshots are always running with
where TRUE
as theirrow_changed_expr
here. That's not right! Forcheck
-strategy snasphots, thecolumn_added
variable should only returntrue
if a new column is added to the snapshot—which isn't ever true for these failing snapshots.I took a quick look, and the last PR to touch this code was indeed merged 12 days ago: dbt-labs/dbt-core#4893
We've got a lead, gumshoe!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updates:
Not a substitute for the longer-term work you propose above, which is absolutely still what we should do:
test/integration/simple_snapshot_test
)