Integrate with vitest-vscode plugin

[charlieforward9]

When I use this tool in VSCode, I am not able to run tests with the testing tab in the navigator.

This would be very helpful to be able to see all the tests in my workspace.

When I replace describe with describeFeature, these disappear:

[amiceli]

I'm not an expert on VsCode but I will check it.
I will update this issue if I found a solution ;).

[charlieforward9]

It looks like this is in the process of being developed. Discussed here. This issue can be closed when the bug? I found is addressed.

[amiceli]

I reply in bug, I'm following that.
Maybe there are some improvements to do in vitest-cucumber.

[amiceli]

@charlieforward9 You can check new answer in the bug discuss.
Stack limit was increased and it should work ;)

[charlieforward9]

After updating vitest/vscode to v0.8.6, I am seeing the icons on each Cucumber statement.

[amiceli]

Nice, I will keep an eye on this vscode plugin for my futur changes ;).

[charlieforward9]

Similar issue in browser mode.

[amiceli]

In browser I only use fetch instead of node:readline to load feature file.
Nothing change for describe, test etc.

You still have missing icons ?

[charlieforward9]

Yes icons are still missing.

[amiceli]

I'll check issues on vitest vscode repository.

I don't see what I can do in vitest-cucumber.

[amiceli]

I found nothing in vitest vscode issues for this bug.

I test late vitest vscode version and 4.3.0 vitest-cucumber version with vitest-browser-vue project.

I've all icons.

[charlieforward9]

The icons show up in the navigation bar, but as the problem description indicates, they do not show up in-line with the code.

I will try to provide more details

[amiceli]

You right, I checked. I've only an icon for describeFeature.

EDIT:
I try on vitest-cucumber repository tests, I've same bug.
Even if I don't use browser mode.

[amiceli]

I tried with different vitest-cucumber versions, with / without browser mode.
I've same bug with icons.

I can't find where the bug comes from.

[amiceli]

vitest-cucumber still uses describe, test, etc.
It should works out of the box.

You can re-open discussion / issue on vitest vscode. If needed a vitest-cucumber fix, i will re-open this issue and create a branch etc.

[amiceli]

@charlieforward9 any news ? Do you open a new issue/discussion on vitest vscode repository ?

[charlieforward9]

@amiceli nothing yet, I have been trying to resolve more pressing issues at the moment, but I have this issue saved to get back to when I can dedicate more time.