-
Notifications
You must be signed in to change notification settings - Fork 525
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
Move from tap to the node core test runner #2267
Comments
Will give a shot at this |
@mcollina There are a lot of test files using Are we looking to migrate all of them in one PR or migrating part by part is fine? |
Hey! Given the large number of tests and the need to meticulously avoid false positives, would it be more effective to split the test suites into separate PRs? For instance, How about we create a list of these suites to distribute the workload and more effectively monitor the outcomes? |
Is there something like t.plan in node:test? |
I am on this now. I opened a PR #2719 for an example transformation. |
LOL. I created basically 6 batches and lost the following stuff, which I stashed in git. So please review and merge the open PRs. Then I can continue to migrate it. |
Nice. Its done. Maybe we can do the same in fastify |
As titled
This could be part of the next semver major that drops old nodes.
The text was updated successfully, but these errors were encountered: