The Problem
There doesn't seem to be any way to customize the generated steps, but people may want to add a default behavior, such as throwing an error, so that generated steps do not pass quietly.
Proposed Solution
Given I am using bddgen
And I have a missing step definition
And I have customized my bddgen setup to include my own code in generated steps
When I run npx bddgen
Then I should see the default bddgen generated step skeletons
And I should see my own code added in as well
$ npx bddgen
Missing step definitions: 1
Given('I am logged out', async ({}) => {
// Step: Given I am logged out
// From: features/sign_out.feature:13:5
throw new Error("not yet implemented!");
});
Use snippets above to create missing steps.
Naturally, people might want different variations of this:
- suppress the default generated step skeleton contents altogether
- include the default, and...
- add
<MY_CODE> before step skeleton
- add
<MY_CODE> within step skeleton, but before the default generated comments
- add
<MY_CODE> within step skeleton, but after the default generated comments
- add
<MY_CODE> after step skeleton
Additional Context
No response
Priority Level
Medium
The Problem
There doesn't seem to be any way to customize the generated steps, but people may want to add a default behavior, such as throwing an error, so that generated steps do not pass quietly.
Proposed Solution
Given I am using
bddgenAnd I have a missing step definition
And I have customized my
bddgensetup to include my own code in generated stepsWhen I run
npx bddgenThen I should see the default
bddgengenerated step skeletonsAnd I should see my own code added in as well
Naturally, people might want different variations of this:
<MY_CODE>before step skeleton<MY_CODE>within step skeleton, but before the default generated comments<MY_CODE>within step skeleton, but after the default generated comments<MY_CODE>after step skeletonAdditional Context
No response
Priority Level
Medium