-
-
Notifications
You must be signed in to change notification settings - Fork 268
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
Add detection for .yaml and .yml #717
Conversation
I believe the only potentially use-facing change is removal of `TAP_DEV_SHORTSTACK` environmental variable. Technically this has no effect on end users as it was always the default. `TAP_DEV_LONGSTACK` still exists and allows users to strip tapjs and other npm "internals" from stack traces.
PR-URL: tapjs#631 Credit: @coreyfarrell Close: tapjs#631 Reviewed-by: @isaacs EDIT(isaacs): cast settings.output to a boolean in the cleanForSnapshot function in settings tests.
One test in test/run/esm.js is skipped in node.js 12.2.0+ due to a compatibility issue with the `esm` module and `nyc`.
bin/run.js
Outdated
} catch (er) { | ||
} catch { | ||
try { | ||
if (fs.accessSync(path + '.yaml') === undefined) { |
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.
Why the access checks? Just read the file, if it throws, it's not there or you can't read it.
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.
Okay. I have updated the PR accordingly.
PR-URL: tapjs#668 Credit: @MylesBorins, @coreyfarrell Close: tapjs#668 Reviewed-by: @isaacs, @coreyfarrell
PR-URL: tapjs#622 Credit: @IlyaSemenov Reviewed-by: @isaacs
Also, add docs for t.notHas and t.notHasStrict
It doesn't support mjs natively, so some tests will always fail.
Landed on v15, will be in next release. Thanks! |
This resolves #706.
I based my tests on
test/run/bad-rcfile.js
because I didn't see any other tests that cover parsing of rc files that I could learn from.I am not clear how to run the tests and generate an HTML coverage report so that I can see what branch(es) are not being covered. When I run
npm run unit
I can see that some branch coverage is missing, but not what it is.