Security News
JavaScript Leaders Demand Oracle Release the JavaScript Trademark
In an open letter, JavaScript community leaders urge Oracle to give up the JavaScript trademark, arguing that it has been effectively abandoned through nonuse.
@jest/test-result
Advanced tools
The @jest/test-result package is part of the Jest testing framework, primarily used to handle and represent the results of tests. It provides structures and utility functions to process and display the outcomes of test suites and individual tests.
Create a test result
This feature allows developers to create a structured test result object, which includes the number of passing, failing, and pending tests, along with detailed results for each test.
{
"numFailingTests": 0,
"numPassingTests": 3,
"numPendingTests": 0,
"testResults": [
{
"fullName": "adds 1 + 2 to equal 3",
"status": "passed"
}
]
}
Summarize test results
This utility function summarizes the test results, providing a quick overview of the test suite's outcome. It's useful for generating reports or logs.
const { summarizeResults } = require('@jest/test-result');
const testResults = {
numFailingTests: 1,
numPassingTests: 2,
numPendingTests: 1,
testResults: [
{ fullName: 'test1', status: 'passed' },
{ fullName: 'test2', status: 'failed' },
{ fullName: 'test3', status: 'pending' }
]
};
console.log(summarizeResults(testResults));
Mocha is a feature-rich JavaScript test framework running on Node.js and in the browser, making asynchronous testing simple and fun. Mocha tests run serially, allowing for flexible and accurate reporting, while mapping uncaught exceptions to the correct test cases. It is similar to @jest/test-result in that it handles test results but is a more comprehensive testing solution.
Chai is a BDD / TDD assertion library for node and the browser that can be delightfully paired with any javascript testing framework. It's similar to @jest/test-result in terms of being used in testing environments but focuses more on assertions rather than handling test results.
25.2.0
[jest-config]
Support ESM config files with .js
extension (#9573).[jest-runtime]
Override module.createRequire
to return a Jest-compatible require
function (#9469)[jest-haste-map]
[BREAKING] Remove mapper
option (#9581)[*]
Support array of paths for moduleNameMapper
aliases (#9465)[jest-reporters]
Adds ability to pass options to the istanbul-reporter through coverageReporters
(#9572)[jest-runtime]
Require stack when a module cannot be resolved (#9681)[jest-transform]
writeCacheFile
no longer calls fsync
(#9695)[expect]
Handle readonly properties correctly (#9575)[jest-cli]
Set coverageProvider
correctly when provided in config (#9562)[jest-cli]
Allow specifying .cjs
and .mjs
config files by --config
CLI option (#9578)[jest-cli]
Update yargs to fix CLI flag overriding (#9519)[jest-config]
Treat setupFilesAfterEnv
like setupFiles
when normalizing configs against presets (#9495)[jest-config]
Support .mjs
config files on Windows as well (#9558)[jest-config]
Verify rootDir
and all roots
are directories (#9569)[jest-config]
Ensure pattern of replacePosixSep
is a string (#9546)[jest-haste-map]
Fix crash on unix based systems without find (#9579)[jest-jasmine2]
Fix --testNamePattern
matching with concurrent
tests (#9090)[jest-matcher-utils]
Fix diff highlight of symbol-keyed object. (#9499)[@jest/reporters]
Notifications should be fire&forget rather than having a timeout (#9567)[jest-resolve]
Fix module identity preservation with symlinks and browser field resolution (#9511)[jest-resolve]
Do not confuse directories with files (#8912)[jest-resolve]
moduleNameMapper
should take precedence over Node core modules (#9563)[jest-runtime]
Reset isolateModules
if it fails (#9541)[jest-runtime]
Yarn PnP errors displayed to the user (#9681)[jest-snapshot]
Downgrade semver to v6 to support node 8 (#9451)[jest-snapshot]
Properly indent new snapshots in the presences of existing ones (#9523)[jest-transform]
Correct sourcemap behavior for transformed and instrumented code (#9460)[jest-transform]
Allow instrumentation of transformed files with weird file extensions (#9589)[@jest/types]
Make ConfigGlobals
an interface to allow for declaration merging. (#9570)[pretty-format]
Export OldPlugin
type (#9491)[docs]
Warn about unexpected behavior / bug of node-notifier when using the notify
options.[docs]
Grammatical corrections to Async docs page. (#9679)[jest-resolver]
Use resolve
package to implement custom module resolution (#9520)[jest-runtime]
Move execution of setupFiles
to jest-runner
(#9596)[jest-runtime]
Update anchor link in helpers
(#9616)[@jest/reporters]
Remove unused dependencies and type exports (#9462)[website]
Update pictures of reports when matchers fail (#9214)[jest-haste-map]
Reduce number of lstat
calls in node crawler (#9514)FAQs
Unknown package
The npm package @jest/test-result receives a total of 27,788,289 weekly downloads. As such, @jest/test-result popularity was classified as popular.
We found that @jest/test-result demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 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.
Security News
In an open letter, JavaScript community leaders urge Oracle to give up the JavaScript trademark, arguing that it has been effectively abandoned through nonuse.
Security News
The initial version of the Socket Python SDK is now on PyPI, enabling developers to more easily interact with the Socket REST API in Python projects.
Security News
Floating dependency ranges in npm can introduce instability and security risks into your project by allowing unverified or incompatible versions to be installed automatically, leading to unpredictable behavior and potential conflicts.