Support it() as well for bench

[lveillard]

Clear and concise description of the problem

So we have already 150 tests we want to benchmark. We need to manually copy them, replace the it() by a bench() and then run our benchmarking

Suggested solution

While not optimal (we are including the expect... logic in the benchmark) it would be really convinient to be able to vitest bench the same files as vitest run

Alternative

An alternative is to store the body of the tests in an array, and then have a creator that encapsulates them as tests or as bench. But too messy.

Another alternative would be to build a different set of tests, but we want to leverage the existing ones.

Additional context

No response

Validations

• [X] Follow our Code of Conduct
• [X] Read the Contributing Guidelines.
• [X] Read the docs.
• [X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[hi-ogawa]

It sounds reasonable, but probably for the better argument, can you provide some concrete examples of some tests you want to bench?

Without considering actual design or implementation, one concern I might have is expect(...).toEqual(...) etc... assertions has pretty non trivial code to traverse you objects, so having all the assertions inside bench can skew the result depending on the assertion.

[lveillard]

We have these tests for instance: https://github.com/Blitzapps/blitz-orm/blob/main/tests/unit/queries/query.ts

Is an ORM for typeDB/surrealDB. Same way we run the tests for both DBs, we would love to just change the command and just run them as bench instead of tests.

I see two alternatives:

• Great: When run inside of bench ignores the expect and similars inside the it()
• Quick Win: Runs the full content of the it(), but warns about the potential result "skewness"

Both would be great for us. Our next step would be finding a way to run the tests once per DB to compare them. But lets keep that one for later 😂