-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency ava to v3.15.0 #47
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
80366d2
to
819da2e
Compare
819da2e
to
dd22814
Compare
dd22814
to
f50eb00
Compare
f50eb00
to
a5bc60f
Compare
a5bc60f
to
3850c17
Compare
3850c17
to
c199241
Compare
c199241
to
597068e
Compare
597068e
to
339abe6
Compare
339abe6
to
523952e
Compare
523952e
to
21ad490
Compare
21ad490
to
8aab4a1
Compare
8aab4a1
to
9d5eabf
Compare
9d5eabf
to
c3de691
Compare
c3de691
to
ab88d58
Compare
ab88d58
to
1dda0e6
Compare
Dependency update (patch)
1dda0e6
to
47ca2f5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.0
->3.15.0
Release Notes
avajs/ava
v3.15.0
Compare Source
Automatic snapshot file removal
When you stop using snapshots in a test file, the next time you run
ava --update-snapshots
we'll remove the left-over snapshot files. Thanks @ninevra!4f093ab
TAP improvements
@tymfear has been on a roll improving our TAP reporter.
t.log()
output is now compliant with the spec99ab93a
. Tests that did not run due to timeouts are now reported98595da
.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 thenextGenConfig
experiment. Say in anava.config.mjs
file:This also allows you to pass an
.mjs
file using the--config
argument.With this experiment enabled, AVA will no longer have special treatment for
ava.config.js
files. 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.mjs
file next to anava.config.js
orava.config.cjs
file.See avajs/ava@v3.14.0...v3.15.0 for all changes.
v3.14.0
Compare Source
Snapshot 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
.snap
from changing when the reports themselves don't. You'll want to rebuild snapshots after upgrading to this release to isolate any changes. Thanks @ninevra!e66b54c
Shared 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 avajs/ava@v3.13.0...v3.14.0 for all changes.
v3.13.0
Compare Source
t.passed
can now be used in tests and teardown functions. Thanks @tymfear!900dc6d
null
as the expectation fort.throws()
&t.throwsAsync()
. You can opt in to this early by enabling thedisableNullExpectations
experiment. Thanks @JSimoni42!f328a69
db5d2c3
a3379fa
See avajs/ava@v3.12.1...v3.13.0 for all changes.
v3.12.1
Compare Source
Configure how AVA loads test files
Normally, AVA loads all files as CommonJS, except for
mjs
files 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 avajs/ava@v3.11.1...v3.12.1 for all changes.
Thank you @AnthumChris for making sure our ESM example used ESM syntax (
20bc781
).v3.12.0
Compare Source
v3.11.1
Compare Source
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 avajs/ava@v3.11.0...v3.11.1 for all changes.
v3.11.0
Compare Source
New
t.like()
assertionThanks to @futpib we now have a
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.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 avajs/ava@v3.10.1...v3.11.0 for all changes.
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
v3.5.1
Compare Source
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻️ 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.