-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
Test runner: spec reporter hides assert.deepStrictEqual diff when used with --test parameter #47051
Comments
Duplicate of: #46871 |
fixed by c7e6a0c |
@MoLow I don't think that's fixed (quick assumption, can't download nightly right now): this issue related only to spec reporter, not tap. As you can see, there are no issue with expected / actual values before that fix, only error name was missed: Also,
|
I confirmed again, both worked on the main branch:
|
@MoLow thank you! |
Version
v19.7.0
Platform
Darwin MOW-C02CF81MMD6T 22.2.0 Darwin Kernel Version 22.2.0: Fri Nov 11 02:08:47 PST 2022; root:xnu-8792.61.2~4/RELEASE_X86_64 x86_64
Subsystem
No response
What steps will reproduce the bug?
With given file t.js
node --test-reporter spec t.js
-> diff is present (see expected behaviour)node --test-reporter spec --test t.js
-> no diff at allHow often does it reproduce? Is there a required condition?
100%
What is the expected behavior?
Output with diff like that
What do you see instead?
No diff, actual & expected values are undefined
Additional information
This make makes spec reporter are totally useless, because I have to re-run failed tests one by one to understand what's happened.
The text was updated successfully, but these errors were encountered: