Requesting Enhancement for "Step_Definitions" location configuration in package.json to support glob patterns about cypress-cucumber-preprocessor

[Huffman17]

I am having a similar issue, I am trying to separate features from step_definitions so in my package.json :
"cypress-cucumber-preprocessor": { "step_definitions": "./cypress/integration/project/stepdefinitions/" }

and my file path for features is cypress/integration/project/features/file.feature

When I run the feature, it cannot find my step definitions.

[lgandecki]

Thanks!

Would you be able to make a fork and try this out? Possibly adding step definitions in a place that would be accessible only through glob and .feature test for it?

[asmahkojo]

Hi! Thanks for the quick reply! I would love to but embarrassingly I'm pretty new to Github and currently don't have too much time on my hands for the next couple weeks. I could possibly get on it after a few weeks but I would really appreciate it if a more seasoned contributor were available to get on it. Any takers for now?
Thanks again!

[lgandecki]

Sure, we could probably have someone cook this up for you.

But, just to clarify, do you have something like:

cypress/
   step_definitions/
        featureSomtehing/
             somethingDefinition.js
             otherDefinition.js
        otherFeature/
            ...otherDefinition.js
        maybeADefinitionHere.js

or

cypress/
    stepDefinitionsFirstFolder/
        definitions.js
    stepDefinitionsSecondFolder/
       someOtherDefinitions.js

?

If it's the second case, what's the reason for NOT putting the step definitions under one folder (with nested folders)?
Could you explain a bit more your situation?

[asmahkojo]

Awesome thanks!
It is more like the first case.

To give you more context, let's call the project i'm working on "TestRunnerApp". TestRunnerApp is responsible for running tests for Repository-A and Repository-B. Thus, Repository-A and Repository-B are pulled into TestRunnerApp via npm link.
Both Repository-A and Respository-B will generally have a folder structure like below:

e2e/
    common/
        step_definitions/
            example1CommonStepDefinitions.js
            example2CommonStepDefinitions.js
    features/
        feature1Folder/
            step_definitions/
                stepDefinitionsSpecificToFeature1.js
            feature1.feature

So putting it all together, imagine the above folder structure for both Repository-A and Repository-B within the node_modules of TestRunnerApp (because they are pulled in via npm link).
So, I want to be able to do something like below in the package.json for TestRunnerApp:

"cypress-cucumber-preprocessor": {
    "step_definitions": "./node_modules/+(Repository-A|Repository-B)/e2e/**/step_definitions/"
}

I hope this helps. Thanks again!

[bhreinb]

Hi There,

I tried the sample project here @

https://github.com/TheBrainFamily/cypress-cucumber-example

I upgraded the dependencies to

"cypress": "^3.0.1",
"cypress-cucumber-preprocessor": "1.2.2"

I notice I'm able to override the default "step_definitions" path when I set this in the package.json

"cypress-cucumber-preprocessor": {
"step_definitions": "./cypress/support/step_definitions/"
}

However, I'm unable to do this within "cypress/plugins/index.js"

const cucumber = require('cypress-cucumber-preprocessor').default
module.exports = (on, config) => {
on('file:preprocessor', cucumber())

return Object.assign({}, config, {
"integrationFolder": "cypress/integration",
"step_definitions": "tests/e2e/support/step_definitions/"
})

}

Naturally, when I set that here I remove the entry within package.json but it doesn't seem to pick up the path I set within "cypress/plugins/index.js". Do I have this right? Any pointers on this would be greatly appreciated.

[lgandecki]

the package.json is a different configuration than what you use here as the config. We've decided not to add anything to the cypress configuration as it's owned by the cypress guys and they didn't really want to cooperate on decisions here. :)

Why can't you use package.json?

[bhreinb]

No I can use the package.json (it's just nice to have all test application configuration centralised in the one place is my only thing 👍 )

For example the "integrationFolder" is defined within "cypress/plugins/index.js"

the code behind that driving the test scenario is within "package.json"

"cypress-cucumber-preprocessor": {
"step_definitions": "./cypress/support/step_definitions/"
}

make sense?

[vio-codes]

I am basically requesting the same in this issue: #483
This is the structure that I'm looking for:

- integration/
-     common/
-         step_definitions/
-             example1CommonStepDefinitions.js
-             example2CommonStepDefinitions.js
-     features/
-         frontend/
-             step_definitions/
-                 frontendstep1.js
-                 someotherfrontendstep.js
-             frontendfeature1.feature
-        backendend/
-             step_definitions/
-                 backendstep1.js
-                 someotherbackendstep.js
-             backendfeature1.feature

Can this be achieved in any other way?

[badeball]

Due to personal reasons, the previous maintainers of this package are stepping down and handing the reigns over to me, a long-time contributor to the project and a user of it myself. This is a responsibility I'm very excited about. Furthermore, I'd like to thank @lgandecki ++ for all the work that they've done so far.

Read more about the transfer of ownership here.

The repository has however moved and all outstanding issues are being closed. This is not a reflection of the perceived importance of your reported issue. However, if after upgrading to the new version, you still find there to be an issue, feel free to open up another ticket or comment below. Please make sure to read CONTRIBUTING.md before doing so.