Use runtime information to update the tests info

[zxch3n]

This extension currently relies on the babel parser to calculate the positions of tests statically. So it doesn't support

• test.each describe.each and test.each are shown as 'test result not found' #7 Iterative tests break when run directly from plugin #130
• Renamed test or describe Extension does not detect tests when "test" is aliased or default export etc. #127

[Maxim-Mazurok]

I saw your PR about watch mode #33 where you used vitest --api, I thought it'd help with test list generation, doesn't it?

[firatoezcan]

Btw, for everyone that reads this, I moved my tests out of my *.spec.ts files into *.each.spec.ts files and added rules so the extension doesn't run them but the CLI still does:

"vitest.exclude": ["**/*each.spec.{ts,tsx}", "**/node_modules/**", "**/dist/**", "**/cypress/**", "**/.{idea,git,cache,output,temp}/**"],
"vitest.include": ["**/*.spec.{ts,tsx}"]

This works like a charm

[ytw0728]

Hello! I appreciate your efforts.
could you let me know this issue's current status in the second one (renamed test or describe)?

is it dealing with now? and which version do you think it will be released?

[sheremet-va]

This is now supported in pre-release 0.5.0 and higher. Note that the extension now requires Vitest 1.4.0 or higher.