Skip to content
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 microbatch tests to handle update wherein incremental strategies are always validated #10884

Merged
merged 2 commits into from
Oct 21, 2024

Conversation

QMalcolm
Copy link
Contributor

Resolves N/A

Problem

A test broke because we fixed a bug in dbt-adapters (and the test depended on the bug 🙃)

Solution

Fix the test to work with the fixt dbt-adapters behavior

Checklist

  • I have read the contributing guide and understand what's expected of me.
  • I have run this code in development, and it appears to resolve the stated issue.
  • This PR includes tests, or tests are not required or relevant for this PR.
  • This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX.
  • This PR includes type annotations for new and modified functions.

…es are always validated

dbt-adapters updated the incremental_strategy validation of incremental models such that
the validation now _always_ happens when an incremental model is executed. A test in dbt-core
`TestMicrobatchCustomUserStrategyEnvVarTrueInvalid` was previously set to _expect_ buggy behavior
where an incremental model would succeed on it's "first"/"refresh" run even if it had an invalid
incremental strategy. Thus we needed to update this test in dbt-core to expect the now correct
behavior of incremental model execution time validation
@QMalcolm QMalcolm added the Skip Changelog Skips GHA to check for changelog file label Oct 18, 2024
@QMalcolm QMalcolm requested a review from a team as a code owner October 18, 2024 18:29
@cla-bot cla-bot bot added the cla:yes label Oct 18, 2024
@QMalcolm QMalcolm requested review from ChenyuLInx and aranke October 18, 2024 18:29
Copy link

codecov bot commented Oct 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.13%. Comparing base (a0674db) to head (46b59f0).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #10884      +/-   ##
==========================================
- Coverage   89.21%   89.13%   -0.08%     
==========================================
  Files         183      183              
  Lines       23443    23443              
==========================================
- Hits        20914    20897      -17     
- Misses       2529     2546      +17     
Flag Coverage Δ
integration 86.42% <ø> (-0.15%) ⬇️
unit 62.12% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
Unit Tests 62.12% <ø> (ø)
Integration Tests 86.42% <ø> (-0.15%) ⬇️

@QMalcolm QMalcolm merged commit 7920b0e into main Oct 21, 2024
56 of 57 checks passed
@QMalcolm QMalcolm deleted the qmalcolm--fix-microbatch-test branch October 21, 2024 20:10
QMalcolm added a commit that referenced this pull request Oct 24, 2024
…es are always validated (#10884)

dbt-adapters updated the incremental_strategy validation of incremental models such that
the validation now _always_ happens when an incremental model is executed. A test in dbt-core
`TestMicrobatchCustomUserStrategyEnvVarTrueInvalid` was previously set to _expect_ buggy behavior
where an incremental model would succeed on it's "first"/"refresh" run even if it had an invalid
incremental strategy. Thus we needed to update this test in dbt-core to expect the now correct
behavior of incremental model execution time validation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla:yes Skip Changelog Skips GHA to check for changelog file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants