-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
assert.deepEqual
can generate invalid YAML
output
#47075
Labels
test_runner
Issues and PRs related to the test runner subsystem.
Comments
debadree25
added
the
test_runner
Issues and PRs related to the test runner subsystem.
label
Mar 14, 2023
MoLow
changed the title
Mar 14, 2023
assert.deepEqual
can generate invalid node:test
outputassert.deepEqual
can generate invalid YAML
output
MoLow
added a commit
to MoLow/node
that referenced
this issue
Jul 6, 2023
PR-URL: nodejs#47088 Fixes: nodejs#47075 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v19.7.0
Platform
Linux Helios 5.10.102.1-microsoft-standard-WSL2 #1 SMP Wed Mar 2 00:30:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
test_runner
What steps will reproduce the bug?
Have this test file:
Run it with
node file.js
and examine the output, or use something liketap-parser
andnode file.js | tap-parser
How often does it reproduce? Is there a required condition?
100%
What is the expected behavior?
It should output valid TAP
What do you see instead?
TAP uses YAML in its output, and here properties from the object in the deep equal check are added to the YAML. Duplicate mapping keys are invalid in YAML, and thus it breaks
tap-parser
, resulting in the following output:You can also verify this error by pasting the contents of the YAMLBlock in something like yamllint.
Additional information
First reported on connor4312/nodejs-testing#5
The text was updated successfully, but these errors were encountered: