vitest-cucumber-plugin

vitest-cucumber-plugin copied to clipboard

Typescript support?

2

It would be nice to receive the state type on the params

thelinuxlich

Plugin can't parse a `.feature` file

1

I added the simple example from the Cucumber setup instructions: ``` Feature: Is it Friday yet? Everybody wants to know when it's Friday Scenario: Sunday isn't Friday Given today is...

matthew-dean

Add support for TypeScript and async steps

8

Thanks for a nice package! What I need to be able to use it in my project is TypeScript and async steps support, which this PR adds. (Fixes #1) I...

joakimbeng

This PR matches Vite configuration and allows importing from files with other extensions (`tsx`, `ts`, `imba` ...) for step definitions. The included test case showcases the feature with typescript (supported...

haikyuu

Remove need to manually generate nearley parser

1

Converting the nearley file to JS is currently a manual process. Maybe use Vite to process it on the fly for dev then process it into a dist package for...

samuel-ziegler

Make the step definitions glob pattern configurable

3

To be able to place my step definitions wherever I want (I have them in `**/*.steps.ts` files) I need the glob pattern for the step definition files to be configurable....

joakimbeng

If a step throws and error, nothing appears in the log. Log the error, step, params and state.

samuel-ziegler

Currently, when a JS file that has syntax errors is imported, a completely unhelpful error is thrown. Need to throw an error that names the problematic file and provided the...

samuel-ziegler

samuel-ziegler

Define methodology for chosing tags via vitest command line

1

Need an easy way to specify a tag expression via the command line to be able to specify which test to run. #5 is a prerequisite.

samuel-ziegler