[CT-2911] [Epic] Unit testing dbt models

[gshank]

See discussion #8275

[P0]

Preview Give feedback

1. [CT-2916] Use a distinct flavor of Manifest, such as UnitTestManifest instead of base Manifest #8289
   +0
2. [CT-3176] [spike] infer fixture data types for unit testing #8757
   enhancement user docs +2
   
3. [CT-2915] Update unit testing POC branch for merging #8287
   +0
   
4. [CT-2921] Create special unit testing Config object #8294
   +0
   
5. [CT-2922] Produce unit testing artifacts for metadata about unit testing #8295
   +0
   
6. [CT-2923] Speed up unit test parsing by some partial parsing equivalent #8296
   +0
   
7. [CT-2996] Add ability to select a single unit test #8421
   +0
   
8. [CT-3043] Add more functional tests for unit test selection and artifact generation #8512
   +0
   
9. [CT-3110] [Implementation] Support a configurable format: csv attribute on a given input and expect fixtures in unit tests #8626
   +0
   
10. [CT-2917] Add ability to use csv file fixtures for inputs/expected in addition to inline yaml dict/csv #8290
    enhancement user docs +2
    
11. [CT-2997] Ability to test incremental models #8422
    +0
    
12. [CT-3146] [Implementation] updating the unit-tests block (to start with test name instead of model) #8698
    user docs +1
    
13. [CT-3122] [spike] explore testing command options to understand technical complexities and determine best option #8651
    user docs +1
    
14. [CT-3046] Enable use of state:modified for detecting changed unit tests #8517
    +0
    
15. [CT-3078] Improve diff displayed in stdout when a test fails #8558
    user docs +1
    
16. [CT-3038] Support input sources, create test cases #8507
    enhancement +1
    
17. [CT-3370] [implementation] ensure dbt retry works with unit tests #9053
    retry user docs +2
    
18. [CT-3123] Make seed inputs optional for unit tests #8652
    enhancement user docs +2
    
19. [CT-3369] [implementation] new test types for unit tests and data tests in dbt test command #9052
    user docs +1
    
20. [CT-2913] Run unit tests in packages that are not the root package #8285
    +0
    
21. [CT-3147] [Implementation] update config block names for data tests and unit tests #8699
    Impact: Exp user docs +2
    
22. [CT-3380] [Implementation] Include file-based fixtures in parsed files during partial parsing #9067
    bug pre-release user docs +3
    
23. [CT-3308] adjust dbt build to run in dag order -> unit tests, model materialization, data tests #8979
    enhancement user docs +2
    
24. [CT-3412] Run unit tests before models in build command #9128
    +0
    
25. [CT-3195] [spike+] unit testing versioned models #8799
    enhancement user docs +2
    
26. [CT-3291] [Feature] unit test models that depend on external nodes #8944
    enhancement +1
    
27. [CT-3039] Ensure that list command works for unit_tests and has reasonable output #8508
    +0
    
28. [CT-3099] Commands & configs naming changes: expansion of dbt testing coverage #8606
    Impact: CA Impact: Exp user docs +3

[beta bugs done]

Preview Give feedback

1. [CT-3329] [Bug] Unit testing errors with long CTE name given reasonable test name length #9015
   bug postgres unit tests +3
   
2. don't require double quotes around numbers in unit testing yml dbt-snowflake#891
   bug unit tests +2
3. [Bug] Change GenericExceptionOnRun to have node_info #9557
   backport 1.7.latest bug pre-release unit tests +4
   
4. case insensitive column names for unit test YML #9467
   High Severity bug case_sensitivity pre-release unit tests +5
   
5. [unit testing] hidden error message #9468
   Highest Severity bug pre-release unit tests +4
   
6. [Bug] can't override namespaced macros for unit testing #9624
   High Severity bug pre-release unit tests +4
   
7. [Bug] fixtures in fixtures/subfolders throwing parsing error #9570
   High Severity bug pre-release unit tests +4
   
8. [Bug] parse-time validation when unit testing incremental model #9593
   High Severity bug dbt tests incremental pre-release unit tests +6
   
9. Wording of TestConfigDeprecation is incorrect #9579
   High Severity bug pre-release unit tests +4
   
10. [Spike+] can't unit test precision #9627
    High Severity bug pre-release unit tests user docs +5
    
11. [Bug] Unit tests + compiled paths: report correct compiled path if the test fails, and don't overwrite input compiled paths with fixtures #9608
    High Severity bug dbt tests pre-release unit tests +5
    
12. parsing error when editing fixture files #9620
    bug dbt tests pre-release unit tests +4
    
