protractor-cucumber-framework | Cucumber framework plugin for Protractor | Functional Testing library

When running automated tests, I recommend to use the browser’s headless mode.

So you could add the args: ["--headless", "--disable-gpu", "--incognito"] in your protractor.conf.js file.

e2e tests can take long time to complete, due to elements on a page that the browser needs to load. Therefore, in some cases, it may be stuck because the element cannot be loaded. Headless testing gets rid of this load time, allowing you to cut your testing times significantly. In our tests with headless testing, we've seen a 30% reduction of test execution times.

can you try this instead

Try removing the chromeDriver attribute from your protractor.conf.js and then running this command before you start your tests:

One reason is Then/When/Given usage change in cucumber 6.x, you can change few step functions to verify this.

For 1.x step function file looks like

You placed onComplete in the wrong place. It should belong to the config itself, not to cucumberOpts

I can't give you a working solution, because you didn't attach the config in text format

You are confusing yourself with Scenario outline and Data tables.

Scenario outlines are used when you want to execute a scenario with multiple test data.

Data table helps in passing multiple test data to a single step in a scenario. you can access this data in step definition using hashes and rows.

You can find the docs here and examples here.

A more detailed documents on Gherkin is found here.

I think you are consoled wrong, You had stringified function not the object

Like I said in the question, the problem was the compiler was failing to compile the scss files of the components when they try to import an scss file from node_modules.

I resolved it with sass-loader applying the following rule for scss in the webpack.config.common.js: