Research
Security News
Malicious npm Package Typosquats react-login-page to Deploy Keylogger
Socket researchers unpack a typosquatting package with malicious code that logs keystrokes and exfiltrates sensitive data to a remote server.
@salesforce/cli-plugins-testkit
Advanced tools
Readme
This package is in heavy development. The APIs exposed from this package are incomplete and will change frequently.
The @salesforce/cli-plugins-testkit library provides test utilities to assist Salesforce CLI plug-in authors with writing NUTs (non-unit-tests), like integration, smoke, and e2e style testing. For example, you could write tests to ensure your plugin commands execute properly using an isolated Salesforce project, scratch org, and different Salesforce CLI executables.
Add this library as a dev dependencies to your project.
yarn add @salesforcecli/cli-plugins-testkit --dev
Create a test file and import the utilities from this library that you'd like to use.
Using a different file extension will help separate your unit tests from your NUTs even if they are in the same directories. For example, if you use mytest.nut.ts
instead of mytest.test.ts
, you can have the following scripts in your package.json (assuming mocha).
{
"scripts": {
"test": "mocha **/*.test.ts",
"test-nut": "mocha **/*.nut.ts"
}
}
Running oclif commands locally is as simple as running against the local bin/run
file.
import { exec } from 'shelljs';
const result = exec('./bin/run mycommand --myflag --json');
console.log(JSON.parse(result.stdout));
However, that doesn't provide flexibility to target different CLI executables in Continuos Integration (CI). For example, you may want to run NUTs against the newly published version of your plugin against the latest-rc of the Salesforce CLI to make sure everything still works as expected.
The testkit provides execCmd
which makes the executable configurable as well as builtin json parsing.
import { execCmd } from '@salesforce/cli-plugins-testkit';
const result = execCmd('mycommand --myflag --json');
console.log(result.jsonOutput);
The executable can then be configured in CI using the TESTKIT_EXECUTABLE_PATH
.
# Install the release candidate in the current directory using NPM
npm install sfdx@latest-rc
# Install the newly published version of my plugin
./node_modules/.bin/sfdx plugins:install myplugin
# Target the local sfdx
export TESTKIT_EXECUTABLE_PATH=./node_modules/.bin/sfdx
# Run NUT test (requires a test-nut script target in the package.json)
yarn test-nut
You will notice that the executable is not configurable in the execCmd
method directly. If you need to run other commands not located in your plugin, use shelljs directly.
import { exec } from 'shelljs';
import { execCmd } from '@salesforce/cli-plugins-testkit';
await exec('sfdx auth:jwt:grant ... --json');
const result = await execCmd('mycommand --myflag --json');
TBD
FAQs
Unknown package
The npm package @salesforce/cli-plugins-testkit receives a total of 16,317 weekly downloads. As such, @salesforce/cli-plugins-testkit popularity was classified as popular.
We found that @salesforce/cli-plugins-testkit demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers unpack a typosquatting package with malicious code that logs keystrokes and exfiltrates sensitive data to a remote server.
Security News
The JavaScript community has launched the e18e initiative to improve ecosystem performance by cleaning up dependency trees, speeding up critical parts of the ecosystem, and documenting lighter alternatives to established tools.
Product
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.