unit test config

[MichelleArk]

resolves #8294
docs dbt-labs/docs.getdbt.com/#

Problem

Solution

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/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

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

[codecov]

Codecov Report

Patch coverage: 91.93% and project coverage change: +10.63% 🎉

Comparison is base (1e64f94) 76.09% compared to head (90908db) 86.72%.
Report is 17 commits behind head on unit_testing_feature_branch.

Additional details and impacted files

@@                       Coverage Diff                        @@
##           unit_testing_feature_branch    #8565       +/-   ##
================================================================
+ Coverage                        76.09%   86.72%   +10.63%     
================================================================
  Files                              176      176               
  Lines                            25962    26002       +40     
================================================================
+ Hits                             19755    22551     +2796     
+ Misses                            6207     3451     -2756     

Flag	Coverage Δ
integration	83.62% <90.32%> (+7.53%)	⬆️
unit	64.98% <91.93%> (?)

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

Files Changed	Coverage Δ
core/dbt/config/runtime.py	96.23% <ø> (+3.22%)	⬆️
core/dbt/contracts/graph/nodes.py	96.01% <66.66%> (+7.76%)	⬆️
core/dbt/context/context_config.py	93.84% <75.00%> (+8.50%)	⬆️
core/dbt/parser/unit_tests.py	92.92% <95.34%> (+3.77%)	⬆️
core/dbt/config/project.py	97.40% <100.00%> (+5.27%)	⬆️
core/dbt/context/providers.py	89.52% <100.00%> (+7.89%)	⬆️
core/dbt/contracts/graph/model_config.py	92.20% <100.00%> (+6.33%)	⬆️
core/dbt/contracts/graph/unparsed.py	93.69% <100.00%> (+2.90%)	⬆️
core/dbt/contracts/project.py	97.19% <100.00%> (+2.93%)	⬆️

... and 109 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[MichelleArk]

I'm seeing the same mypy failure on the unit_testing_feature_branch branch: https://github.com/dbt-labs/dbt-core/actions/runs/6111537160/job/16586993751?pr=8411

core/dbt/context/providers.py:1507: error: Argument 1 to "contextmember" has incompatible type "Callable[[UnitTestContext, str, Optional[str]], str]"; expected "Optional[str]"  [arg-type]

@gshank - any idea what the cause is? I think we could review this PR independently and look to resolve the mypy issue in a follow-up

[gshank]

That mypy error for contextmember was also seen in a mypy pr that Quigley did. Let me merge main into the feature branch...

[gshank]

Oh, I think '@contextmember' needs to be changed to '@contextmember()'

[gshank]

Code looks good. I suspect we'd get schema changes if we ran the script to build it though. We don't have any artifact tests for unit tests, which is why there are no test failures.

[MichelleArk]

I suspect we'd get schema changes if we ran the script to build it though.

good point! I updated manifest/v11.json in this commit so we can keep track of where the changes were necessary but won't backfill the artifact tests as this PR is already getting pretty big.

[MichelleArk]

@dbt-labs/cloud-artifacts - these changes going onto a feature branch so don't need review quite yet as they will not be released until the feature branch is merged (which will tag the CA team for review at that point)

[FishtownBuildBot]

Opened a new issue in dbt-labs/docs.getdbt.com: dbt-labs/docs.getdbt.com#4062