chore(deps): update dependency ava to v3.10.1 #1662
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.5.1
->3.10.1
Release Notes
avajs/ava
v3.10.1
Compare Source
It's time for another AVA release 🎉
Restricting when you can update snapshots
When executing a subset of tests, through
--match
or 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.f72fab4
If 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()
callsThanks to @jonathansamines you can now provide a message string when using
t.timeout()
. This can be useful if your test depends on some other setup that may not have been completed:ca8ea45
t.try()
does not work in hookst.try()
has never worked in hooks, but thanks to @okyantoro it now fails properly instead of crashing.d01db61
t.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 thedisableSnapshotsInHooks
experiment. Again thank you @okyantorod01db61
.Fixed TypeScript definition for
t.like()
The experimental
t.like()
assertion should now work better with TypeScript.All changes
See avajs/ava@v3.9.0...v3.10.1 for all changes.
v3.10.0
Compare Source
v3.9.0
Compare Source
New experiments!
Thanks to @futpib we now have an experimental
t.like()
assertion19c4f35
:In the following example, the
map
property ofvalue
must be deeply equal to that ofselector
. Howevernested.qux
is ignored, because it's not inselector
.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 first952a017
. This will be the behavior in AVA 4.To enable both these experiments update your AVA configuration:
package.json
:ava.config.js
:Reporter changes
@Michael55555 has helped us combine our reporter code into a single file
b3866b6
. We've also made some other tweaks and improvementsbaaf99a
. 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 concordancejs/concordance#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 avajs/ava@v3.8.2...v3.9.0 for all changes. Thank you @paulrobertlloyd and @Autre31415 for contributing documentation improvements.
v3.8.2
Compare Source
fd92b4a
a5385a4
v3.8.1
Compare Source
Node.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.js
Running
npx ava test.js:2
for would run theunicorn
test. In fact you could use any line number between1
and3
.This feature is only available from the command line. It won't work if you use tools like
ts-node/register
or@babel/register
, and it does not currently work with@ava/babel
and@ava/typescript
. See #2473.Thank you @ulken for your hard work and patience to get this shipped.
1222ce9
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:75cbc3b
Node.js internal in stack traces
Thanks to @bunysae, stack traces now include Node.js internals. Previously we removed them because we wanted you to focus on your own code, but quite often they do provide context. Now they're displayed, but somewhat dimmed.
9a9351d
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!8f312c0
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 avajs/ava@v3.7.1...v3.8.1 for all changes.
v3.8.0
Compare Source
v3.7.1
Compare Source
26c8326
v3.7.0
Compare Source
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
See avajs/ava@v3.6.0...v3.7.0 for all changes.
v3.6.0
Compare Source
afterEach()
andafterEach.always()
hooks can now determine whether the test passed. Thank you @bunysae for contributing this!8f312c0
:@mbiesiad has diligently translated our documentation to Polish. Thank you @kekuu for reviewing.
Also thank you @timgates42 for fixing a typo in our documentation.
ede4f32
See avajs/ava@v3.5.0...v3.6.0 for all changes.
v3.5.2
Compare Source
Renovate configuration
📅 Schedule: "before 3am on Monday" (UTC).
🚦 Automerge: Disabled due to failing status checks.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.