Config common steps folder instead of all steps [Question]

[venkata-reddy-dev]

I want to configure predefined steps folder path as line no 13 instead of line no 14 to 16

[venkata-reddy-dev]

I feel, it's really not developer friendly to update build.yml file for each re-usable step configuration.

[olexale]

Hello! Thanks for raising the ticket.

This mechanism was not intended to be used for local steps with relative paths. If you follow the README, for external steps, you need to specify the package name. That was made for users to be intentional when they share (provide external step) or import (use existing step) anything from another package via bdd_options config.

It might be annoying to add common steps at the beginning of the project, but soon the list becomes stable as the majority of the steps will be feature-specific. If that's not true for your project and you expect the majority of steps to be shared between features, consider specifying the stepFolderName instead.

How many common steps that are private for the package do you expect to have in your project?

[venkata-reddy-dev]

@olexale Thanks for quick replay. and by the way this is a great package to write tests.

As per my understanding, stepFolderName setting is per package and for all the .feature tests fallow that.

But in my case i have a folder where all the re-usable steps are placed. i just want to configure directory path of re-usable steps instead of each step path in build.yaml

My usecase :

I am writing the bdd test cases per screen, not per feature

Lets say I have 30 screens. I am creating 30 .feature files and 1 folder for each.

For each screen I have below steps

• given mock data as per scenario
• The app is running /// common step for all the screens
• i wait {3} seconds /// common step for all the screens
• verify screen

[venkata-reddy-dev]

As per this doc, it is configuration for step folder name right, not for re-usable steps config.

[olexale]

stepFolderName will not only change the name, it may also make all feature files inside the package use a single directory, so you will get the steps reusability you requested. Inside this folder, you may create subfolders to prevent it from becoming a mess.

If that solution is not acceptable, my question is the same: how many common steps that are private for the package do you expect to have in your project? So far it looks like you have two common steps (which I believe should be combined into a single one). That sounds not that bad if you had to write a single line in the config.

[venkata-reddy-dev]

@olexale i get it now, Thanks.

For my project mostly 5 to 6 common steps. not more than this.