Merge branch 'add-metrics-in-ci' of https://github.com/dbt-labs/docs.…

…getdbt.com into add-metrics-in-ci

website/docs/best-practices/how-we-build-our-metrics/semantic-layer-9-conclusion.md

@@ -28,7 +28,7 @@ pagination_next: null
 
 - 🗺️ Use these best practices to map out your team's plan to **incrementally adopt the Semantic Layer**.
 - 🤗 Get involved in the community and ask questions, **help craft best practices**, and share your progress in building a dbt Semantic Layer.
-- [Test your metrics in CI](/docs/deploy/ci-jobs#test-metrics-in-ci) to ensure code changes made to dbt models don't break these metrics.
+- [Validate semantic nodes in CI](/docs/deploy/ci-jobs#semantic-validations-in-ci) to ensure code changes made to dbt models don't break these metrics.
 
 The dbt Semantic Layer is the biggest paradigm shift thus far in the young practice of analytics engineering. It's ready to provide value right away, but is most impactful if you move your project towards increasing normalization, and allow MetricFlow to do the denormalization for you with maximum dimensionality.
 

website/docs/docs/build/saved-queries.md

@@ -230,5 +230,5 @@ To include all saved queries in the dbt build run, use the [`--resource-type` fl
 </detailsToggle>
 
 ## Related docs
-- [Test your metrics in a CI job](/docs/deploy/ci-jobs#test-metrics-in-ci) 
+- [Validate semantic nodes in a CI job](/docs/deploy/ci-jobs#semantic-validations-in-ci)
 - Configure [caching](/docs/use-dbt-semantic-layer/sl-cache)

website/docs/docs/deploy/deploy-environments.md

@@ -41,7 +41,7 @@ In dbt Cloud, each project can have one designated deployment environment, which
 
 For customers using the dbt Semantic Layer, the next section of environment settings is the Semantic Layer configurations. [The Semantic Layer setup guide](/docs/use-dbt-semantic-layer/setup-sl) has the most up-to-date setup instructions.
 
-You can also leverage the dbt Job scheduler to [validate your semantic nodes in a CI job](/docs/deploy/ci-jobs#test-metrics-in-ci) to ensure code changes made to dbt models don't break these metrics.
+You can also leverage the dbt Job scheduler to [validate your semantic nodes in a CI job](/docs/deploy/ci-jobs#semantic-validations-in-ci) to ensure code changes made to dbt models don't break these metrics.
 
 ## Staging environment
 

website/docs/docs/use-dbt-semantic-layer/exports.md

@@ -203,6 +203,6 @@ To include all saved queries in the dbt build run, use the [`--resource-type` fl
 </detailsToggle>
 
 ## Related docs
-- [Test your metrics in a CI job](/docs/deploy/ci-jobs#test-metrics-in-ci)
+- [Validate semantic nodes in a CI job](/docs/deploy/ci-jobs#semantic-validations-in-ci)
 - Configure [caching](/docs/use-dbt-semantic-layer/sl-cache)
 - [dbt Semantic Layer FAQs](/docs/use-dbt-semantic-layer/sl-faqs)

website/docs/docs/use-dbt-semantic-layer/setup-sl.md

@@ -47,7 +47,7 @@ import SlSetUp from '/snippets/_new-sl-setup.md';
 
 - Now that you've set up the dbt Semantic Layer, start querying your metrics with the [available integrations](/docs/cloud-integrations/avail-sl-integrations).
 - [Optimize querying performance](/docs/use-dbt-semantic-layer/sl-cache) using declarative caching.
-- [Test your metrics in CI](/docs/deploy/ci-jobs#test-metrics-in-ci) to ensure code changes made to dbt models don't break these metrics.
+- [Validate semantic nodes in CI](/docs/deploy/ci-jobs#semantic-validations-in-ci) to ensure code changes made to dbt models don't break these metrics.
 - If you haven't already, learn how to [build you metrics and semantic models](/docs/build/build-metrics-intro) in your development tool of choice.
 
 ## Related docs

website/docs/docs/use-dbt-semantic-layer/sl-cache.md

@@ -134,6 +134,6 @@ You can manually invalidate the cache through the [dbt Semantic Layer APIs](/doc
 
 
 ## Related docs
-- [Test your metrics in CI](/docs/deploy/ci-jobs#test-metrics-in-ci) 
+- [Validate semantic nodes in CI](/docs/deploy/ci-jobs#semantic-validations-in-ci)
 - [Saved queries](/docs/build/saved-queries)
 - [dbt Semantic Layer FAQs](/docs/use-dbt-semantic-layer/sl-faqs)

website/docs/docs/use-dbt-semantic-layer/sl-faqs.md

@@ -228,10 +228,10 @@ Yes, while [entities](/docs/build/entities) must be defined under “entities,
 
 <Expandable alt_header="Can I test my semantic models and metrics?">
 
-Yes! You can test your metrics in a few ways:
+Yes! You can validate your semantic nodes (semantic models, metrics, saved queries) in a few ways:
 
 - [Query and validate you metrics](/docs/build/metricflow-commands) in your development tool before submitting your code changes.
-- [Test and validate your metrics in CI](/docs/deploy/ci-jobs#test-metrics-in-ci) to ensure code changes made to dbt models don't break these metrics.
+- [Validate semantic nodes in CI](/docs/deploy/ci-jobs#semantic-validations-in-ci) to ensure code changes made to dbt models don't break these metrics.
 
 </Expandable>
 

website/docs/guides/set-up-ci.md

@@ -55,7 +55,7 @@ In the Execution Settings, your command will be preset to `dbt build --select st
 To be able to find modified nodes, dbt needs to have something to compare against. dbt Cloud uses the last successful run of any job in your Production environment as its [comparison state](/reference/node-selection/syntax#about-node-selection). As long as you identified your Production environment in Step 2, you won't need to touch this. If you didn't, pick the right environment from the dropdown.
 
 :::info Use CI to test your metrics
-If you've [built metric definition models](/docs/build/build-metrics-intro) in your dbt project, you can [test and validate them in CI](/docs/deploy/ci-jobs#test-metrics-in-ci) to ensure code changes made to dbt models don't break these metrics.
+If you've [built semantic nodes](/docs/build/build-metrics-intro) in your dbt project, you can [validate them in a CI job](/docs/deploy/ci-jobs#semantic-validations-in-ci) to ensure code changes made to dbt models don't break these metrics.
 :::
 
 ### 3. Test your process