GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
We can still keep the existing tests around as a sort of "extra" test, but before we remove them, we should add tap tests to cover the additional cases.
It looks like npm test already only runs tests in test/tap.
npm run test-all runs a different set of tests that aren't encompassed by npm test. It's probably going to take a while to get the coverage in npm (and the other modules it uses) increased to the point where the TAP tests alone are authoritative.
npm run test-all
We're closing this issue as it has gone thirty days without activity. In our experience if an issue has gone thirty days without any activity then it's unlikely to be addressed. In the case of bug reports, often the underlying issue will be addressed but finding related issues is quite difficult and often incomplete.
If this was a bug report and it is still relevant then we encourage you to open it again as a new issue. If this was a feature request then you should feel free to open it again, or even better open a PR.
For more information about our new issue aging policies and why we've instituted them please see our blog post.