not_covered.md

The README discusses what is covered in this repo.

What it does not cover

1. clear delineation between "anomaly detection" and "broken" data (e.g., broken expectations/contracts/promises)
   1. Anomalous data might be a good or bad surprise (more revenue than expected 👍 or more complaints than ever before 👎) but the data might still be correct and not "broken"
   2. Broken data violates some fundamental expectation of the data, like no nulls or unique identifiers
   3. Configuing error vs. warn severity levels in dbt
2. the new pytest-based testing framework (that can be used for adapters and packages alike)
   1. or alternatives like pytest-dbt-core
3. unit testing:
   1. dbt_unittest
   2. dbt-datamocktool
   3. dbt-unit-test
   4. any other way of "unit testing" dbt transformations
4. test coverage:
   1. dbt-test-coverage
5. structural conformance testing:
   1. dbt-project-evaluator
   2. dbt_meta_testing
   3. oliver-twist
6. data comparisons
   1. data-diff
   2. data-diff-demo
   3. dbt-audit-helper
7. other stuff related to data observability:
   1. elementary
   2. dbt_dataquality
   3. etc