sfdx-test-results-jacoco v0.1.0

sfdx-test-results-jacoco

helps with converting the results from running tests into jacoco format

• Debugging your plugin

$ npm install -g sfdx-test-results-jacoco
$ sfdx COMMAND
running command...
$ sfdx (-v|--version|version)
sfdx-test-results-jacoco/0.1.0 win32-x64 node-v16.7.0
$ sfdx --help [COMMAND]
USAGE
  $ sfdx COMMAND
...

• sfdx test2jacoco:convert [-i <string>] [-p <string>] [-o <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

sfdx test2jacoco:convert [-i <string>] [-p <string>] [-o <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

convert the results from running sfdx force:test into jacoco format

USAGE
  $ sfdx test2jacoco:convert [-i <string>] [-p <string>] [-o <string>] [--json] [--loglevel 
  trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

OPTIONS
  -i, --input=input                                                                 the input filename

  -o, --output=output                                                               the file where the output should be
                                                                                    stored

  -p, --project=project                                                             [default: sfdx-project.json] the
                                                                                    sfdx project json to use - will
                                                                                    retrieve package directories

  --json                                                                            format output as json

  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
                                                                                    this command invocation

EXAMPLE
  sfdx test2jacoco:convert --input ./testresults/test-result-7071y00000MJoUt.json --project sfdx-project.json --output 
  ./testresults/codecoverage/jacoco.xml

See code: src/commands/test2jacoco/convert.ts

Debugging your plugin

We recommend using the Visual Studio Code (VS Code) IDE for your plugin development. Included in the .vscode directory of this plugin is a launch.json config file, which allows you to attach a debugger to the node process when running your commands.

To debug the hello:org command: 1. Start the inspector

If you linked your plugin to the sfdx cli, call your command with the dev-suspend switch:

$ sfdx hello:org -u myOrg@example.com --dev-suspend

Alternatively, to call your command using the bin/run script, set the NODE_OPTIONS environment variable to --inspect-brk when starting the debugger:

$ NODE_OPTIONS=--inspect-brk bin/run hello:org -u myOrg@example.com

2. Set some breakpoints in your command code
3. Click on the Debug icon in the Activity Bar on the side of VS Code to open up the Debug view.
4. In the upper left hand corner of VS Code, verify that the "Attach to Remote" launch configuration has been chosen.
5. Hit the green play button to the left of the "Attach to Remote" launch configuration window. The debugger should now be suspended on the first line of the program.
6. Hit the green play button at the top middle of VS Code (this play button will be to the right of the play button that you clicked in step #5). Congrats, you are debugging!