avajs/ava (ava)
Compare Source 
What's Changed
- Keep test worker alive until explicitly freed by @matz3 in #3391 
New Contributors
Full Changelog: avajs/ava@v6.4.0...v6.4.1 
Compare Source 
What's Changed
Interactive watch mode filters
@mmulet did fantastic work to spearhead interactive watch mode filters. You can now filter test files by glob patterns, and tests by matching their titles. It's just like you already could from the CLI itself, but now without exiting AVA 🚀 #3372 
As part of this work we've removed the "sticky" .only() behavior #3381 
Examples
We've been remiss in merging #3335 which updates the examples to use AVA 6. It's done now, examples are up to date and it's all due to @tommy-mitchell 👏
New Contributors
Full Changelog: avajs/ava@v6.3.0...v6.4.0 
Compare Source 
What's Changed
New Contributors
Full Changelog: avajs/ava@v6.2.0...v6.3.0 
Compare Source 
What's Changed
- Add filterNodeArgumentsForWorkerThreadsoption in #3336
- Add Node.js 23 to supported engines (and test matrix) in #3346 
New Contributors
Full Changelog: avajs/ava@v6.1.3...v6.2.0 
Compare Source 
What's Changed
New Contributors
Full Changelog: avajs/ava@v6.1.2...v6.1.3 
Compare Source 
What's Changed
Full Changelog: avajs/ava@v6.1.1...v6.1.2 
Compare Source 
What's Changed
Full Changelog: avajs/ava@v6.1.0...v6.1.1 
Compare Source 
What's Changed
- 
Implement registerCompletionHandler()by @novemberborn in #3283
 AVA 6 expects test code to clean up gracefully when the tests are complete, allowing the test environment (worker thread or child process) to exit. If this does not happen, AVA will report a timeout. You can use registerCompletionHandler()to perform any other clean up (or indeed exit the process) after AVA has completed the test execution. See the description here.
 
- 
Fix potential bug with watch mode when no failed test files are written by @novemberborn in #3287  
- 
Fix ava/internalESM type module by @codetheweb in #3292
 
Full Changelog: avajs/ava@v6.0.1...v6.1.0 
Compare Source 
What's Changed
Full Changelog: avajs/ava@v6.0.0...v6.0.1 
Compare Source 
Breaking Changes
- 
AVA now requires Node.js versions 18.18, 20.8 or 21. Versions 14 and 16 are no longer supported. #3251 #3216  
- 
When tests finish, worker threads or child processes are no longer exited through proces.exit(). If your test file does not exit on its own, the test run will time out. #3260
 
- 
Changes to watch mode #3218: 
- Watch mode can no longer be started via the ava.config.*orpackage.jsonconfiguration.
- The ignoredByWatcherconfiguration has moved to thewatchModeobject, under theignoreChangeskey.
- Watch mode now uses the built-in fs.watch()in recursive mode. This is supported on Linux in Node.js 20 or newer, and MacOS and Windows in Node.js 18 as well. There are caveats to keep in mind.
 
- 
Failed assertions now throw, meaning that any subsequent code is not executed. This also impacts the type definitions. #3246  
- 
Only native errors are now considered errors by the t.throws()andt.throwsAsync()assertions.Object.create(Error.prototype)is not a native error. #3229
 
- 
Changes to modules loaded through the requireconfiguration #3184:
 
- If such modules export a default function, this function is now invoked.
- Local files are loaded through @ava/typescriptif necessary.
 
