@Eomm as soon as you have time I wanted to ask you, for this PR what do I do, do I close it or do I need to update the PR? you see that the plan() method has been removed, with the latest change, see here: https://github.com/fastify/fastify/pull/6085/files#diff-26e9d5ca961ed63343e75a6e163636828fd423a76eb500c26bb0e169089e1f96L81, it is there in all tests

This is not necessary in these tests, tap.plan behaves differently from what the node test runner does and is often mandatory.
It can still be useful to ensure that the expected number of assertions has been triggered for complex lifecycles, e.g. involving hooks we want to be sure there are executed.

But this is ok to keep them even if there are not very useful, I kept them in other PRs I've done.

Personally, I have you keep them on all the tests or take them off on all of them, if you start taking them off in one and in others you leave them, it doesn't make much sense.

Those are rules you have to decide on the tests, so you also keep all the tests in the various repositories in order.

There are in all the tests in the fastify organization repositories. If you follow stable rules, it is also easier for contributors to follow the rules. Think about it

This is a pretty old and complex code base with a lot of different contributors on a long period time, there are no such strict rules and nobody want to waste time on it I think.
You can re-add them if you want and ask for a review.

I don't think you lose too much time, but just keep things in order, even if the tests are old and complex.

I have updated this PR with the new modifcations so that plan() method is put back in.