-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
doc(test): add missing passed
and error
on TextContext
#59322
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
base: main
Are you sure you want to change the base?
doc(test): add missing passed
and error
on TextContext
#59322
Conversation
Review requested:
|
passed
and error
on TextContext
passed
and error
on TextContextpassed
and error
on TextContext
485f8ca
to
24c4abc
Compare
24c4abc
to
7ddb4dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for raising.
I wasn't aware of this functionality; I'll check the implementation this weekend to confirm.
…rties on TextContext
added: v20.12.0 | ||
--> | ||
|
||
Indicates whether the test succeeded, this defaults to `true` before the test is executed, e.g. in a `beforeEach` hook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you happen to know where this is set? The implementation you cited does not do this, and that behaviour seems wrong. I would expect context.passed
to be nullish until there is something to report.
The failure reason for this test, if a non `Error` object was thrown it will be wrapped and available via the `cause` | ||
property. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The failure reason for this test, if a non `Error` object was thrown it will be wrapped and available via the `cause` | |
property. | |
The failure reason for the test/case; if anything other than an instance of `Error` was thrown, that will be wrapped and available via `context.error.cause`. |
(line length may anger the linter)
See #59321 and #51485 for implementation