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
As the chaos of normal development with multiple devs/teams continues, it is not unusual for a feature file to change. To keep the code base neat, it is a good idea to remove any step definitions that are no longer in use after such changes. However, finding such unused step definitions manually is hard work. Perhaps this plugin can do so automatically.
✨ What's your proposed solution?
Add an inspection that highlights unused step definitions in code, or a command to output a list of unused step definitions.
⛏ Have you considered any alternatives or workarounds?
Doing this manually is possible, but error-prone.
There are tools that plugin to the various cucumber runtimes to detect unused step definitions. However, they're not available for every runtime supported by this plugin.
📚 Any additional context?
For the project I'm working on right now I'm using Cypress with a pre-processor. I was happy to find that this plugin had no trouble recognizing the step definitions anyway, so navigation and auto-complete work.
🤔 What's the problem you're trying to solve?
As the chaos of normal development with multiple devs/teams continues, it is not unusual for a feature file to change. To keep the code base neat, it is a good idea to remove any step definitions that are no longer in use after such changes. However, finding such unused step definitions manually is hard work. Perhaps this plugin can do so automatically.
✨ What's your proposed solution?
Add an inspection that highlights unused step definitions in code, or a command to output a list of unused step definitions.
⛏ Have you considered any alternatives or workarounds?
Doing this manually is possible, but error-prone.
There are tools that plugin to the various cucumber runtimes to detect unused step definitions. However, they're not available for every runtime supported by this plugin.
📚 Any additional context?
For the project I'm working on right now I'm using Cypress with a pre-processor. I was happy to find that this plugin had no trouble recognizing the step definitions anyway, so navigation and auto-complete work.
This text was originally generated from a template, then edited by hand. You can modify the template here.
The text was updated successfully, but these errors were encountered: