sfdk-check

Display test suites

$ sfdk check --list-suites

$ sfdk check

$ sfdk check [[-l|--levels]] +[level]

$ sfdk check [[-l|--levels]] -[level]

$ sfdk check [[-s|--suites]] +[suite]

$ sfdk check [[-s|--suites]] -[suite]

sfdx doctor:diagnose [--json] [--verbose]

--json
    Output the results in JSON format, suitable for programmatic parsing.

--verbose
    Display more detailed information during the diagnostic process, including raw command outputs and additional checks.

The command 'sfdk-check' is not a standard Linux command. However, it is highly likely a conceptual reference or a typo for diagnostic commands within the Salesforce DX CLI (sfdx). The most analogous command is sfdx doctor:diagnose (or its alias sfdx doctor), which is used to analyze the health, configuration, and dependencies of your Salesforce development environment.

This diagnostic tool verifies critical components such as Node.js installation, Java Development Kit (JDK) presence, Salesforce CLI plugin versions, environment variable settings, and network connectivity to Salesforce instances. It helps developers quickly identify and troubleshoot common setup issues, ensuring their environment is ready for Salesforce development tasks. The output typically provides a summary of passed and failed checks, often with recommendations for remediation.

The command 'sfdk-check' itself does not exist as a standard Linux utility or within the official Salesforce CLI. This analysis is based on the assumption that it refers to the diagnostic capabilities commonly found in Software Development Kits (SDKs), specifically drawing parallels to the sfdx doctor:diagnose command from the Salesforce DX CLI. Users should verify the exact command in their specific SDK documentation if 'sfdk-check' is encountered.

A diagnostic command like this typically verifies:
Node.js Version: Ensures the installed Node.js version meets requirements.
Java Development Kit (JDK): Checks for JDK installation and correct version (often required for older Salesforce tooling or specific plugins).
Salesforce CLI Version: Confirms the CLI itself is up-to-date.
Plugin Health: Validates installed Salesforce CLI plugins.
Environment Variables: Looks for correctly set environment variables like PATH, JAVA_HOME, etc.
Network Connectivity: Tests the ability to reach Salesforce API endpoints.

This command is primarily used by developers when:
1. Setting up a new development environment.
2. Troubleshooting issues with Salesforce CLI commands or project deployment.
3. Verifying prerequisites for new features or Salesforce CLI updates.

Diagnostic tools like 'sfdx doctor:diagnose' became essential with the advent of complex SDKs and CLI tools that rely on multiple external dependencies (Node.js, Java, specific npm packages, etc.). As Salesforce development shifted towards a command-line-centric and source-driven model with Salesforce DX, ensuring a consistent and healthy development environment became critical. The 'doctor' command family was introduced to provide self-service troubleshooting, reducing setup friction and support overhead for developers.

sfdx(1), node(1), java(1)