Move Nitro Test Utils to this organisation

[johannschopplich]

The unofficial testing library may not be as refined as say Nuxt test utils, but it serves a purpose well: test a Nitro server with all bells and whistles like server routes.

In its current state, it is coupled to Vitest and the development or production Node.js build of a Nitro server.

I’d be happy go move nitro-test-utils under the Nitro organisation umbrella if the library does fit in the broader ecosystem, of course.

[pi0]

Thanks for the kind offer and great efforts on nitro-test-utils ❤️ mirroring my reply from X:

We don’t have official testing utils yet for two reasons: direct fetch interface (coming with h3 v2) and the ability to run prod tests in the target runtime and agnostic of the runner. I believe these should go directly into the nitro core and we also have a good amount of work done already in nitro tests/ dir that can be reused.

TYhere are several areas to work on relevant to testing:

• Official testing section in documentation
• Nitro CLI integration
• Runtime-compatible testing utils (sharing more details)
• Vitest environment for Nitro (similar to current nitro-test-utils. It would be nice if you could refactor current utils)

I must emphasize that Nitro has stricter design goals than higher-order frameworks to make sure it both remains runtime agnostic and remains composable enough to benefit the wrapped usage of Nitro.

In the meanwhile, i will make some issues on nitro-test-utils.