You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure what this issue is about. The choice of testing style in Vitest is deliberate and we do not plan to add different styles - this is left to the community to figure out and publish their own solutions (like you did).
Clear and concise description of the problem
In my company we use jest-cucumber to run our unit tests with our Gherkin feature file.
It allow to run unit tests checking if we missed a Scenario or a Scenario step like When.
Currently we moved to vitest in some project but we don't have a hest-cucumber alternative.
Suggested solution
I've created a repository vitest-cucumber with we can run unit tests using our Gherkin feature file.
It provides same method like jest-cucumber :
Scenario,WhenetcSo when we run unit test it check if we forgot a Scenario, or type a bad etc.
Alternative
No response
Additional context
I also publish vitest-cucumber on npm
@amiceli/vitest-cucumber.I would like to have your opinion.
Validations
The text was updated successfully, but these errors were encountered: