describe.each and test.each are shown as 'test result not found'

[lampewebdev]

Hello,

when usuing .each the extension can not find the tests.

[zxch3n]

.each is not supported yet. I'll find a way to make it work

[lampewebdev]

@zxch3n thanks for the info.

Are you accepting PR's?

If you could just point me to the right file, I could take a look at it :)

[zxch3n]

PRs are welcome! But I'm afraid this might not be an easy fix. Because we cannot infer the dynamic test name with 100% correctness from the static text content (which is how this plugin works right now).

There are two options left

• Only register the dynamic tests' ancestors, and aggregate the test results to them
• Start a Vitest server and communicate with it

I'll work on the latter in a week or two, which can also provide watch mode #4

If you are interested you can take a look at discover.ts and the VSCode testing API document.

[lampewebdev]

Thanks for the info, I have investigated this a little and looked into the vitest/ui package because there it works.

They are basically connecting to the server like this:
https://github.com/vitest-dev/vitest/blob/main/packages/ui/client/composables/client.ts

When I have more time, I can investigate this a little more.

[sheremet-va]

• Start a Vitest server and communicate with it

Yeah, I think Vitest has an api to communicate with --ui? Can you use that?

---

Edit:

They are basically connecting to the server like this:

Oh, I should have read the next comment 👀 Sorry for ping 👀

[Nisgrak]

Maybe this is working now? In my repo the test shows the actual results

[TylerOliver]

I was still seeing an issue today where the last entry in the each array was undefined when being processed

it.each([ 1, "1", true, {}, [] ])("should be true when value is truthy", (value) => {
  expect(required(value)).toBe(true);
  // 1 -> true
  // "1" -> true
  // true -> true
  // {} -> true
  // undefined
})

It didn't matter which value was the last, that value would always become undefined.

[watonyweng]

Hi @lampewebdev, the latest version of vitest already supports describe.each and test.each, does the test command still prompt test result not found?

[unikitty37]

Using the example from the describe.each documentation, I'm still only seeing placeholders rather than the expanded tests.

Version: 1.76.1
Commit: 5e805b79fcb6ba4c2d23712967df89a089da575b
Date: 2023-03-08T16:48:08.231Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Darwin arm64 21.6.0
Sandboxed: No

Vitest extension v0.2.39

[wadefletch]

+1

[dreamorosi]

In my case the it.each tests are running and being detected fine however all the ones afterwards fail/hang.

Would be great to find a way to either support the feature or find a compromise that at least allows to "skip" the test cases containing .each while making the rest of the suites running and being detected normally.