Conversation
novemberborn
force-pushed
the
assertions-throw
branch
from
6d31fea to
f1d0b19
Compare
Fixes #3201. 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 `throws` and `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.
novemberborn
force-pushed
the
assertions-throw
branch
from
f1d0b19 to
a706a5f
Compare
This was referenced Dec 4, 2023
This was referenced Jun 20, 2024
This was referenced Dec 17, 2025
Merged
mergify bot
added a commit
to Agoric/agoric-sdk
that referenced
this pull request
Jan 22, 2026
closes: #9083 ## Description Breaking changes in v6: https://github.com/avajs/ava/releases/tag/v6.0.0 Relevant subset: - 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. avajs/ava#3260 - Failed assertions now throw, meaning that any subsequent code is not executed. This also impacts the type definitions. avajs/ava#3246 - [Only native errors](https://nodejs.org/api/util.html#utiltypesisnativeerrorvalue) are now considered errors by the t.throws() and t.throwsAsync() assertions. [Object.create(Error.prototype) is not a native error](https://github.com/avajs/ava/blob/v6.0.0/Object.create(Error.prototype)). avajs/ava#3229 This removes our local patches of Ava - #7619 - #7330 ### Security Considerations none, no runtime change ### Scaling Considerations none, no runtime change ### Documentation Considerations none ### Testing Considerations CI ### Upgrade Considerations none, no runtime change
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #3201.
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
throwsandthrowsAsyncnow 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.