Improvements
Rewritten watcher
The watcher has been rewritten. It’s now built on fs.watch() in recursive mode.
@vercel/nft is used to perform static dependency analysis, supporting ESM and CJS imports for JavaScript & TypeScript source files. This is a huge improvement over the previous runtime tracking of CJS imports, which did not support ESM.
Integration with @ava/typescript has been improved. The watcher can now detect a change to a TypeScript source file, then wait for the corresponding build output to change before re-running tests.
The ignoredByWatcher configuration has moved to the watchMode object, under the ignoreChanges key.
See #3218 and #3257.
Failed assertions now throw
Assertions now throw a TestFailure error when they fail. This error is not exported or documented and should not be used or thrown manually. You cannot catch this error in order to recover from a failure, use t.try() instead.
All assertions except for t.throws() and t.throwsAsync() now return true when they pass. This is useful for some of the assertions in TypeScript where they can be used as a type guard.
Committing a failed t.try() result now also throws.
See #3246.
t.throws() and t.throwsAsync() can now expect any error
By default, the thrown error (or rejection reason) must be a native error. You can change the assertion to expect any kind of error by setting any: true in the expectation object:
t.throws(() => { throw 'error' }, {any: true})See #3245 by @adiSuper94.
The require configuration is now more powerful
It now loads ES modules.
Local files are loaded through @ava/typescript if necessary, so you can also write these in TypeScript.
If there is a default export function, it is invoked after loading. The function is awaited so it can do asynchronous setup before further modules are loaded. Arguments from the configuration can be passed to the function (as a [structured clone](https://developer.mozilla.org/en-US/docs/Web/API/structuredClone)).
See #3184 by @sculpt0r.
Other changes worth noting
- Internal events can now be observed (experimentally). See #3247 by @codetheweb. It’s experimental and undocumented.
- You can now use t.timeout.clear()to restore a previoust.timeout(). #3221
- Code coverage is flushed to disk at opportune moments. #3220 
New Contributors
Full Changelog: avajs/ava@v5.3.1...v6.0.0 
Compare Source 
What's Changed
Full Changelog: avajs/ava@v5.3.0...v5.3.1 
Compare Source 
What's Changed
New Contributors
Full Changelog: avajs/ava@v5.2.0...v5.3.0 
Compare Source 
What's Changed
New Contributors
Full Changelog: avajs/ava@v5.1.1...v5.2.0 
Compare Source 
What's Changed
Full Changelog: avajs/ava@v5.1.0...v5.1.1 
Compare Source 
What's Changed
- Output logs for tests that remain pending when AVA exits by @kevo1ution in #3125 
- Check for --config file extensions after they fail to load, allowing custom loaders by @panva in #3135 
New Contributors
Full Changelog: avajs/ava@v5.0.1...v5.1.0 
Compare Source 
Despite the major version bump this is a relatively minor release. Node.js 12 is no longer supported. The type definitions are now distributed to be compatible with TypeScript 4.7 or newer.
npm install --save-dev ava
Breaking Changes
- AVA now requires Node.js 14.19, 16.15 or 18. #3043 
- Type definition distribution assumes at least TypeScript 4.7. #3041 
- We're now exporting types rather than interfaces. #3096 
Improvements
New Contributors
Full Changelog: avajs/ava@v4.3.3...v5.0.1 
Compare Source 
Despite the major version bump this is a relatively minor release. Node.js 12 is no longer supported. The type definitions are now distributed to be compatible with TypeScript 4.7 or newer.
It's available as a pre-release under the next tag for the next few weeks:
npm install --save-dev ava@next
Breaking Changes
- AVA now requires Node.js 14.19, 16.15 or 18. #3043 
- Type definition distribution is no longer compatible with TypeScript versions before 4.7. #3041 
- We're now exporting types rather than interfaces. #3096 
Improvements
New Contributors
Full Changelog: avajs/ava@v4.3.3...v5.0.0 
Compare Source 
Add compatibility with Node.js 18.8, thanks @Brooooooklyn #3091.
Full Changelog: avajs/ava@v4.3.1...v4.3.3 
Compare Source 
Compare Source 
What's Changed
- When translating line numbers, check whether the source map entry has original values in #3061 
- Report error when parsing for line number selection in #3062 
New Contributors
Full Changelog: avajs/ava@v4.3.0...v4.3.1 
Compare Source 
What's Changed
- We're now shipping type definitions compatible with TypeScript 4.7, by @RebeccaStevens in #3024 
- throwsand- throwsAsyncassertions now take a function to test error messages, by @il3ven in #2995
- Test failure summaries no longer duplicate t.log()messages, by @il3ven in #3013
- The number of timed-out tests is printed at the end of a run, by @il3ven in #3021 
- We've documented how to load multiple instances of the same "shared" worker, by @codetheweb in #3009 
- Links to translated documentation have been updated, by @forresst in #3037 
- Node.js 17 has been removed from the test matrix, and Node.js 18 added in #3039 
Full Changelog: avajs/ava@v4.2.0...v4.3.0 
Compare Source 
What's Changed
New Contributors
Full Changelog: avajs/ava@v4.1.0...v4.2.0 
Compare Source 
New features
- Allow customized sorting of test files prior to execution using sortTestFiles()inava.config.jsfiles by @erezrokah in #2968
- Warn when unsupported ava.config.jsonfiles are encountered by @razor-x in #2962
- Loosen type constraints for deepEqualassertion by @RebeccaStevens in #2969
Fixes
New Contributors
Full Changelog: avajs/ava@v4.0.1...v4.1.0 
Compare Source 
What's Changed
Full Changelog: avajs/ava@v4.0.0...v4.0.1 
Compare Source 
We're celebrating the new year with the official AVA 4 release! 🎊
The cool new stuff 🆒
Worker threads 🧑💼
By default, test files are now run in worker threads! Huge thanks to @dnlup for landing this.
Test files should run a little quicker, since it's easier to spin up a worker thread than a child process. You can use --no-worker-threads on the command line, or workerThreads: false in your AVA configuration, to fall back to using child processes.
Shared workers are no longer experimental 🎊
Shared workers are no longer experimental. This is a powerful feature that loads a program in a worker thread in AVA's main process and then communicate with code running in the test workers. This enables your tests to better utilize shared resources during a test run, as well as providing opportunities to set up these resources before tests start (or clean them up after).
When you use watch mode, shared workers remain loaded across runs.
Improved test selection 🤳
AVA selects test files based on your package.json or ava.config.* configuration files. When used on the CLI you can then provide patterns to select a subset of these files.
You can now pass a folder and AVA will select the test files contained therein. Or you can provide a specific JavaScript file and AVA will run it even if it wasn’t selected by your configuration.
If AVA finds files based on the configuration, but none of those were selected to the CLI arguments, it now prints a warning.
Better monorepo support 🚝
AVA now looks for ava.config.* files in parent directories, until it finds a directory with a .git directory (or file). This lets you specify AVA configuration at the top of your monorepo and still run AVA from within each package.
New snapshot format 📸
@ninevra has worked tirelessly on landing a new snapshot format. It contains all information necessary to regenerate the report file. This allows for snapshots to be updated even if tests or assertions are skipped.
Previously failing test files run first 🏃
AVA now records which test files failed in the previous run. It then prioritizes testing these files when you run AVA again. Thanks @bunysae!
ESM support 🤾
AVA 4 comes with full ES module support. Both ESM and CJS entrypoints are provided so that you can use it no matter how you manage your project.
The ava.config.js file is now treated as CJS or ESM depending on module type configured in the package.json file. ava.config.mjs is now supported.
If you use JavaScript files with non-standard extensions you can configure AVA to import them.
Note that dependency tracking in watch mode does not yet work with ES modules.
Dedicated macro factory with type inference 🏭
test.macro() returns an object that can be used with test() and hooks. The t.context type is inherited from test. When used with TypeScript this gives much better type inference.
Like with AVA 3, regular functions that also have a title property that is a string-returning function are supported. However the type checking won’t be as good.
Source maps 🗺
AVA now uses the source map support that’s built in to Node.js itself. This should give better stack traces. However we’re not sure yet what happens if you load a program that automatically modifies stack traces.
Line number selection (where npx ava test.js:5 runs the test at line 5) now uses source maps and so should work better with TypeScript files.
Assertions as type guards 💂
Most assertions now return a boolean indicating whether they passed. If you use AVA with TypeScript, you can use this as a type guard. Thanks @jmarkham828!
(This is not supported for t.snapshot() and the "throws" assertions.)
Breaking changes 💥
AVA 4 requires at least Node.js 12.22, 14.17, 16.4 or 17. Node.js 10 is no longer supported.
If installed globally, AVA will no longer use any locally installed version. Install locally and run with npx ava instead. When running test files from another project that also has AVA installed, those test files will now fail to run (because they'll try and use that other AVA version).
Ecosystem 🏞
- Support for @ava/babelhas been removed. We haven’t seen enough contributions to that package to recommend it for AVA 4. We’d be open to reinstating it in the future (just as we’d be open to support any other compilation provider).
- As a consequence, "enhanced assertions" are no longer available.
- AVA 4 requires avajs/typescript@1.1or newer.
- Support for the esmpackage has been removed.
Configuration 🗒
- ava.config.jsnow follows the module type configured in- package.json.
- ava.config.*files may be found that are outside your project directory.
Tests and assertions 🥼
- By default test files execute in worker threads, not child processes.
- test.meta.fileand- test.meta.snapshotDirectoryare now file URL strings.
- Whitespace in test titles is now normalized. This could result in two tests being treated as having the same title, even though they are different in code. Thanks @KillyMXI!
- test()and- t.try()no longer take an array of test implementations. Use a loop instead.
- The t.throws()andt.throwAsync()assertions can no longer be called with anullvalue for the expectations argument.
- test.cb()and- t.end()have been removed. Use async functions and- util.promisify()instead.
- t.teardown()now executes in last-in-first-out order.
Snapshots 📸
- Snapshots recorded using earlier AVA versions are no longer recognized. Run npx ava -uto rebuild your snapshots after upgrading.
- Snapshots no longer recognize React elements, instead we want to provide this functionality through a plugin interface 
- t.snapshot()no longer works in hooks.
- t.snapshot()no longer takes an options argument allowing you to customize the snapshot ID.
TypeScript 🪛
- The instanceOfexpectation oft.throws()andt.throwsAsync()assertions must now be anErrorconstructor.
- You’re expected to use test.macro()when declaring macros.
- Implementation arguments now default to unknown.
- Types have been renamed. MetareplacesMetaInterface, other types withInterfacesuffixes now use theFnsuffix. There may be some other changes too.4b4b2f6
- t.throws()and- t.throwsAsync()return- undefinedwhen the assertion fails. The type definition now matches this behavior.
- Our TypeScript definitions are now tested against TypeScript 4.4
Other changes 🤓
- We’ve removed the non-verbose reporter because it proved too hard to maintain two subtly different reporter outputs. We’d really like to rewrite the reporter. 
- AVA's configuration files may now export promises or asynchronous factory methods.
- The --configargument may now point to a file that is not alongside thepackage.jsonfile.
- When you use t.timeout(), AVA itself won’t time out until your test does. Thanks @OhYash!
- Multi-line snapshot labels now render correctly in Markdown. Thanks @KillyMXI!
- The reporters now clean up .testand.specextensions from file names, as well astest-prefixes.
- Watch mode is better at detecting changes to snapshots and not rerunning tests.
New Contributors
Full changelog since RC 1: avajs/ava@v4.0.0-rc.1...v4.0.0 
Full changelog since AVA 3: avajs/ava@v3.15.0...v4.0.0 
 
Uh oh!
There was an error while loading. Please reload this page.
This PR contains the following updates:
3.15.0->6.4.1Release Notes
avajs/ava (ava)
v6.4.1Compare Source
What's Changed
New Contributors
Full Changelog: avajs/ava@v6.4.0...v6.4.1
v6.4.0Compare Source
What's Changed
Interactive watch mode filters
@mmulet did fantastic work to spearhead interactive watch mode filters. You can now filter test files by glob patterns, and tests by matching their titles. It's just like you already could from the CLI itself, but now without exiting AVA 🚀 #3372
As part of this work we've removed the "sticky"
.only()behavior #3381Examples
We've been remiss in merging #3335 which updates the examples to use AVA 6. It's done now, examples are up to date and it's all due to @tommy-mitchell 👏
New Contributors
Full Changelog: avajs/ava@v6.3.0...v6.4.0
v6.3.0Compare Source
What's Changed
npm auditwarnings by @novemberborn in #3377New Contributors
Full Changelog: avajs/ava@v6.2.0...v6.3.0
v6.2.0Compare Source
What's Changed
filterNodeArgumentsForWorkerThreadsoption in #3336New Contributors
Full Changelog: avajs/ava@v6.1.3...v6.2.0
v6.1.3Compare Source
What's Changed
serialconfiguration option by @turadg in #3321New Contributors
Full Changelog: avajs/ava@v6.1.2...v6.1.3
v6.1.2Compare Source
What's Changed
any: trueby @gibson042 in #3313Full Changelog: avajs/ava@v6.1.1...v6.1.2
v6.1.1Compare Source
What's Changed
Full Changelog: avajs/ava@v6.1.0...v6.1.1
v6.1.0Compare Source
What's Changed
Implement
registerCompletionHandler()by @novemberborn in #3283AVA 6 expects test code to clean up gracefully when the tests are complete, allowing the test environment (worker thread or child process) to exit. If this does not happen, AVA will report a timeout. You can use
registerCompletionHandler()to perform any other clean up (or indeed exit the process) after AVA has completed the test execution. See the description here.Fix potential bug with watch mode when no failed test files are written by @novemberborn in #3287
Fix
ava/internalESM type module by @codetheweb in #3292Full Changelog: avajs/ava@v6.0.1...v6.1.0
v6.0.1Compare Source
What's Changed
Full Changelog: avajs/ava@v6.0.0...v6.0.1
v6.0.0Compare Source
Breaking Changes
AVA now requires Node.js versions 18.18, 20.8 or 21. Versions 14 and 16 are no longer supported. #3251 #3216
When tests finish, worker threads or child processes are no longer exited through
proces.exit(). If your test file does not exit on its own, the test run will time out. #3260Changes to watch mode #3218:
ava.config.*orpackage.jsonconfiguration.ignoredByWatcherconfiguration has moved to thewatchModeobject, under theignoreChangeskey.fs.watch()in recursive mode. This is supported on Linux in Node.js 20 or newer, and MacOS and Windows in Node.js 18 as well. There are caveats to keep in mind.Failed assertions now throw, meaning that any subsequent code is not executed. This also impacts the type definitions. #3246
Only native errors are now considered errors by the
t.throws()andt.throwsAsync()assertions.Object.create(Error.prototype)is not a native error. #3229Changes to modules loaded through the
requireconfiguration #3184:@ava/typescriptif necessary.Improvements
Rewritten watcher
The watcher has been rewritten. It’s now built on
fs.watch()in recursive mode.@vercel/nftis used to perform static dependency analysis, supporting ESM and CJS imports for JavaScript & TypeScript source files. This is a huge improvement over the previous runtime tracking of CJS imports, which did not support ESM.Integration with
@ava/typescripthas been improved. The watcher can now detect a change to a TypeScript source file, then wait for the corresponding build output to change before re-running tests.The ignoredByWatcher configuration has moved to the watchMode object, under the ignoreChanges key.
See #3218 and #3257.
Failed assertions now throw
Assertions now throw a
TestFailureerror when they fail. This error is not exported or documented and should not be used or thrown manually. You cannot catch this error in order to recover from a failure, uset.try()instead.All assertions except for
t.throws()andt.throwsAsync()now returntruewhen they pass. This is useful for some of the assertions in TypeScript where they can be used as a type guard.Committing a failed
t.try()result now also throws.See #3246.
t.throws()andt.throwsAsync()can now expect any errorBy default, the thrown error (or rejection reason) must be a native error. You can change the assertion to expect any kind of error by setting
any: truein the expectation object:See #3245 by @adiSuper94.
The
requireconfiguration is now more powerfulIt now loads ES modules.
Local files are loaded through
@ava/typescriptif necessary, so you can also write these in TypeScript.If there is a default export function, it is invoked after loading. The function is awaited so it can do asynchronous setup before further modules are loaded. Arguments from the configuration can be passed to the function (as a [structured clone](https://developer.mozilla.org/en-US/docs/Web/API/structuredClone)).
See #3184 by @sculpt0r.
Other changes worth noting
t.timeout.clear()to restore a previoust.timeout(). #3221New Contributors
Full Changelog: avajs/ava@v5.3.1...v6.0.0
v5.3.1Compare Source
What's Changed
t.like()to support Symbol keys and ignore non-enumerable properties by @gibson042 in #3209t.like()by @novemberborn in #3212Full Changelog: avajs/ava@v5.3.0...v5.3.1
v5.3.0Compare Source
What's Changed
t.like()assertions by @tommy-mitchell in #3185expectandassert) and use their formatting by @Irvenae in #3187New Contributors
Full Changelog: avajs/ava@v5.2.0...v5.3.0
v5.2.0Compare Source
What's Changed
New Contributors
Full Changelog: avajs/ava@v5.1.1...v5.2.0
v5.1.1Compare Source
What's Changed
Full Changelog: avajs/ava@v5.1.0...v5.1.1
v5.1.0Compare Source
What's Changed
New Contributors
Full Changelog: avajs/ava@v5.0.1...v5.1.0
v5.0.1Compare Source
Despite the major version bump this is a relatively minor release. Node.js 12 is no longer supported. The type definitions are now distributed to be compatible with TypeScript 4.7 or newer.
npm install --save-dev avaBreaking Changes
Improvements
process.exit()called from tests by @gibson042 in #3080os.cpus()returning an empty array on unsupported platforms by @catink123 in #3095New Contributors
Full Changelog: avajs/ava@v4.3.3...v5.0.1
v5.0.0Compare Source
Despite the major version bump this is a relatively minor release. Node.js 12 is no longer supported. The type definitions are now distributed to be compatible with TypeScript 4.7 or newer.
It's available as a pre-release under the
nexttag for the next few weeks:npm install --save-dev ava@nextBreaking Changes
Improvements
process.exit()called from tests by @gibson042 in #3080os.cpus()returning an empty array on unsupported platforms by @catink123 in #3095New Contributors
Full Changelog: avajs/ava@v4.3.3...v5.0.0
v4.3.3Compare Source
Add compatibility with Node.js 18.8, thanks @Brooooooklyn #3091.
Full Changelog: avajs/ava@v4.3.1...v4.3.3
v4.3.2Compare Source
v4.3.1Compare Source
What's Changed
New Contributors
Full Changelog: avajs/ava@v4.3.0...v4.3.1
v4.3.0Compare Source
What's Changed
throwsandthrowsAsyncassertions now take a function to test error messages, by @il3ven in #2995t.log()messages, by @il3ven in #3013Full Changelog: avajs/ava@v4.2.0...v4.3.0
v4.2.0Compare Source
What's Changed
New Contributors
Full Changelog: avajs/ava@v4.1.0...v4.2.0
v4.1.0Compare Source
New features
sortTestFiles()inava.config.jsfiles by @erezrokah in #2968ava.config.jsonfiles are encountered by @razor-x in #2962deepEqualassertion by @RebeccaStevens in #2969Fixes
ava --versionworks again by @novemberborn in #2961New Contributors
Full Changelog: avajs/ava@v4.0.1...v4.1.0
v4.0.1Compare Source
What's Changed
Full Changelog: avajs/ava@v4.0.0...v4.0.1
v4.0.0: AVA 4Compare Source
We're celebrating the new year with the official AVA 4 release! 🎊
npm install -D avaThe cool new stuff 🆒
Worker threads 🧑💼
By default, test files are now run in worker threads! Huge thanks to @dnlup for landing this.
Test files should run a little quicker, since it's easier to spin up a worker thread than a child process. You can use
--no-worker-threadson the command line, orworkerThreads: falsein your AVA configuration, to fall back to using child processes.Shared workers are no longer experimental 🎊
Shared workers are no longer experimental. This is a powerful feature that loads a program in a worker thread in AVA's main process and then communicate with code running in the test workers. This enables your tests to better utilize shared resources during a test run, as well as providing opportunities to set up these resources before tests start (or clean them up after).
When you use watch mode, shared workers remain loaded across runs.
Improved test selection 🤳
AVA selects test files based on your
package.jsonorava.config.*configuration files. When used on the CLI you can then provide patterns to select a subset of these files.You can now pass a folder and AVA will select the test files contained therein. Or you can provide a specific JavaScript file and AVA will run it even if it wasn’t selected by your configuration.
If AVA finds files based on the configuration, but none of those were selected to the CLI arguments, it now prints a warning.
Better monorepo support 🚝
AVA now looks for
ava.config.*files in parent directories, until it finds a directory with a.gitdirectory (or file). This lets you specify AVA configuration at the top of your monorepo and still run AVA from within each package.New snapshot format 📸
@ninevra has worked tirelessly on landing a new snapshot format. It contains all information necessary to regenerate the report file. This allows for snapshots to be updated even if tests or assertions are skipped.
Previously failing test files run first 🏃
AVA now records which test files failed in the previous run. It then prioritizes testing these files when you run AVA again. Thanks @bunysae!
ESM support 🤾
AVA 4 comes with full ES module support. Both ESM and CJS entrypoints are provided so that you can use it no matter how you manage your project.
The
ava.config.jsfile is now treated as CJS or ESM depending on module type configured in thepackage.jsonfile.ava.config.mjsis now supported.If you use JavaScript files with non-standard extensions you can configure AVA to import them.
Note that dependency tracking in watch mode does not yet work with ES modules.
Dedicated macro factory with type inference 🏭
test.macro()returns an object that can be used withtest()and hooks. Thet.contexttype is inherited fromtest. When used with TypeScript this gives much better type inference.Like with AVA 3, regular functions that also have a
titleproperty that is a string-returning function are supported. However the type checking won’t be as good.Source maps 🗺
AVA now uses the source map support that’s built in to Node.js itself. This should give better stack traces. However we’re not sure yet what happens if you load a program that automatically modifies stack traces.
Line number selection (where
npx ava test.js:5runs the test at line 5) now uses source maps and so should work better with TypeScript files.Assertions as type guards 💂
Most assertions now return a boolean indicating whether they passed. If you use AVA with TypeScript, you can use this as a type guard. Thanks @jmarkham828!
(This is not supported for
t.snapshot()and the "throws" assertions.)Breaking changes 💥
AVA 4 requires at least Node.js 12.22, 14.17, 16.4 or 17. Node.js 10 is no longer supported.
If installed globally, AVA will no longer use any locally installed version. Install locally and run with
npx avainstead. When running test files from another project that also has AVA installed, those test files will now fail to run (because they'll try and use that other AVA version).Ecosystem 🏞
@ava/babelhas been removed. We haven’t seen enough contributions to that package to recommend it for AVA 4. We’d be open to reinstating it in the future (just as we’d be open to support any other compilation provider).avajs/typescript@1.1or newer.esmpackage has been removed.Configuration 🗒
ava.config.jsnow follows the module type configured inpackage.json.ava.config.*files may be found that are outside your project directory.Tests and assertions 🥼
test.meta.fileandtest.meta.snapshotDirectoryare now file URL strings.test()andt.try()no longer take an array of test implementations. Use a loop instead.t.throws()andt.throwAsync()assertions can no longer be called with anullvalue for the expectations argument.test.cb()andt.end()have been removed. Use async functions andutil.promisify()instead.t.teardown()now executes in last-in-first-out order.Snapshots 📸
npx ava -uto rebuild your snapshots after upgrading.t.snapshot()no longer works in hooks.t.snapshot()no longer takes an options argument allowing you to customize the snapshot ID.TypeScript 🪛
instanceOfexpectation oft.throws()andt.throwsAsync()assertions must now be anErrorconstructor.test.macro()when declaring macros.unknown.MetareplacesMetaInterface, other types withInterfacesuffixes now use theFnsuffix. There may be some other changes too.4b4b2f6t.throws()andt.throwsAsync()returnundefinedwhen the assertion fails. The type definition now matches this behavior.Other changes 🤓
--configargument may now point to a file that is not alongside thepackage.jsonfile.t.timeout(), AVA itself won’t time out until your test does. Thanks @OhYash!.testand.specextensions from file names, as well astest-prefixes.New Contributors
Full changelog since RC 1: avajs/ava@v4.0.0-rc.1...v4.0.0
Full changelog since AVA 3: avajs/ava@v3.15.0...v4.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.