ava
8.4.0 · 7 Nov 2026MIT575.3k / weekRepositoryHomepagenpmAtom feed
112 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 8.x · latest line
8.4.0
7 Nov 2026Summary· from the note as AI read it
Nothing to change: 2 new, 1 fixed.
What's Changed
Report how many snapshots were updated or removed
Don't confuse ENOENT thrown by config code with the config file not existing
Expose debugging state in test.meta.debugMode
8.3.0
31 Oct 2026Summary· from the note as AI read it
Nothing to change: 0 new, 3 fixed.
What's Changed
Avoid re-entry of test finish logic, ensuring teardowns run only once
Update TypeScript documentation
Make
timeoutwork for synchronous testsFix incorrect removal of
test-from test title prefixes
8.2.0
27 Oct 2026Summary· from the note as AI read it
Nothing to change: 0 new, 5 fixed.
What's Changed
Improve
t.throwsmessage when function doesn't throwReport timeouts without crashing the TAP reporter
Guard against undefined variable when test file selection throws
Fix TAP reporter assertion locations
8.1.2
23 Oct 2026Switch back to long-hand form for the package.json repository field
This is a patch release to fix some npm metadata.
What's Changed
Switch back to long-hand form for the package.json repository field
8.1.1
22 Oct 2026This is a patch release to fix some npm metadata. I've included a wider dependency update, but there's no changed functionality.
This is a patch release to fix some npm metadata. I've included a wider dependency update, but there's no changed functionality.
8.1.0
18 Oct 2026~40% faster for many small test files (startup-bound)
~30% faster for a single file with thousands of tests
~50% faster for many files run concurrently
Code block formatting for string snapshots
This release adds an overload for
t.snapshot():t.snapshot(expected, {formatAsCodeBlock}, message?)The overload is only accepted when
expectedis a string. The string is stored verbatim and rendered as a fenced code block in the resulting.snap.mdfile. SetformatAsCodeBlocktotruefor a generic code block, or a non-empty language identifier string for syntax highlighting:test('generates code', t => { const code = generate(); t.snapshot(code, {formatAsCodeBlock: 'js'}); });The resulting snapshots can only be read with AVA 8.1 or newer, but snapshots that do not contain code blocks are backwards compatible. And existing snapshots can still be read, of course.
Performance improvements
~40% faster for many small test files (startup-bound)
~30% faster for a single file with thousands of tests
~50% faster for many files run concurrently
8.0.2
15 Oct 2026Correct link to
CODE_OF_CONDUCT.mdinCONTRIBUTING.mdUpgrade @ava/test to 8.0.1; upgrade tap; refresh reporter logs; snapshot Node.js 26 external assertions
Update tooling, dependencies, formatting and CI workflows
This is a patch release to get CI green again. More goodies are coming.
What's Changed
Correct link to
CODE_OF_CONDUCT.mdinCONTRIBUTING.mdUpgrade @ava/test to 8.0.1; upgrade tap; refresh reporter logs; snapshot Node.js 26 external assertions
Update tooling, dependencies, formatting and CI workflows
8.0.1
17 May 2026This release officially adds Node.js 26 support, with thanks to @novemberborn in #3450.
What's Changed
This release officially adds Node.js 26 support, with thanks to @novemberborn in #3450.
Per our policy, support for Node.js 25 has been removed.
8.0.0
27 Apr 2026Watch mode now ignores changes to
*.tsbuildinfofilesTAP reporter is more defensive when restoring the original error name, thanks to @ninper00
Reported errors when
throwsAsync/notThrowsAsyncare not awaited have been improved
Breaking Changes
AVA now expects Node.js 22.20, 24.12 or newer.
Internally AVA is now fully ESM. This is possible now that Node.js supports loading ES modules using
require()calls and simplifies AVA's types and internals.If you use AVA from a CommonJS project you'll have to update your imports:
-const test = require('ava'); +const {default: test} = require('ava');We expect an increasing number of projects to be ESM only. As per the above, CommonJS is still supported, but we don't expect
cjsextensions to be used. The default file extensions are nowjsandmjs. Specifyextensions: ['cjs', 'js', 'mjs']for AVA to run test files with thecjsextension.All test files (and those loaded through AVA's
requireconfig) are now loaded viaimport(). Use customization hooks for transpilation. The object form of theextensionsconfiguration is no longer supported.If you use AVA with @ava/typescript you must upgrade that package to v7.
New Features
There's two new test modifiers courtesy of @sindresorhus:
test.skipIf()to skip a test based on a runtime condition.test.runIf()is the inverse: the test only runs when the condition is true.test.skipIf(process.platform === 'win32')('not on Windows', t => { t.pass(); }); test.runIf(process.platform === 'linux')('Linux only', t => { t.pass(); });These work with other modifiers like
.serialand.failing:test.serial.skipIf(process.platform === 'win32')('serial, not on Windows', t => { t.pass(); }); test.failing.skipIf(process.platform === 'win32')('expected failure, not on Windows', t => { t.fail(); });Other Changes
Watch mode now ignores changes to
*.tsbuildinfofilesTAP reporter is more defensive when restoring the original error name, thanks to @ninper00
Reported errors when
throwsAsync/notThrowsAsyncare not awaited have been improved
- 7.x
7.0.0
27 Feb 2026- Removed
Remove support for Node.js 18 and 23; require 20.19 or newer, 22.20 or newer or 24,12 or newer; update dependencies including transitive
glob Replace
strip-ansiwithnode:util.stripVTControlCharacters
- 6.x
6.4.1
12 Jul 2025Keep test worker alive until explicitly freed
6.4.0
7 Jun 2025AVA is now tested with Node.js 24 (but no longer v23) #3379
We're now publishing to npm with provenance attestations #3385
What's Changed
AVA is now tested with Node.js 24 (but no longer v23) #3379
We're now publishing to npm with provenance attestations #3385
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 👏
6.3.0
2 May 2025Do not count writes to stdout/stderr as non-idling activity for timeouts
What's Changed
Do not count writes to stdout/stderr as non-idling activity for timeouts
6.2.0
27 Oct 2024Add
filterNodeArgumentsForWorkerThreadsoptionAdd Node.js 23 to supported engines (and test matrix)
6.1.3
5 May 2024Include Node.js 22 in supported engines and test matrix
Add VS Code debugging instructions for Yarn PnP projects
Document
serialconfiguration option
6.1.2
28 Feb 2024Fix throws assertions rejecting falsy values when
any: true
6.1.1
29 Jan 2024Fix 'previous failures' in watch mode always incrementing
6.1.0
21 Jan 2024Implement
registerCompletionHandler()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
Fix
ava/internalESM type module
6.0.1
6 Dec 2023Maintenance only: docs, tests, build or refactoring. Nothing changes in how you use it.
6.0.0
4 Dec 2023- Breaking
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 - Breaking
Changes to watch mode #3218:
Breaking Changes
- Breaking
AVA now requires Node.js versions 18.18, 20.8 or 21. Versions 14 and 16 are no longer supported. #3251 #3216
- Breaking
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 - Breaking
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.
- Breaking
Failed assertions now throw, meaning that any subsequent code is not executed. This also impacts the type definitions. #3246
- Breaking
Only native errors are now considered errors by the
t.throws()andt.throwsAsync()assertions.Object.create(Error.prototype)is not a native error. #3229 - Breaking
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/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.
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:t.throws(() => { throw 'error' }, {any: true})See #3245
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](developer.mozilla.org/en-US/docs/Web/API/struct…)).
See #3184
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(). #3221Code coverage is flushed to disk at opportune moments. #3220
- 5.x
5.3.1
16 Jun 2023Update
t.like()to support Symbol keys and ignore non-enumerable propertiesFix circular selector detection in
t.like()
5.3.0
25 May 2023Support arrays in
t.like()assertionsRecognize typical assertion errors (
expectandassert) and use their formatting
5.2.0
6 Feb 2023Infer thrown error from expectations
5.1.1
15 Jan 2023Fix de-registration of shared workers to ensure AVA exits correctly, by @codetheweb in #3149 & #3151
5.1.0
14 Nov 2022Output logs for tests that remain pending when AVA exits
Check for --config file extensions after they fail to load, allowing custom loaders
5.0.1
25 Sep 2022- Breaking
AVA now requires Node.js 14.19, 16.15 or 18. #3043
- Breaking
Type definition distribution assumes at least TypeScript 4.7. #3041
- Breaking
We're now exporting types rather than interfaces. #3096
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
- Breaking
AVA now requires Node.js 14.19, 16.15 or 18. #3043
- Breaking
Type definition distribution assumes at least TypeScript 4.7. #3041
- Breaking
We're now exporting types rather than interfaces. #3096
Improvements
Detect
process.exit()called from testsImprove test result accessibility
Parse for line numbers with latest supported ECMA version
Work around
os.cpus()returning an empty array on unsupported platformsCount timeouts separately from the timed out tests
Cap idle timeouts to the maximum possible value
5.0.0
4 Sep 2022- Breaking
AVA now requires Node.js 14.19, 16.15 or 18. #3043
- Breaking
Type definition distribution is no longer compatible with TypeScript versions before 4.7. #3041
- Breaking
We're now exporting types rather than interfaces. #3096
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@next
Breaking Changes
- Breaking
AVA now requires Node.js 14.19, 16.15 or 18. #3043
- Breaking
Type definition distribution is no longer compatible with TypeScript versions before 4.7. #3041
- Breaking
We're now exporting types rather than interfaces. #3096
Improvements
Detect
process.exit()called from testsImprove test result accessibility
Parse for line numbers with latest supported ECMA version
Work around
os.cpus()returning an empty array on unsupported platformsCount timeouts separately from the timed out tests
- 4.x
4.3.3
25 Aug 2022Add compatibility with Node.js 18.8, thanks @Brooooooklyn #3091.
4.3.2
25 Aug 20224.3.1
10 Jul 2022When translating line numbers, check whether the source map entry has original values
Report error when parsing for line number selection
4.3.0
2 Jun 2022We're now shipping type definitions compatible with TypeScript 4.7,
throwsandthrowsAsyncassertions now take a function to test error messages,Test failure summaries no longer duplicate
t.log()messages,
What's Changed
We're now shipping type definitions compatible with TypeScript 4.7,
throwsandthrowsAsyncassertions now take a function to test error messages,Test failure summaries no longer duplicate
t.log()messages,The number of timed-out tests is printed at the end of a run,
We've documented how to load multiple instances of the same "shared" worker,
Links to translated documentation have been updated,
Node.js 17 has been removed from the test matrix, and Node.js 18 added
4.2.0
10 Apr 2022Update Babel recipe for AVA 4
Document how GitHub Actions can be configured for parallel builds
Allow parallel builds to be disabled
What's Changed
Update Babel recipe for AVA 4
Document how GitHub Actions can be configured for parallel builds
Allow parallel builds to be disabled
Improve typing of teardown methods
4.1.0
6 Mar 2022Allow customized sorting of test files prior to execution using
sortTestFiles()inava.config.jsfilesWarn when unsupported
ava.config.jsonfiles are encounteredLoosen type constraints for
deepEqualassertion
New features
Allow customized sorting of test files prior to execution using
sortTestFiles()inava.config.jsfilesWarn when unsupported
ava.config.jsonfiles are encounteredLoosen type constraints for
deepEqualassertion
Fixes
ava --versionworks again
4.0.1
8 Jan 2022Fix encoding of large snapshot data
4.0.0
3 Jan 2022- Breaking
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). - Breaking
As a consequence, “enhanced assertions” are no longer available.
- Breaking
AVA 4 requires
avajs/typescript@1.1or newer.
We're celebrating the new year with the official AVA 4 release! 🎊
npm install -D ava
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-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
- Breaking
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). - Breaking
As a consequence, “enhanced assertions” are no longer available.
- Breaking
AVA 4 requires
avajs/typescript@1.1or newer. - Breaking
Support for the
esmpackage has been removed.
Configuration
- Breaking
ava.config.jsnow follows the module type configured inpackage.json. - Breaking
ava.config.*files may be found that are outside your project directory.
Snapshots
- Breaking
Snapshots recorded using earlier AVA versions are no longer recognized. Run
npx ava -uto rebuild your snapshots after upgrading. - Breaking
Snapshots no longer recognize React elements, instead we want to provide this functionality through a plugin interface
- Breaking
t.snapshot()no longer works in hooks. - Breaking
t.snapshot()no longer takes an options argument allowing you to customize the snapshot ID.
TypeScript
- Breaking
The
instanceOfexpectation oft.throws()andt.throwsAsync()assertions must now be anErrorconstructor. - Breaking
You’re expected to use
test.macro()when declaring macros. - Breaking
Implementation arguments now default to
unknown. - Breaking
Types have been renamed.
MetareplacesMetaInterface, other types withInterfacesuffixes now use theFnsuffix. There may be some other changes too. 4b4b2f6 - Breaking
t.throws()andt.throwsAsync()returnundefinedwhen the assertion fails. The type definition now matches this behavior. - Breaking
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.
- 3.x
3.15.0
1 Jan 2021When you stop using snapshots in a test file, the next time you run
ava --update-snapshotswe'll remove the left-over snapshot files. Thanks @ninevra! 4f093abAutomatic snapshot file removal
When you stop using snapshots in a test file, the next time you run
ava --update-snapshotswe'll remove the left-over snapshot files. Thanks @ninevra! 4f093abTAP improvements
@tymfear has been on a roll improving our TAP reporter.
t.log()output is now compliant with the spec 99ab93a. Tests that did not run due to timeouts are now reported 98595da.Next-generation configuration
AVA 4 will add full support for ESM configuration files as well as allowing you to have asynchronous factory functions a2f2614. If you're using Node.js 12 or later you can opt-in to these features in AVA 3 by enabling the
nextGenConfigexperiment. Say in anava.config.mjsfile:export default { nonSemVerExperiments: { nextGenConfig: true }, files: ['unit-tests/**/*] };This also allows you to pass an
.mjsfile using the--configargument.With this experiment enabled, AVA will no longer have special treatment for
ava.config.jsfiles. Instead AVA follows Node.js' behavior, so if you've set"type": "module"you must use ESM, and otherwise you must use CommonJS.You mustn't have an
ava.config.mjsfile next to anava.config.jsorava.config.cjsfile.See v3.14.0...v3.15.0 for all changes.
3.14.0
7 Dec 2020With this release, snapshot files are now ordered based on test declaration, not completion. This makes it easier to compare the human-readable reports to your test file, and also stops the
.snapfrom changing when the reports themselves don't. You'll want to rebuild snapshots after upgrading to this release to isolate any changes. Thanks @ninevra! e66b54cSnapshot ordering
With this release, snapshot files are now ordered based on test declaration, not completion. This makes it easier to compare the human-readable reports to your test file, and also stops the
.snapfrom changing when the reports themselves don't. You'll want to rebuild snapshots after upgrading to this release to isolate any changes. Thanks @ninevra! e66b54cShared workers
We’ve been working on making AVA more extensible. One major step on this path is our new shared worker support: run code in the main process, communicate with test workers and influence execution. Find out more in our shared workers recipe.
See v3.13.0...v3.14.0 for all changes.
3.13.0
27 Sep 2020In AVA 4, you'll no longer be able to pass
nullas the expectation fort.throws()&t.throwsAsync(). You can opt in to this early by enabling thedisableNullExpectationsexperiment. Thanks @JSimoni42! f328a69The Enzyme recipe has been updated. Thanks @jonathansamines! db5d2c3
t.passedcan now be used in tests and teardown functions. Thanks @tymfear! 900dc6dIn AVA 4, you'll no longer be able to pass
nullas the expectation fort.throws()&t.throwsAsync(). You can opt in to this early by enabling thedisableNullExpectationsexperiment. Thanks @JSimoni42! f328a69The Enzyme recipe has been updated. Thanks @jonathansamines! db5d2c3
The TypeScript recipe has been updated. Thanks @SephReed! a3379fa
See v3.12.1...v3.13.0 for all changes.
3.12.1
24 Aug 2020Normally, AVA loads all files as CommonJS, except for
mjsfiles and if you've configured"type": "module"in yourpackage.json.Configure how AVA loads test files
Normally, AVA loads all files as CommonJS, except for
mjsfiles and if you've configured"type": "module"in yourpackage.json.As an experiment, you can now configure how AVA loads other file extensions. This is useful if you want to use Node.js' experimental loaders feature. Read more in our documentation. Thank you @macarie for working on this! 5c9dbb9
Comparison bugfix
There was a bug in our comparison library which meant that negative-index properties on lists were not compared. This was fixed in a patch release, which will definitely be installed when you install AVA 3.12. Your tests may have been passing, even though they should have been failing. They'll fail now. Snapshots may also be different, causing tests to fail.
All changes
See v3.11.1...v3.12.1 for all changes.
3.12.0
23 Aug 20203.11.1
3 Aug 2020This release fixes corrupted output of the default reporter when test or program code writes to standard out. 5ddc9fd
This release fixes corrupted output of the default reporter when test or program code writes to standard out. 5ddc9fd
Also, thanks to @jonathansamines we've taken another step to using AVA to test AVA. 1150991
See v3.11.0...v3.11.1 for all changes.
3.11.0
27 Jul 2020In the following example, the
mapproperty ofvaluemust be deeply equal to that ofselector. Howevernested.quxis ignored, because it's not inselector.New
t.like()assertionIn the following example, the
mapproperty ofvaluemust be deeply equal to that ofselector. Howevernested.quxis ignored, because it's not inselector.t.like({ map: new Map([['foo', 'bar']]), nested: { baz: 'thud', qux: 'quux' } }, { map: new Map([['foo', 'bar']]), nested: { baz: 'thud', } })Read more in the
t.like()assertion documentation.This assertion was previously introduced as an experiment.
VSCode 1.47 debugging improvements
You can now debug tests using the new JavaScript Debug Terminal in VSCode 1.47. We've updated our debugging recipe accordingly. Thank you @connor4312 for the documentation updates and your work on VSCode! bc39bcc
All changes
See v3.10.1...v3.11.0 for all changes.
3.10.1
7 Jul 2020When executing a subset of tests, through
--matchor or.only()or.skip(), you can no longer also update snapshots. This prevents you from accidentally deleting snapshots. Thank you @bunysae for putting this together. f72fab4It's time for another AVA release
Restricting when you can update snapshots
When executing a subset of tests, through
--matchor or.only()or.skip(), you can no longer also update snapshots. This prevents you from accidentally deleting snapshots. Thank you @bunysae for putting this together. f72fab4If you are skipping a test that you can't immediately fix, but you still need to update snapshots, use
.failing()instead.Support for message strings in
t.timeout()callstest('foo', t => { t.timeout(100, 'make sure database has started'); // Write your assertions here });t.try()does not work in hookst.try()has never worked in hooks, but thanks to @okyantoro it now fails properly instead of crashing. d01db61t.snapshot()does not really work in hooks eithert.snapshot()sort of works in hooks, but we'll be removing this in AVA 4. You can opt in to this behavior by enabling thedisableSnapshotsInHooksexperiment. Again thank you @okyantoro d01db61.Fixed TypeScript definition for
t.like()The experimental
t.like()assertion should now work better with TypeScript.All changes
See v3.9.0...v3.10.1 for all changes.
3.10.0
5 Jul 20203.9.0
14 Jun 2020In the following example, the
mapproperty ofvaluemust be deeply equal to that ofselector. Howevernested.quxis ignored, because it's not inselector.New experiments!
In the following example, the
mapproperty ofvaluemust be deeply equal to that ofselector. Howevernested.quxis ignored, because it's not inselector.t.like({ map: new Map([['foo', 'bar']]), nested: { baz: 'thud', qux: 'quux' } }, { map: new Map([['foo', 'bar']]), nested: { baz: 'thud', } })Read more in the
t.like()assertion documentation and let us know what you think.@yjpa7145 has contributed an experiment to reverse the order in which
t.teardown()functions are run, so that the last registered function is called first 952a017. This will be the behavior in AVA 4.To enable both these experiments update your AVA configuration:
package.json:{ "ava": { "nonSemVerExperiments": { "likeAssertion": true, "reverseTeardowns": true } } }ava.config.js:export default { nonSemVerExperiments: { likeAssertion: true, reverseTeardowns: true } }Reporter changes
@Michael55555 has helped us combine our reporter code into a single file b3866b6. We've also made some other tweaks and improvements baaf99a. Let us know if anything seems amiss.
Improved diffs
@bunysae made it so that missing or extraneous objects in diffs are printed with extra depth #62.
Farewell Node.js 13
Node.js 13 has reached end-of-life. Per our support statement we have removed it from our test matrix and supported version list.
All changes
See v3.8.2...v3.9.0 for all changes. Thank you @paulrobertlloyd and @Autre31415 for contributing documentation improvements.
3.8.1
27 Apr 2020Node.js 14 support
Great news, this is a feature heavy release!
First off, though, AVA now officially supports Node.js 14. Thank you @zackschuster! 2e7c76b
Run tests at specific line numbers
AVA can now run tests at specific line numbers! 🎉
Given the following test file:
test.js1: test('unicorn', t => { 2: t.pass(); 3: }); 4: 5: test('rainbow', t => { 6: t.fail(); 7: });Running
npx ava test.js:2for would run theunicorntest. In fact you could use any line number between1and3.This feature is only available from the command line. It won't work if you use tools like
ts-node/registeror@babel/register, and it does not currently work with@ava/babeland@ava/typescript. See #2473.Test-specific teardown functions
Sometimes tests have side-effects you want to clean up. @ulken has implemented
t.teardown()which lets you register teardown functions within your test. They'll run once your test has finished, even if it failed: 75cbc3btest('read file', t => { fs.writeFileSync('file.txt', '👋'); t.teardown(() => fs.unlinkSync('file.txt'); // Run assertions });Watch mode with the default reporter
Watch mode with the default reporter once again accepts key input. Thanks @pcdevil! 59c227d
ICYMI
afterEach()andafterEach.always()hooks can now determine whether the test passed. Thank you @bunysae for contributing this! 8f312c0test('passes', t => t.pass()); test.afterEach(t => { if (t.passed) { // Do something because the test passed } else { // Do something because the test failed } });If you've ever wanted to save some files along with AVA's snapshots, you can now determine the directory path by accessing
test.meta.snapshotDirectory. Thank you @ulken! cb5f9f7
All changes
See v3.7.1...v3.8.1 for all changes.
3.8.0
26 Apr 20203.7.1
19 Apr 2020Support parallel runs that do not need to run test files, courtesy of @micaelmbagira 26c8326
3.7.0
13 Apr 2020If you've ever wanted to save some files along with AVA's snapshots, you can now determine the directory path by accessing
test.meta.snapshotDirectory. Thank you @ulken ! cb5f9f7If you've ever wanted to save some files along with AVA's snapshots, you can now determine the directory path by accessing
test.meta.snapshotDirectory. Thank you @ulken ! cb5f9f7See v3.6.0...v3.7.0 for all changes.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.