-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Support assertion message in t.timeout() #2443
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
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
We can support an assertion message in This requires adding an argument here: Line 67 in 447d371
And then passing it along to here: Line 435 in 447d371
We should retain the default message. I think that should just show up correctly in the reporters. We must also add it to the type definition: Line 344 in 447d371
Our ESLint plugin must also be updated: |
Fantastic. I'm happy to help with that work if you'd like it |
@shellscape yes, PRs welcome 😉 |
Checking in, this is still on my radar. |
@novemberborn I'd like to work on this, if no one else is already doing so. |
@jonathansamines yes that'd be great. I assume @shellscape hasn't found the time to pick this up yet. |
You have assumed correctly. 🙇 |
@shellscape no worries! Hope all is well. |
Fixes #2443. Co-authored-by: Mark Wubben <[email protected]>
Please provide details about:
I'd like to display a message to folks observing test runs on a particular timeout to indicate that they need to check some configuration locally. This particular scenario arises from bad user config that is detectable only at runtime (thanks AWS).
I've sifted through the docs and can't find a good way to do this. I haven't taken a look at the source for a hack as I've been burned by doing that in the past and upgrading major versions.
Spitballing here, but perhaps:
The text was updated successfully, but these errors were encountered: