New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What happened to the "cucumberOpts" parameter? Is that no longer supported? #848
Comments
No. |
See #679
That isn't true |
Thanks I'll check that out! |
@charlierudolph Tnx for explaining! |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This issue is a continuation of this https://github.com/angular/protractor/issues/4311. Where I'm discussing the changes on syntax about how to use protractor to execute Cucumberjs scripts.
As requested by @wswebcreation https://github.com/wswebcreation, I closed that other issue and opened a new one here.
So, my last comment was this....
The last record I have of a successful execution was on 12 May 2017, 14:03. Precisely the date in your document.
Your example about tags is very simplistic... how then should I call for 3 tags, two that must be executed and one that is ignored. Before May 12, this used to work fine, but now it doesn't:
protractor ./FM_IntTest_UI_conf.js --disableChecks --params.login.email=mytest@email.com --params.login.passw=mypassword --cucumberOpts.tags ~@ignore --cucumberOpts.tags @smoke,@sprint
Your document says now it should be like this, but doesn't work, returns same error message I submitted with the "ticket".
protractor ./FM_IntTest_UI_conf.js --disableChecks --params.login.email=mytest@email.com --params.login.passw=mypassword --cucumberOpts.tags '@smoke or @rt' --cucumberOpts.tags 'not @ignore'
Error: Error: more than one config file specified
at C:\Users\echavez\AppData\Roaming\npm\node_modules\protractor\built\cli.js:155:15
at C:\Users\echavez\AppData\Roaming\npm\node_modules\protractor\node_modules\optimist\index.js:307:21
at Array.forEach (native)
at parseArgs (C:\Users\echavez\AppData\Roaming\npm\node_modules\protractor\node_modules\optimist\index.js:305:16)
at Object.Argv.self.parse (C:\Users\echavez\AppData\Roaming\npm\node_modules\protractor\node_modules\optimist\index.js:140:16)
at Object. (C:\Users\echavez\AppData\Roaming\npm\node_modules\protractor\built\cli.js:158:21)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
I can see in the Cucumber document that also the coding syntax for step definition changed? Why making it more complicated now? Because with the new syntax, I must group steps by scenarios. But there are some steps that are repeated in several scenarios, thus repeating code on each scenario? I will end up with redundancies in my code. Why?
Here's a snippet of what I have NOW in my test.spec.js file:
Here's a snippet of what is proposed as an "update"... for me is a DOWNGRADE:
If the scenario has several Given, When, Then... do those have to be enumerated here, like this?:
defineSupportCode(function({Given, And, And, When, And, And, Then, And, And, And}) {
If that's is true... So now, if I want to use again the step "When There are records in the EDI-Rejects Widget" in another scenario in my feature, do I need to code all the function again?
All I need are answers with arguments. Don't take it personally.
The text was updated successfully, but these errors were encountered: