@@ -150,7 +150,7 @@ FLAG DESCRIPTIONS
150
150
directory.
151
151
```
152
152
153
- _ See code: [ src/commands/apex/get/log.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.0 /src/commands/apex/get/log.ts ) _
153
+ _ See code: [ src/commands/apex/get/log.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.1 /src/commands/apex/get/log.ts ) _
154
154
155
155
## ` sf apex get test `
156
156
@@ -210,7 +210,7 @@ EXAMPLES
210
210
me@myorg'
211
211
```
212
212
213
- _ See code: [ src/commands/apex/get/test.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.0 /src/commands/apex/get/test.ts ) _
213
+ _ See code: [ src/commands/apex/get/test.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.1 /src/commands/apex/get/test.ts ) _
214
214
215
215
## ` sf apex list log `
216
216
@@ -250,7 +250,7 @@ EXAMPLES
250
250
$ sf apex list log --target-org [email protected]
251
251
```
252
252
253
- _ See code: [ src/commands/apex/list/log.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.0 /src/commands/apex/list/log.ts ) _
253
+ _ See code: [ src/commands/apex/list/log.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.1 /src/commands/apex/list/log.ts ) _
254
254
255
255
## ` sf apex run `
256
256
@@ -297,7 +297,7 @@ EXAMPLES
297
297
$ sf apex run
298
298
```
299
299
300
- _ See code: [ src/commands/apex/run.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.0 /src/commands/apex/run.ts ) _
300
+ _ See code: [ src/commands/apex/run.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.1 /src/commands/apex/run.ts ) _
301
301
302
302
## ` sf apex run test `
303
303
@@ -443,7 +443,7 @@ FLAG DESCRIPTIONS
443
443
--tests Test1 --tests Test2
444
444
```
445
445
446
- _ See code: [ src/commands/apex/run/test.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.0 /src/commands/apex/run/test.ts ) _
446
+ _ See code: [ src/commands/apex/run/test.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.1 /src/commands/apex/run/test.ts ) _
447
447
448
448
## ` sf apex tail log `
449
449
@@ -486,7 +486,7 @@ EXAMPLES
486
486
$ sf apex tail log --color --skip-trace-flag
487
487
```
488
488
489
- _ See code: [ src/commands/apex/tail/log.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.0 /src/commands/apex/tail/log.ts ) _
489
+ _ See code: [ src/commands/apex/tail/log.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.1 /src/commands/apex/tail/log.ts ) _
490
490
491
491
## ` sf logic get test `
492
492
@@ -534,7 +534,7 @@ EXAMPLES
534
534
$ sf logic get test --test-run-id <test run id> --result-format junit --target-org my-scratch
535
535
```
536
536
537
- _ See code: [ src/commands/logic/get/test.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.0 /src/commands/logic/get/test.ts ) _
537
+ _ See code: [ src/commands/logic/get/test.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.1 /src/commands/logic/get/test.ts ) _
538
538
539
539
## ` sf logic run test `
540
540
@@ -583,11 +583,16 @@ DESCRIPTION
583
583
retrieve the results. If you want to wait for the test run to complete and see the results in the command output, use
584
584
the --synchronous flag.
585
585
586
- To run specific tests, use the --tests flag, passing it the Apex test class names or the Flow tests in the form
587
- Flowtest.<name>. You can also run specific test methods, although if you run the tests synchronously, the methods must
588
- belong to a single Apex class or Flow test. To run all tests of a certain category, use --test-level with
589
- --test-category. If neither flag is specified, all local tests for all categories are run by default. You can also use
590
- the --class-names and --suite-names flags to run Apex test classes or suites.
586
+ To run specific tests, use the --tests flag and pass it the names of Apex and Flow tests. For Apex, simply specify the
587
+ name of the Apex test class. For Flows, use the format "FlowTesting.<name-of-flow-test>". To find the name of all the
588
+ flow tests in your org, run this command and specify the Flow category, such as "sf logic run test --synchronous
589
+ --test-category Flow --test-level RunAllTestsInOrg". The command displays a table of all the flow tests it ran; see
590
+ the "TEST NAME" column for the full name of all available flow tests in your org.
591
+
592
+ You can also run specific test methods, although if you run the tests synchronously, the methods must belong to a
593
+ single Apex class or Flow test. To run all tests of a certain category, use --test-category and --test-level together.
594
+ If neither of these flags is specified, all local tests for all categories are run by default. You can also use the
595
+ --class-names and --suite-names flags to run Apex test classes or suites.
591
596
592
597
To see code coverage results, use the --code-coverage flag with --result-format. The output displays a high-level
593
598
summary of the test run and the code coverage values for the tested classes or flows. If you specify human-readable
@@ -599,7 +604,8 @@ DESCRIPTION
599
604
EXAMPLES
600
605
Run a mix of specific Apex and Flow tests asynchronously in your default org:
601
606
602
- $ sf logic run test --tests MyApexClassTest,FlowTest.ProcessOrder
607
+ $ sf logic run test --tests \
608
+ MyApexClassTest,FlowTesting.Modify_Account_Desc.Modify_Account_Desc_TestAccountDescription
603
609
604
610
Run all local Apex and Flow tests and wait for the results to complete; run the tests in the org with alias
605
611
"my-scratch":
@@ -650,6 +656,6 @@ FLAG DESCRIPTIONS
650
656
--tests Test1 --tests Test2
651
657
```
652
658
653
- _ See code: [ src/commands/logic/run/test.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.0 /src/commands/logic/run/test.ts ) _
659
+ _ See code: [ src/commands/logic/run/test.ts] ( https://github.com/salesforcecli/plugin-apex/blob/3.8.1 /src/commands/logic/run/test.ts ) _
654
660
655
661
<!-- commandsstop -->
0 commit comments