selenium-cucumber-js | Browser automation framework written in pure | Functional Testing library

First of all, note that selenium-cucumber-js is using a rather old version of cucumber-js (1.3.3 vs 5.0.2 at the moment of writing this). Keep that in mind when you're consulting cucumber-js docs or looking for examples. Below, I'll be posting links to the cucumber-js@1.3.3 docs.

As for what's not working in your set up:

1. scenario object that is passed into your hooks doesn't have page objects attached to it. It only contains some meta info about the scenario and methods to get it. Here's a list of them: cucumber-js docs
2. If you want to reference the page objects from your hooks, you can use the global page as described here: Page objects - selenium-cucumber-js
3. Your loginApp() function probably still won't work because you're accessing webdriver as this.driver and helpers as this.driver.helpers. They're also globally defined by selenium-cucumber-js: Helpers

So, your hooks.js should look like this:

Note: the below example is for an old version of cucumber-js: 1.3.3. With cucumber.js, when you're referencing this from inside step definitions, you're actually referencing the World context. So, for this.page.addvalues.addValues(x,y); to work properly, you'll first need to create page that has a reference to your addvalues.js. Something along these lines:

world.js:

Everything defined under scripts gets executed in the default system terminal and on Windows ./node_modules/selenium-cucumber-js/index.js is definitely not a valid command (or rather a path). It just happens that the same file has a +x argument and a shebang pointing to a Node.js (or another JS interpreter) binary so that it gets executed on Linux without intervention.

I'm quite certain you'll get the same error if you were to execute the same command in the default Windows terminal (cmd.exe) but you may get away with it in some ports/emulations of *nix terminals (i.e. Cygwin, MSYS, bash.exe etc.) which may give you a false sense of everything working correctly outside of the npm chain.

If you want to make sure your script gets executed by Node.js while using relative paths and keeping cross-platform compatibility, call it explicitly as: