sf-delta-tests

Calculate dependencies and scope to relevant tests.

  

This plugin is designed to optimize your Salesforce CI/CD pipeline by calculating only the relevant test classes that need to be run based on the metadata changes in your package. It uses the Salesforce Dependency API to determine these relationships.

Install

``bash
sf plugins install sf-delta-tests
`

$3

To build the plugin locally, make sure to have yarn installed and run the following commands:

`bash


Install the dependencies and compile


yarn && yarn build
`

To use your plugin, run using the local ./bin/dev.js or ./bin/dev.cmd file.

`bash


Run using local run file.


./bin/dev.js delta test-classes -o --package-path=test/fixtures/manifest/package.xml
`

There should be no differences when running via the Salesforce CLI or using the local run file. However, it can be useful to link the plugin to do some additional testing or run your commands from anywhere on your machine.

`bash


Link your plugin to the sf cli

sf plugins link .

To verify

sf plugins
`

Commands


* sf delta test-classes

sf delta test-classes

Run only related tests

`
USAGE
$ sf delta test-classes -o [--json] [--flags-dir ] [-p ] [--always-run-test ...]
[--include-all-flows]

FLAGS
-o, --target-org= (required) The org you want to check the dependencies against.
-p, --package-path= [default: manifest/package.xml] Path to the package.xml that will be deployed.
--always-run-test=... A test class to run when no tests need to be ran.
--[no-]include-all-flows When enabled, if any Flow is changed, include all Flows that require test coverage
based on their trigger type or process type. This ensures proper test coverage
validation since Salesforce checks coverage for all such Flows during deployment,
not just the changed ones. Use --no-include-all-flows to disable.

GLOBAL FLAGS
--flags-dir= Import flag values from a directory.
--json Format output as json.

DESCRIPTION
Run only related tests

Calculates the tests needed to be ran based on the changed metadata given using the Salesforce Dependency API. For
Flows, also queries FlowTestCoverage to include test classes that have previously covered the Flows.

EXAMPLES
testCmd=$(sf delta test-classes --target-org matt@never.io.dev)

$ sf project deploy validate ${testCmd}
`


- sf delta test-classes

sf delta test-classes

Calculates the tests needed to be run based on the changed metadata given using the Salesforce Dependency API

`
Run only related tests

USAGE
$ sf delta test-classes -o [--json] [--flags-dir ] [-p ] [--always-run-test ...] [--include-all-flows]

FLAGS
-o, --target-org= (required) The org you want to check the dependencies against.
-p, --package-path= [default: manifest/package.xml] Path to the package.xml that will be deployed.
--always-run-test=... A test class to run when no tests need to be ran.
--[no-]include-all-flows When enabled, if any Flow is changed, include all Flows that require test coverage based on their trigger type
or process type. This ensures proper test coverage validation since Salesforce checks coverage for all such
Flows during deployment, not just the changed ones. Use --no-include-all-flows to disable.

GLOBAL FLAGS
--flags-dir= Import flag values from a directory.
--json Format output as json.

DESCRIPTION
Run only related tests

Calculates the tests needed to be ran based on the changed metadata given using the Salesforce Dependency API

EXAMPLES
testCmd=$(sf delta test-classes --target-org matt@never.io.dev)

$ sf project deploy validate ${testCmd}
``