From 277e76244edb2b8068a9b2320c24e985f4788b61 Mon Sep 17 00:00:00 2001 From: Juliet Shackell Date: Thu, 20 Nov 2025 14:50:51 -0800 Subject: [PATCH 1/2] fix: update --help for runrelevanttests based on new info --- messages/delete.source.md | 4 +++- messages/deploy.metadata.md | 4 ++-- messages/deploy.metadata.validate.md | 4 +++- 3 files changed, 8 insertions(+), 4 deletions(-) diff --git a/messages/delete.source.md b/messages/delete.source.md index da571700e..afeb6c49e 100644 --- a/messages/delete.source.md +++ b/messages/delete.source.md @@ -106,7 +106,9 @@ Valid values are: - RunAllTestsInOrg — All tests in your org are run, including tests of managed packages. -If you don’t specify a test level, the default behavior depends on the contents of your deployment package and target org. For more information, see “Running Tests in a Deployment” in the Metadata API Developer Guide. +- RunRelevantTests — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest Annotation" in the "Apex Developer Guide" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). + +If you don’t specify a test level, the default behavior depends on the contents of your deployment package and target org. For more information, see "Running Tests in a Deployment" (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the "Metadata API Developer Guide". # localPrompt diff --git a/messages/deploy.metadata.md b/messages/deploy.metadata.md index fa4248be5..c7649209c 100644 --- a/messages/deploy.metadata.md +++ b/messages/deploy.metadata.md @@ -104,9 +104,9 @@ Valid values are: - RunAllTestsInOrg — All tests in your org are run, including tests of managed packages. -- RunRelevantTests — Runs only tests that are relevant to the files being deployed. +- RunRelevantTests — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest Annotation" in the "Apex Developer Guide" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). - If you don’t specify a test level, the default behavior depends on the contents of your deployment package and target org. For more information, see [Running Tests in a Deployment](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the "Metadata API Developer Guide". +If you don’t specify a test level, the default behavior depends on the contents of your deployment package and target org. For more information, see "Running Tests in a Deployment" (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the "Metadata API Developer Guide". # flags.source-dir.summary diff --git a/messages/deploy.metadata.validate.md b/messages/deploy.metadata.validate.md index ad2b96449..fa0d7c1e9 100644 --- a/messages/deploy.metadata.validate.md +++ b/messages/deploy.metadata.validate.md @@ -52,7 +52,9 @@ Valid values are: - RunAllTestsInOrg — All tests in your org are run, including tests of managed packages. -- RunRelevantTests — Runs only tests that are relevant to the files being deployed. +- RunRelevantTests — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest Annotation" in the "Apex Developer Guide" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). + +If you don’t specify a test level, the default behavior depends on the contents of your deployment package and target org. For more information, see "Running Tests in a Deployment" (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the "Metadata API Developer Guide". # flags.source-dir.summary From af96753c7379aeb02a2f3553b5c44cd6c6d00f32 Mon Sep 17 00:00:00 2001 From: Juliet Shackell Date: Thu, 20 Nov 2025 16:27:44 -0800 Subject: [PATCH 2/2] fix: edit --- messages/delete.source.md | 2 +- messages/deploy.metadata.md | 2 +- messages/deploy.metadata.validate.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/messages/delete.source.md b/messages/delete.source.md index afeb6c49e..e4d6222d8 100644 --- a/messages/delete.source.md +++ b/messages/delete.source.md @@ -106,7 +106,7 @@ Valid values are: - RunAllTestsInOrg — All tests in your org are run, including tests of managed packages. -- RunRelevantTests — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest Annotation" in the "Apex Developer Guide" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). +- RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest Annotation" in the "Apex Developer Guide" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and triggers individually and is different than the overall coverage percentage. If you don’t specify a test level, the default behavior depends on the contents of your deployment package and target org. For more information, see "Running Tests in a Deployment" (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the "Metadata API Developer Guide". diff --git a/messages/deploy.metadata.md b/messages/deploy.metadata.md index c7649209c..cee72524a 100644 --- a/messages/deploy.metadata.md +++ b/messages/deploy.metadata.md @@ -104,7 +104,7 @@ Valid values are: - RunAllTestsInOrg — All tests in your org are run, including tests of managed packages. -- RunRelevantTests — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest Annotation" in the "Apex Developer Guide" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). +- RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest Annotation" in the "Apex Developer Guide" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and triggers individually and is different than the overall coverage percentage. If you don’t specify a test level, the default behavior depends on the contents of your deployment package and target org. For more information, see "Running Tests in a Deployment" (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the "Metadata API Developer Guide". diff --git a/messages/deploy.metadata.validate.md b/messages/deploy.metadata.validate.md index fa0d7c1e9..506ccfa7b 100644 --- a/messages/deploy.metadata.validate.md +++ b/messages/deploy.metadata.validate.md @@ -52,7 +52,7 @@ Valid values are: - RunAllTestsInOrg — All tests in your org are run, including tests of managed packages. -- RunRelevantTests — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest Annotation" in the "Apex Developer Guide" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). +- RunRelevantTests (Beta) — Runs only tests that are relevant to the files being deployed. Salesforce automatically identifies the relevant tests based on an analysis of the deployment payload and the payload dependencies. For fine-grained control, you can also annotate test classes so that they always run in certain conditions. See "@IsTest Annotation" in the "Apex Developer Guide" (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_annotation_isTest.htm). Each class and trigger in the deployment package must be covered by the executed tests for a minimum of 75% code coverage. This coverage is computed for each class and triggers individually and is different than the overall coverage percentage. If you don’t specify a test level, the default behavior depends on the contents of your deployment package and target org. For more information, see "Running Tests in a Deployment" (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) in the "Metadata API Developer Guide".