diff --git a/openmetadata-docs/content/deployment/upgrade/versions/011-to-012.md b/openmetadata-docs/content/deployment/upgrade/versions/011-to-012.md
index 6170b9edb8b..10f7750ba65 100644
--- a/openmetadata-docs/content/deployment/upgrade/versions/011-to-012.md
+++ b/openmetadata-docs/content/deployment/upgrade/versions/011-to-012.md
@@ -43,6 +43,14 @@ internals as well. Main topics to consider:
 2. Any past test data will be cleaned up during the upgrade to 0.12.0, as the internal data storage has been improved
 3. The Profiler Ingestion Pipelines will be cleaned up during the upgrade to 0.12.0 as well.
 
+### DBT Tests Integration
+
+From 0.12, OpenMetadata supports ingesting the tests and the test results from your DBT project.
+
+- Along with `manifest.json` and `catalog.json` files, We now provide an option to ingest the `run_results.json` file generated from the DBT run and ingest the test results from it.
+- The field to enter the `run_results.json` file path is an optional field in the case of local and http DBT configs. The test results will be ingested from this file if it is provided.
+- For others the file will be picked from their respective sources if it is available.
+
 ### Profiler Workflow Updates
 
 On top of the information above, the `fqnFilterPattern` has been converted into the same patterns we use for ingestion,
@@ -100,6 +108,8 @@ upgrade that, but you want to use OM 0.12, reach out to us.
   - Removed: `hostPort`
 - Databricks
   - Removed: `username` and `password`
+- DBT Config
+  - Added: `dbtRunResultsFilePath` and `dbtRunResultsHttpPath` where path of the `run_results.json` file can be passed to get the test results data from DBT.
 
 ### Ingestion from CLI