Closed HarikrishnanVK closed 1 year ago
Hi @HarikrishnanVK , thanks for posting this issue. We are currently working on improvements to support indicating the features path as part of the execution arguments (and not assume the features folder is always located in root execution directory). We will have that implementation ready soon (cannot provide an ETA yet, sorry)
Regards, Hernan
Hi @HarikrishnanVK, We have applied the fix in https://github.com/hrcorval/behavex/tree/release_2.0.0 It will be released pretty soon.
Regards,
Changes already implemented in latest release (v2.0.1)
Describe the bug I have a directory that has different sub folders where one of them has features and tests related to Behave.
Using Behave package, I can run my feature pointing to my sub folder as per below command.. behave behaveSample/features --tags=dropdownTest
But when i try to do the same using behaveX wrapper, it is not finding my features and throwing error as unrecognized arguments.
I couldn't find anything from documentation about how to set the path to features folder via behaveX CLI. Plz help me on this.
To Reproduce Steps to reproduce the behavior:
Expected behavior BehaveX should able to find the features directory located inside sub directories or at least there should be a way to mention the directory path like in behave.
Screenshots With behave where features are found:
With behaveX where features are not found:
Desktop (please complete the following information):