
Research
Malicious npm Packages Impersonate Flashbots SDKs, Targeting Ethereum Wallet Credentials
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
mocha-ctrf-json-reporter
Advanced tools
Save Mocha test results as a JSON file
A Mocha JSON test reporter to create test reports that follow the CTRF standard.
Common Test Report Format ensures the generation of uniform JSON test reports, independent of programming languages or test framework in use.
Maintained by Matthew Thomas
Contributions are very welcome!
Explore more integrations
{
"results": {
"tool": {
"name": "mocha"
},
"summary": {
"tests": 1,
"passed": 1,
"failed": 0,
"pending": 0,
"skipped": 0,
"other": 0,
"start": 1706828654274,
"stop": 1706828655782
},
"tests": [
{
"name": "ctrf should generate the same report with any tool",
"status": "passed",
"duration": 100
}
],
"environment": {
"appName": "MyApp",
"buildName": "MyBuild",
"buildNumber": "1"
}
}
}
npm install --save-dev mocha-ctrf-json-reporter
You can configure Mocha to use mocha-ctrf-json-reporter in several ways: through .mocharc.js, .mocharc.json, or via the command line. Below are the instructions for each method:
Update your .mocharc.js file as follows:
module.exports = {
reporter: 'mocha-ctrf-json-reporter',
}
Using .mocharc.json, update your config file as follows:
{
"reporter": "mocha-ctrf-json-reporter"
}
Run your tests as you normally would:
npx mocha
You'll find a JSON file named ctrf-report.json
in the ctrf
directory.
You can also specify the reporter from the command line:
mocha --reporter mocha-ctrf-json-reporter
The reporter supports several configuration options, update your .mocharc.js
{
reporter: "mocha-ctrf-json-reporter",
reporterOptions: {
outputFile: 'custom-name.json', // Optional: Output file name. Defaults to 'ctrf-report.json'.
outputDir: 'custom-directory', // Optional: Output directory path. Defaults to 'ctrf'.
appName: 'MyApp', // Optional: Specify the name of the application under test.
appVersion: '1.0.0', // Optional: Specify the version of the application under test.
osPlatform: 'linux', // Optional: Specify the OS platform.
osRelease: '18.04', // Optional: Specify the OS release version.
osVersion: '5.4.0', // Optional: Specify the OS version.
buildName: 'MyApp Build', // Optional: Specify the build name.
buildNumber: '100', // Optional: Specify the build number.
buildName: 'MyApp Build', // Optional: Specify the build name.
buildUrl: "https://ctrf.io", // Optional: Specify the build url.
repositoryName: "ctrf-json", // Optional: Specify the repository name.
repositoryUrl: "https://gh.io", // Optional: Specify the repository url.
branchName: "main", // Optional: Specify the branch name.
testEnvironment: "staging" // Optional: Specify the test environment (e.g. staging, production).
}
},
For .mocharc.json
{
"reporter": "mocha-ctrf-json-reporter",
"reporterOptions": {
"outputFile": "custom-name.json"
}
}
Alternatively, you can pass the reporter options via the command line when running your Mocha tests. Use the --reporter-options flag followed by the options in a key=value format, separated by commas:
npx mocha --reporter mocha-ctrf-json-reporter --reporter-options "outputFile=custom-name.json,outputDir=custom-directory,appName=MyApp,appVersion=1.0.0"
Results JSON filename can contain [hash]
, e.g. ./path_to_your/test-results.[hash].json
. [hash]
is replaced by MD5 hash of test results JSON. This enables support of parallel execution of multiple mocha-ctrf-json-reporter
's writing test results in separate files.
The test object in the report includes the following CTRF properties:
Name | Type | Required | Details |
---|---|---|---|
name | String | Required | The name of the test. |
status | String | Required | The outcome of the test. One of: passed , failed , skipped , pending , other . |
duration | Number | Required | The time taken for the test execution, in milliseconds. |
message | String | Optional | The failure message if the test failed. |
trace | String | Optional | The stack trace captured if the test failed. |
start | Number | Optional | The start time of the test as a Unix epoch timestamp. |
stop | Number | Optional | The end time of the test as a Unix epoch timestamp. |
rawStatus | String | Optional | The original playwright status of the test before mapping to CTRF status. |
filePath | String | Optional | The file path where the test is located in the project. |
retries | Number | Optional | The number of retries attempted for the test. |
flaky | Boolean | Optional | Indicates whether the test result is flaky. |
CTRF is a universal JSON test report schema that addresses the lack of a standardized format for JSON test reports.
Consistency Across Tools: Different testing tools and frameworks often produce reports in varied formats. CTRF ensures a uniform structure, making it easier to understand and compare reports, regardless of the testing tool used.
Language and Framework Agnostic: It provides a universal reporting schema that works seamlessly with any programming language and testing framework.
Facilitates Better Analysis: With a standardized format, programatically analyzing test outcomes across multiple platforms becomes more straightforward.
If you find this project useful, consider giving it a GitHub star ⭐ It means a lot to us.
FAQs
A Mocha test reporter to create test results reports
The npm package mocha-ctrf-json-reporter receives a total of 9,628 weekly downloads. As such, mocha-ctrf-json-reporter popularity was classified as popular.
We found that mocha-ctrf-json-reporter demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer 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
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.