Skip to content
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

Fix unittest failures in Node14 under coverage mode #1594

Merged
merged 1 commit into from
Apr 15, 2021

Conversation

smcclure15
Copy link
Member

Resolves #1593.

The failing unittests for the ESM support lead to repairs in src/cli/run.js. I was observing different errors than just the one we were sniffing for, so I added another check with as much granularity as possible. This passes in both coverage and non-coverage runs now.

The other failing unittest was regarding source-maps; here we were simply getting different stack traces based on maps, and from what I could gather, the codecoverage mode was already doing mapping, and then --enable-source-maps does more, and seemed to be conflicting. I filtered this test under code coverage mode by inspecting the NYC_PROCESS_ID env var. I wanted to use BUILD_TARGET=coverage, but that is being set in a different process from what ultimately runs this test.

@Krinkle Krinkle merged commit 241b565 into qunitjs:main Apr 15, 2021
@smcclure15 smcclure15 deleted the codecov-node14 branch April 15, 2021 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Make unittests pass with "npm run coverage" on Node 14
2 participants