Merge branch 'main' into er/addSupportForAgentTests

Author: jshackell-sfdc

.eslintrc.cjs

@@ -1,9 +1,3 @@
-/*
- * Copyright (c) 2021, salesforce.com, inc.
- * All rights reserved.
- * Licensed under the BSD 3-Clause license.
- * For full license text, see LICENSE.txt file in the repo root or https://opensource.org/licenses/BSD-3-Clause
- */
 module.exports = {
   extends: ['eslint-config-salesforce-typescript', 'eslint-config-salesforce-license', 'plugin:sf-plugin/recommended'],
 };

CHANGELOG.md

@@ -1,3 +1,15 @@
+# [3.8.0](https://github.com/salesforcecli/plugin-apex/compare/3.7.1...3.8.0) (2025-09-16)
+
+### Bug Fixes
+
+- remove Agent as a valid test-category value ([59e607b](https://github.com/salesforcecli/plugin-apex/commit/59e607b80aa0d13e4019e5d234010b3ded093703))
+- remove alias ([93e15e1](https://github.com/salesforcecli/plugin-apex/commit/93e15e1e02c90ad127d21d9d58339d7bbbf51954))
+- rename class ([6bf342c](https://github.com/salesforcecli/plugin-apex/commit/6bf342c229ddd42f8fa6c57bc9217f296845d049))
+
+### Features
+
+- add logic run test command ([89ff36b](https://github.com/salesforcecli/plugin-apex/commit/89ff36ba5dcca1a357333b62ba414df0afbdfd74))
+
 ## [3.7.1](https://github.com/salesforcecli/plugin-apex/compare/3.7.0...3.7.1) (2025-09-14)
 
 ### Bug Fixes

README.md

@@ -94,6 +94,7 @@ Happy debugging!
 - [`sf apex run test`](#sf-apex-run-test)
 - [`sf apex tail log`](#sf-apex-tail-log)
 - [`sf logic get test`](#sf-logic-get-test)
+- [`sf logic run test`](#sf-logic-run-test)
 
 ## `sf apex get log`
 
@@ -149,7 +150,7 @@ FLAG DESCRIPTIONS
     directory.
 ```
 
-_See code: [src/commands/apex/get/log.ts](https://github.com/salesforcecli/plugin-apex/blob/3.7.1/src/commands/apex/get/log.ts)_
+_See code: [src/commands/apex/get/log.ts](https://github.com/salesforcecli/plugin-apex/blob/3.8.0/src/commands/apex/get/log.ts)_
 
 ## `sf apex get test`
 
@@ -209,7 +210,7 @@ EXAMPLES
       me@myorg'
 ```
 
-_See code: [src/commands/apex/get/test.ts](https://github.com/salesforcecli/plugin-apex/blob/3.7.1/src/commands/apex/get/test.ts)_
+_See code: [src/commands/apex/get/test.ts](https://github.com/salesforcecli/plugin-apex/blob/3.8.0/src/commands/apex/get/test.ts)_
 
 ## `sf apex list log`
 
@@ -249,7 +250,7 @@ EXAMPLES
     $ sf apex list log --target-org [email protected]
 ```
 
-_See code: [src/commands/apex/list/log.ts](https://github.com/salesforcecli/plugin-apex/blob/3.7.1/src/commands/apex/list/log.ts)_
+_See code: [src/commands/apex/list/log.ts](https://github.com/salesforcecli/plugin-apex/blob/3.8.0/src/commands/apex/list/log.ts)_
 
 ## `sf apex run`
 
@@ -296,7 +297,7 @@ EXAMPLES
     $ sf apex run
 ```
 
-_See code: [src/commands/apex/run.ts](https://github.com/salesforcecli/plugin-apex/blob/3.7.1/src/commands/apex/run.ts)_
+_See code: [src/commands/apex/run.ts](https://github.com/salesforcecli/plugin-apex/blob/3.8.0/src/commands/apex/run.ts)_
 
 ## `sf apex run test`
 
@@ -348,6 +349,9 @@ DESCRIPTION
   haven't finished by the end of the wait time, the command displays a test run ID. Use the "sf apex get test
   --test-run-id" command to get the results.
 
+  To run both Apex and Flow tests together, run the "sf logic run test" CLI command, which has similar flags as this
+  command, but expands the --tests flag to also include Flow tests.
+
   You must have the "View All Data" system permission to use this command. The permission is disabled by default and can
   be enabled only by a system administrator.
 
@@ -439,7 +443,7 @@ FLAG DESCRIPTIONS
     --tests Test1 --tests Test2
 ```
 
-_See code: [src/commands/apex/run/test.ts](https://github.com/salesforcecli/plugin-apex/blob/3.7.1/src/commands/apex/run/test.ts)_
+_See code: [src/commands/apex/run/test.ts](https://github.com/salesforcecli/plugin-apex/blob/3.8.0/src/commands/apex/run/test.ts)_
 
 ## `sf apex tail log`
 
@@ -482,7 +486,7 @@ EXAMPLES
     $ sf apex tail log --color --skip-trace-flag
 ```
 
-_See code: [src/commands/apex/tail/log.ts](https://github.com/salesforcecli/plugin-apex/blob/3.7.1/src/commands/apex/tail/log.ts)_
+_See code: [src/commands/apex/tail/log.ts](https://github.com/salesforcecli/plugin-apex/blob/3.8.0/src/commands/apex/tail/log.ts)_
 
 ## `sf logic get test`
 
@@ -530,6 +534,122 @@ EXAMPLES
     $ sf logic get test --test-run-id <test run id> --result-format junit --target-org my-scratch
 ```
 
-_See code: [src/commands/logic/get/test.ts](https://github.com/salesforcecli/plugin-apex/blob/3.7.1/src/commands/logic/get/test.ts)_
+_See code: [src/commands/logic/get/test.ts](https://github.com/salesforcecli/plugin-apex/blob/3.8.0/src/commands/logic/get/test.ts)_
+
+## `sf logic run test`
+
+Invoke tests for Apex and Flows in an org.
+
+```
+USAGE
+  $ sf logic run test -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-d <value>] [-l
+    RunLocalTests|RunAllTestsInOrg|RunSpecifiedTests] [-n <value>... | -s <value>... | -t <value>... | --test-category
+    Apex|Flow...] [-r human|tap|junit|json] [-w <value>] [-y] [-v -c] [--concise]
+
+FLAGS
+  -c, --code-coverage              Retrieve code coverage results.
+  -d, --output-dir=<value>         Directory in which to store test run files.
+  -l, --test-level=<option>        Level of tests to run; default is RunLocalTests.
+                                   <options: RunLocalTests|RunAllTestsInOrg|RunSpecifiedTests>
+  -n, --class-names=<value>...     Apex test class names to run; default is all classes.
+  -o, --target-org=<value>         (required) Username or alias of the target org. Not required if the `target-org`
+                                   configuration variable is already set.
+  -r, --result-format=<option>     [default: human] Format of the test results.
+                                   <options: human|tap|junit|json>
+  -s, --suite-names=<value>...     Apex test suite names to run.
+  -t, --tests=<value>...           Comma-separated list of test names to run. Can include Apex test classes and Flow
+                                   tests.
+  -v, --detailed-coverage          Display detailed code coverage per test.
+  -w, --wait=<value>               Sets the streaming client socket timeout in minutes; specify a longer wait time if
+                                   timeouts occur frequently.
+  -y, --synchronous                Runs test methods from a single Apex class synchronously; if not specified, tests are
+                                   run asynchronously.
+      --api-version=<value>        Override the api version used for api requests made by this command
+      --concise                    Display only failed test results; works with human-readable output only.
+      --test-category=<option>...  Category of tests to run, such as Apex or Flow.
+                                   <options: Apex|Flow>
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Invoke tests for Apex and Flows in an org.
+
+  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.
+
+  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.
+
+  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.
+
+  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.
+
+  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.
+
+EXAMPLES
+  Run a mix of specific Apex and Flow tests asynchronously in your default org:
+
+    $ sf logic run test --tests MyApexClassTest,FlowTest.ProcessOrder
+
+  Run all local Apex and Flow tests and wait for the results to complete; run the tests in the org with alias
+  "my-scratch":
+
+    $ sf logic run test --test-level RunLocalTests --test-category Apex --test-category Flow --synchronous \
+      --target-org my-scratch
+
+  Run two methods in an Apex test class and an Apex test suite:
+
+    $ sf logic run test --class-names MyApexClassTest.methodA --class-names MyApexClassTest.methodB --suite-names \
+      MySuite
+
+  Run all local tests for all categories (the default behavior), save the JUnit results to the "test-results"
+  directory, and include code coverage results:
+
+    $ sf logic run test --result-format junit --output-dir test-results --synchronous --code-coverage
+
+FLAG DESCRIPTIONS
+  -l, --test-level=RunLocalTests|RunAllTestsInOrg|RunSpecifiedTests  Level of tests to run; default is RunLocalTests.
+
+    Here's what the levels mean:
+
+    - RunSpecifiedTests — Only the tests that you specify in the runTests option are run. Code coverage requirements
+    differ from the default coverage requirements when using this test level. The executed tests must cover each class
+    and trigger in the deployment package 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.
+    - RunLocalTests — All local tests in your org, including tests that originate from no-namespaced unlocked packages,
+    are run. The tests that originate from installed managed packages and namespaced unlocked packages aren't run. This
+    test level is the default for production deployments that include Apex classes or triggers.
+    - RunAllTestsInOrg — All tests are run. The tests include all tests in your org.
+
+  -n, --class-names=<value>...  Apex test class names to run; default is all classes.
+
+    If you select --class-names, you can't specify --suite-names or --tests.
+    For multiple classes, repeat the flag for each.
+    --class-names Class1 --class-names Class2
+
+  -s, --suite-names=<value>...  Apex test suite names to run.
+
+    If you select --suite-names, you can't specify --class-names or --tests.
+    For multiple suites, repeat the flag for each.
+    --suite-names Suite1 --suite-names Suite2
+
+  -t, --tests=<value>...  Comma-separated list of test names to run. Can include Apex test classes and Flow tests.
+
+    If you specify --tests, you can't specify --class-names or --suite-names
+    For multiple tests, repeat the flag for each.
+    --tests Test1 --tests Test2
+```
+
+_See code: [src/commands/logic/run/test.ts](https://github.com/salesforcecli/plugin-apex/blob/3.8.0/src/commands/logic/run/test.ts)_
 
 <!-- commandsstop -->

messages/runlogictest.md

@@ -8,7 +8,9 @@ This command provides a single and unified way to run tests for multiple Salesfo
 
 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.
 
-To run specific tests, use the --tests flag, passing it the Apex test class names or the Flow tests in the form FlowTest.<name> or Agentforce agents tests in the form AgentTest.<name>. You can also run specific test methods, although if you run the tests synchronously, the methods must belong to a single Apex class, Flow test or Agentforce agents 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.
+To run specific tests, use the --tests flag and pass it the names of Apex and Flow tests. For Apex, simply specify the name of the Apex test class. For Flows, use the format "FlowTesting.<name-of-flow-test>". To find the name of all the flow tests in your org, run this command and specify the Flow category, such as "sf logic run test --synchronous --test-category Flow --test-level RunAllTestsInOrg". The command displays a table of all the flow tests it ran; see the "TEST NAME" column for the full name of all available flow tests in your org.
+
+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-category and --test-level together. If neither of these flags 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.
 
 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, flows or Agentforce agents. If you specify human-readable result format, use the --detailed-coverage flag to see detailed coverage results for each test method run.
 
@@ -18,7 +20,7 @@ You must have the "View All Data" org system permission to use this command. The
 
 - Run a mix of specific Apex and Flow tests asynchronously in your default org:
 
-  <%= config.bin %> <%= command.id %> --tests MyApexClassTest --tests FlowTest.ProcessOrder
+  <%= config.bin %> <%= command.id %> --tests MyApexClassTest,FlowTesting.Modify_Account_Desc.Modify_Account_Desc_TestAccountDescription                                     
 
 - Run all local Apex and Flow tests and wait for the results to complete; run the tests in the org with alias "my-scratch":
 

package.json

@@ -1,7 +1,7 @@
 {
   "name": "@salesforce/plugin-apex",
   "description": "Apex commands",
-  "version": "3.7.1",
+  "version": "3.8.0",
   "author": "Salesforce",
   "bugs": "https://github.com/forcedotcom/cli/issues",
   "dependencies": {

test/.eslintrc.cjs

@@ -1,10 +1,3 @@
-/*
- * Copyright (c) 2021, salesforce.com, inc.
- * All rights reserved.
- * Licensed under the BSD 3-Clause license.
- * For full license text, see LICENSE.txt file in the repo root or https://opensource.org/licenses/BSD-3-Clause
- */
-
 module.exports = {
   extends: '../.eslintrc.cjs',
   // Allow describe and it