amiceli

I tried with a new beta version `3.5.1-beta.1`. When I changes tests, for example, `expect(true).toBe(false)` to `expect(true).toBe(true)`. Vitest detect changes and I havn't an error about feature file. Do you...

I close this issue, i'll re-open if I have any feedback

vitest-cucumber is framework agnostic, so it won't provide logic for a specific framework. In my (company or side) projects using Vue, we use hooks to set/reset components, mocks etc. Like...

I made this repo when I needed Gherkin in my company/side projects for unit tests. I never tested `vitest-cucumber` with e2e tests. For me `vitest` is for unit tests and,...

If you use `rerender ` inside `describe`, `afterAll`, etc without vitest-cucumber but just with vitest, you have same issue ?

No updated for a while, I closed. It will re-open if this issue is updated ;).

All right, I keep it open ;).

Well done ! I'm going to add it in the doc ;).

I added it on the [readme](https://github.com/amiceli/vitest-cucumber?tab=readme-ov-file#examples).

Yes a good idea, I will do it ;)