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
multiCapabilities doesn't invoke parallel instances of WebDriver #5145
Comments
Could you please have a look at this issue? This issue is blocking me from running automation tests using Protractor = 6.0.0-beta branch. |
Any reason why you think multiCapabilities not working in Protractor 6.0.0? |
Same here |
Facing same problem with protractor version |
Any update on this issue? |
Yikes, this appears to be an issue. Maybe keep using 5.4.2 until this is resolved. I'm not sure and will talk it over with Julie. |
While removing q from Protractor, I did run into this (which might be suspect): https://github.com/angular/protractor/blob/master/lib/launcher.ts#L231 My problem with this was we called a method that returned a Promise without awaiting the promise. I ended up putting an await there. This might not be it... It might be: https://github.com/angular/protractor/blob/master/lib/launcher.ts#L250 |
Appreciate your help for looking into this issue. I will continue using 5.4.2 until this issue is resolved. |
Similar issue here: #5232 I have not had time to look at this. |
Any updates on this? |
I think this is the same issue, my error is saying the path to the spec file for chrome is not correct, but I believe it is looking at my project structure, it's obvious. So I believe the error is wrong, but it is the same issue. Conf file: In my multiCapabilities I have two different browsers with the argument
and
respectively, but only Firefox browser launches. I expect both Chrome and Firefox to run parallel (2 instances of webDriver) with different spec files respectively.
|
When should we expect 6.0.1? It looks like the development of a protractor has stopped completely. And the latest version 6.0.0 has a typescript error. that makes it totally unuseful. Can somebody release just that fix under 6.0.1, and then take care of the rest in a scope of 6.0.2? Or else, if there's no more development of protractor, can it be announced, so that people start to look for alternatives? |
Any update on this? Has someone found any workaround in the meantime? @cnishina Even more important: Is the project abandoned? |
I've found workaround for parallel sessions using bluebird promises.
|
@cnishina Keen to know where things stand with Protractor and future of version 6. Not seen any updates for few months? |
I was trying to contact some developers of this project and Angular 4 months ago and I had no reply. It really seems abandoned. |
Yes, this is important. Please announce if protractor development is being continued or we need to look into alternatives? |
Start using Cypress |
I don't see Cypress as a viable alternative atm. It only supports Chrome and doesn't work with BrowserStack. Also, it requires a paid license. |
here you wait for every runner, sequentially in the loop.
should be:
and |
@heathkit @cnishina @juliemr no longer work on Protractor, we can't speak to future plans. We continue to use Protractor internally, and there's a lot of other projects at Google that depend on it. The Angular team would like to invest more in Protractor, and will have time now that they've landed Ivy. @IgorMinar will be better able to answer questions about the future of Protractor. |
Is someone fixing this ? I need it badly. Our tests serially takes more than an hour. Please help. |
Bug report
Using Protractor = 6.0.0-beta, multiCapabilities execute individual captibilities in sequential order rather than running the capabilities in parallel.
v10.15.1
6.0.0-beta
3.141.59
Chrome 72/ Firefox 64
2.46
Mac OS 10.14.2
- Your protractor configuration file
// conf.js
- A relevant example test
// spec.js
- Output from running the test
Able to reproduce this issue only in Protector 6.0.0-beta
The text was updated successfully, but these errors were encountered: