Research
Security News
Threat Actor Exposes Playbook for Exploiting npm to Build Blockchain-Powered Botnets
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
xunit-file
Advanced tools
Basically the same reporter as mocha's xunit reporter, but writes the output in a file.
Basically the same reporter as mocha's xunit reporter, but writes the output to a file.
npm install xunit-file --save-dev
Run mocha with -R xunit-file
or --reporter xunit-file
The xunit.xml output is saved in process.cwd()/xunit.xml
by default.
To change the output and activate terminal output, you can create a config.json
, or use environment variables.
config.json
{
"file" : "xunit.xml",
"consoleOutput" : {
"suite" : true,
"test" : true,
"fail" : false
}
}
environment variables
$ XUNIT_FILE=output/xunit.xml mocha -R xunit-file // writes result to output/xunit.xml
$ LOG_XUNIT=true mocha -R xunit-file // activates terminal output
$ XUNIT_SILENT=true mocha -R xunit-file // disable all terminal output
Set XUNIT_LOG_ENV environment variable, if you want the output process and environment variables in the properties section of the xml file.
$ XUNIT_LOG_ENV=true mocha -R xunit-file
Add the following to the xml report.
<properties>
<property name="process.arch" value="x64"/>
<property name="process.platform" value="win32"/>
<property name="process.memoryUsage" value="[ rss: '26570752', heapTotal: '17734144', heapUsed: '8982088']"/>
<property name="process.cwd" value="D:\Dev\Demo\git\Demo\DemoApp\build\jsTest"/>
<property name="process.execPath" value="D:\Dev\Demo\git\Demo\DemoApp\build\nodeJs\node-v0.11.10-windows-x64\bin\node.exe"/>
<property name="process.version" value="v0.11.10"/>
<property name="process.versions" value="[ http_parser: '2.2', node: '0.11.10', v8: '3.22.24.10', uv: '0.11.17', zlib: '1.2.3', modules: '13', openssl: '1.0.1e']"/>
...
<property name="process.env.NODE_PATH" value="D:\Dev\Demo\git\Demo\DemoApp\build\jsTest\node_modules"/>
<property name="process.env.SUITE_NAME" value="jsTest.myTest"/>
<property name="process.env.XUNIT_FILE" value="D:\Dev\Demo\git\Demo\DemoApp\build\test-results\TEST-jsTest.myTest.xml"/>
<property name="process.env.LOG_XUNIT" value="undefined"/>
</properties>
This reporter is just the original xunit reporter from mocha only writing the result in an xml file.
MIT
FAQs
Basically the same reporter as mocha's xunit reporter, but writes the output in a file.
The npm package xunit-file receives a total of 0 weekly downloads. As such, xunit-file popularity was classified as not popular.
We found that xunit-file demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 9 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
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.