Using Cucumber with an existing Vitest setup

[charlieforward9]

I have been looking into using Cucumber to test integrations while using Vitest test the unit and component lifecycles. In practice, I am curious about a few things that seem incomplete about using these tools together in a seamless manner.

1. Writing Cucumber tests is distinct from Vitest tests. Given this, I imagine the coverages are not merged with the Vitest coverage report. I have not tested this myself, but I am curious if this is this possible to do? Particularly with an actions tool like vitest-coverage-report-action?

2. Using vitest-cucumber removes the 'quick-run' button that shows to the left of the line number on the describe, it, or test lines in my test files, since it replaces these APIs with Cucumber-specific describeFeature, etc method. I opened #62 to continue this conversation, but would like to know how likely it would be to see this come to fruition sometime soon.

3. Using vitest-cucumber-plugin, does not seem any easier. Especially as it has not been contributed to in 9 months. Additionally, I am trying to use React Testing Library to render the component I am testing, which does not look to have any documentation/examples.

Given these points, it seems that my best bet is to keep Cucumber and Vitest separate. However, I'd like to hear back from some contributors who may be able to help me get a deeper understanding of this use case.

[sheremet-va]

1. Not sure why it would be different. Coverage is just running files - if you import a file and run its methods, the coverage would be fine
2. Try using the pre-release version of VS Code extension. It should support the quick-run buttons. It also support coverage by the way
3. Cannot help you here, unfortunately

[sheremet-va]

The position is correct, by the way. vitest-cucumber uses test under the hood for And

[charlieforward9]

I am having issues with the test output not showing the correct output.

It would also be nice to see the breakdown of quick-run buttons on the lines similar to how it is broken down in the Test Explorer. This integration could use a bit of work, I will try to log the issues in the relevant area.

[amiceli]

I'm maintainer of vitest-cucumber, maybe I can help.
vitest-cucumber use test in each scenario steps like And, Given etc with test.each.
And describeFeature, Scenario and ScenarioOutline use describe.

@sheremet-va I'm not an expert, you speak about stack-race maybe I can improve this in vitest-cucumber project ?

[sheremet-va]

I'm not an expert, you speak about stack-race maybe I can improve this in vitest-cucumber project ?

It should just work out of the box. Vitest has a location property that resolves to the location of the call in a test file, so And, Given, etc will be displayed as tests, and describeFeature, Scenario and ScenarioOutline are displayed as suites.

I increased the stack limit so it should hopefully display icons correctly for all of them now.

[charlieforward9]

Do I have to update something? I am still not seeing the icons correctly.