13. failing unit test displayed in system logs, not at the node level #9619
    Impact: Exp Impact: Orch enhancement pre-release unit tests +5
    
14. [Bug] can't unit test a model that depends on an ephemeral model #9686
    High Severity bug dbt tests pre-release unit tests +5
    

[beta bugs to do]

Preview Give feedback

1. unit testing logging for folks who are color blind #9632
   enhancement unit tests +2
   
2. better error message for unit test with missing input #9882
   dbt tests enhancement stale unit tests +4
3. Unit test fixture (csv) returns "" for empty value #9881
   backport 1.8.latest bug pre-release unit tests user docs +5
   
4. [Bug] Built-in unit tests: dbt ls --select output is not usable with dbt test --select #9895
   High Severity backport 1.8.latest bug dbt tests list pre-release unit tests +7
   
5. Docs site does not support unit tests dbt-docs#506
   bug pre-release regression unit tests +4
   
6. [bug] deferral for unit test when modifying upstream and doing a partial build #10017
   bug pre-release unit tests +3
   
7. [Unit Testing] Allow explicit precision testing in unit tests #9884
   enhancement unit tests user docs +3

[P1]

Preview Give feedback

1. [CT-3121] [Implementation] get schema of inputs prior to executing unit test command #8649
   enhancement user docs +2
2. [CT-3309] --empty flag to to provide a cost-effective way to run a selection of empty models for dbt build and run #8980
   empty user docs +2
   
3. [CT-3529] [Unit Testing] Unit Testing Versioned Models #9344
   user docs +1
   
4. [CT-3437] add test coverage for unit testing a model that depends on a snapshot #9179
   enhancement +1
   
5. [CT-3467] add environment variable / flag to exclude certain resource types #9237
   Impact: CC Impact: Orch enhancement user docs +4
   
6. [CT-3371] Include unit tests in dbt docs dbt-docs#472
   enhancement +1
   
7. [CT-2998] [SPIKE] Handle unit testing of JSON and ARRAY data types #8423
   Impact: Adapters enhancement +2
   
8. [CT-3567] [Feature] unit testing support format: sql #9405
   enhancement user docs +2
   
9. Add a new selection method for unit_test: #10053
   backport 1.8.latest list node selection unit tests user docs +5
10. [CT-3495] I want to use spacing to make my csv input/expected output mock data more readable for unit tests #9280
    enhancement paper_cut unit tests +3
11. [CT-3153] [implementation] limit the size of fixtures for unit testing #8708
    unit tests user docs +2
12. [CT-3129] Ability to test the incremental behavior of models after merge/insert/append/etc has occurred #8664
    enhancement unit tests +2
13. [CT-3033] [Spike] Explore support multiple unit test materialization strategies: CTE vs 'seed'-based #8499
    enhancement unit tests +2
14. [CT-3496] allow "missing" inputs for inputs where you want to use empty mock data for unit test #9282
    enhancement unit tests +2
15. [Unit Testing] Implement unit_testing_column_schema_strategy macro and use it unit materialization dbt-adapters#113
    0 of 6
    Stale enhancement refinement user docs +4
16. [Unit Testing] Extend TestRedshiftUnitTestingTypes to include complex types dbt-redshift#726
    enhancement unit tests +2
17. [Unit Testing] Extend TestPostgresUnitTestingTypes to include complex types dbt-postgres#29
    enhancement unit tests +2

[P2]

Preview Give feedback

1. [CT-3460] [unit testing] Update unique id for data tests #9220
   Impact: CA unit tests user docs +3
   
2. [CT-3398] unit tests should support enabled #9109
   enhancement paper_cut unit tests user docs +4
3. [CT-3497] I want to add a description/label to each of the rows in my unit test to explicitly call out the edge cases I'm testing for #9283
   enhancement unit tests +2
4. [CT-3310] Support --empty flag for dbt seed #8981
   Impact: Adapters empty unit tests user docs +4
5. [CT-3468] allow creating unit testing fixtures in non-root projects #9238
   enhancement unit tests +2
6. [CT-2919] Improved way of generating unit test yaml, via codegen or other techniques #8292
   enhancement unit tests +2
7. [CT-2920] Unit testing python models #8293
   enhancement unit tests +2
8. [CT-2999] Unit testing of CTEs #8425
   enhancement unit tests +2
9. [CT-2918] Implement inline fixture reuse, in a "fixtures" yaml file section #8291
   enhancement unit tests +2

[graciegoheen]

I'm going to close this as completed, since our first pass at unit testing was released in dbt-core 1.8