
Security News
Another Round of TEA Protocol Spam Floods npm, But It’s Not a Worm
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.
jupyter-js-auto-test
Advanced tools
This project could scan files under the specific directory and run tests in them. The test report could be print to the terminal or pass to the caller via Callback.
Or you could setup only mode to only run all tests or specific tests a specific file.
To run it, you first need to write test.
You could write test by yourself or use the test template and config to setup tests. Either way require the test functions to be exported and having a callback function as their parameter which will callback(testResult[, errorMessage]).
For example (Write by yourself, it also require chalk.)
const chalk = require('chalk')
module.exports = {
foo
}
function foo(callback) {
if (1 + 1 === 2) {
console.log(chalk.green('Test foo passed'))
callback(true)
} else {
console.log(chalk.red('Test foo failed due to '), 'impossible')
callback(false, 'error message')
}
}
Or you could use test template and config,
module.exports = {
foo2,
}
const { TestFunctionConfig, readConfigAndRun } = require('jupyter-js-auto-test')
// in most case, this obj should be the object about to test
const obj = {
foo2: (callback) => {
if (1 + 1 === 2) {
console.log("Object run foo2")
callback(null)
} else {
console.log("Object run foo2")
callback("impossible")
}
}
}
function foo2(callback) {
readConfigAndRun(
new TestFunctionConfig(obj, 'foo2', [], null),
callback
)
}
More Config examples
// having prerunfuncs
new TestFunctionConfig(
UserLoyaltyLevels,
'getLevel',
[level.LevelID],
null,
[new TestFunctionConfig(UserLoyaltyLevels, 'addLevel', [level.LevelID, level], null)]
)
Once you have your test functions, you can run it.
const { setAndRun } = require('jupyter-js-auto-test')
setAndRun('path/to/directory')
If you have any problems or anything to say, please create an issue at github respo, https://github.com/Jupiter0806/JS_Playground/tree/master/my_node_modules/jupyter-js-auto-test I will try to reply as soon as possible.
FAQs
Auto scan files under the directory and run test in them
We found that jupyter-js-auto-test demonstrated a not healthy version release cadence and project activity because the last version was released 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.

Security News
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.

Security News
PyPI adds Trusted Publishing support for GitLab Self-Managed as adoption reaches 25% of uploads

Research
/Security News
A malicious Chrome extension posing as an Ethereum wallet steals seed phrases by encoding them into Sui transactions, enabling full wallet takeover.