docs: rearrange message locations

Author: EstebanRomero84

messages/logicruntest.md

@@ -4,37 +4,38 @@ Invoke tests for Apex and Flows in an org.
 
 # description
 
-This command provides a single, unified interface to run tests for multiple metadata types.
-By default, the command executes asynchronously, returning a test run ID. Use 'sf logic get test' to retrieve the results.
-Use the --synchronous flag to wait for the test run to complete and see the results in the command output.
-To run specific tests, use --test-names. To run all tests of a certain type, use --test-level with --test-category. If neither is specified, all local tests for all categories will be run.
+This command provides a single and unified way to run tests for multiple Salesforce features, such as Apex classes and Flows. Running the tests together with a single command ensures seamless interoperability between the features.
 
-# examples
+By default, the command executes asynchronously and returns a test run ID. Then use the "sf logic get test" command to retrieve the results. If you want to wait for the test run to complete and see the results in the command output, use the --synchronous flag.
 
-- Run a mix of specific named tests for Apex and Flow asynchronously:
+To run specific tests, use the --tests flag, passing it the Apex test class names or the Flow tests in the form Flowtest.<name>. You can also run specific test methods, although if you run the tests synchronously, the methods must belong to a single Apex class or Flow test. To run all tests of a certain category, use --test-level with --test-category. If neither flag is specified, all local tests for all categories are run by default. You can also use the --class-names and --suite-names flags to run Apex test classes or suites.
 
-  <%= config.bin %> <%= command.id %> --test-names MyApexClassTest,FlowTest.ProcessOrder
+To see code coverage results, use the --code-coverage flag with --result-format. The output displays a high-level summary of the test run and the code coverage values for the tested classes or flows. If you specify human-readable result format, use the --detailed-coverage flag to see detailed coverage results for each test method run.
 
-- Run all local tests for only the Apex and Flow categories, waiting for the results to complete:
+You must have the "View All Data" org system permission to use this command. The permission is disabled by default and can be enabled only by a system administrator.
 
-  <%= config.bin %> <%= command.id %> --test-level RunLocalTests --test-category Apex --test-category Flow --synchronous
+# examples
 
-- Run all local tests for ALL categories (the default behavior) and save the JUnit results to the "test-results" directory:
+- Run a mix of specific Apex and Flow tests asynchronously in your default org:
 
-  <%= config.bin %> <%= command.id %> --result-format junit --output-dir test-results --synchronous
+  <%= config.bin %> <%= command.id %> --tests MyApexClassTest,FlowTest.ProcessOrder
 
-# flags.logicTests.summary
+- Run all local Apex and Flow tests and wait for the results to complete; run the tests in the org with alias "my-scratch":
 
-Comma-separated list of test names to run. Can include Apex classes, Flow tests (FlowTest.<name>), and Agent tests (AgentTest.<name>).
+  <%= config.bin %> <%= command.id %> --test-level RunLocalTests --test-category Apex --test-category Flow --synchronous --target-org my-scratch
 
-# flags.test-category.summary
+- Run two methods in an Apex test class and an Apex test suite:
 
-Category of tests to run.
+  <%= config.bin %> <%= command.id %> --class-names MyApexClassTest.methodA --class-names MyApexClassTest.methodB --suite-names MySuite
 
-# flags.test-category.description
+- Run all local tests for all categories (the default behavior), save the JUnit results to the "test-results" directory, and include code coverage results:
 
-Category of tests to run. Can be specified multiple times. Valid values are 'Apex' and 'Flow'.
+  <%= config.bin %> <%= command.id %> --result-format junit --output-dir test-results --synchronous --code-coverage
 
-# runLogicTestReportCommand
+# flags.logicTests.summary
+
+Comma-separated list of test names to run. Can include Apex test classes and Flow tests.
+
+# flags.test-category.summary
 
-Run "%s logic get test -i %s -o %s" to retrieve test results
+Category of tests to run, such as Apex or Flow.

messages/runlogictest.md

@@ -127,44 +127,3 @@ Display detailed code coverage per test.
 # flags.concise.summary
 
 Display only failed test results; works with human-readable output only.
-
-# runTestReportCommand
-
-Run "%s apex get test -i %s -o %s" to retrieve test results
-
-# runLogicTestReportCommand
-
-Run "%s logic get test -i %s -o %s" to retrieve test results
-
-# runTestSyncInstructions
-
-Run with --synchronous or increase --wait timeout to wait for results.
-
-# syncClassErr
-
-Synchronous test runs can include test methods from only one Apex class. Omit the --synchronous flag or include tests from only one class.
-
-# syncClassErrForUnifiedLogic
-
-Synchronous test runs can include test methods from either a single Apex class or a single Flow test. Omit the --synchronous flag or include test methods from only one class or Flow.
-
-# testLevelErr
-
-When specifying classnames, suitenames, or tests, indicate RunSpecifiedTests as the testlevel
-
-# testResultProcessErr
-
-Encountered an error when processing test results
-%s
-
-# apexTestReportFormatHint
-
-Run "sf apex get test %s --result-format <format>" to retrieve test results in a different format.
-
-# outputDirHint
-
-Test result files written to %s
-
-# apexLibErr
-
-Unknown error in Apex Library: %s

messages/runtest.md

@@ -94,7 +94,6 @@ export default class RunTestLogic extends SfCommand<RunCommandResult> {
     }),
     'test-category': arrayWithDeprecation({
       summary: messages.getMessage('flags.test-category.summary'),
-      description: messages.getMessage('flags.test-category.description'),
       options: ['Agent', 'Apex', 'Flow'],
     }),
   };

src/commands/logic/run/test.ts

@@ -23,7 +23,7 @@ import { JsonReporter, RunResult } from './jsonReporter.js';
 const FAILURE_EXIT_CODE = 100;
 
 Messages.importMessagesDirectoryFromMetaUrl(import.meta.url);
-const messages = Messages.loadMessages('@salesforce/plugin-apex', 'runtest');
+const messages = Messages.loadMessages('@salesforce/plugin-apex', 'runtestcommon');
 
 export class TestReporter {
   /**
@@ -72,7 +72,13 @@ export class TestReporter {
       }
       switch (options['result-format']) {
         case 'human':
-          this.logHuman(result, options['detailed-coverage'] as boolean, options['concise'], options['output-dir'], options.isUnifiedLogic);
+          this.logHuman(
+            result,
+            options['detailed-coverage'] as boolean,
+            options['concise'],
+            options['output-dir'],
+            options.isUnifiedLogic
+          );
           break;
         case 'tap':
           this.logTap(result);
@@ -187,7 +193,13 @@ export class TestReporter {
     }
   }
 
-  private logHuman(result: TestResult, detailedCoverage: boolean, concise: boolean, outputDir?: string, isUnifiedLogic?: boolean): void {
+  private logHuman(
+    result: TestResult,
+    detailedCoverage: boolean,
+    concise: boolean,
+    outputDir?: string,
+    isUnifiedLogic?: boolean
+  ): void {
     if (outputDir) {
       this.ux.log(messages.getMessage('outputDirHint', [outputDir]));
     }