You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 29, 2024. It is now read-only.
Right now, protractor can only accept promise as capabilities if we are NOT using multicapabilities. The reason for this is because multiCapabilities runs each task in a new process, so the promise (function) cannot be passed (single capabilities work because we're not forking). Alternatively we could resolve capabilities in the launcher, before passing the resolved capabilities into the new processes; however, this will break #1040, which relies on capability promises to be resolved after driverProvider setup (i.e. for proxy purposes).
I can't think of an easy way of doing this (without large refactoring), but it is definitely doable. Just creating this issue to get a feel of how many people would benefit from being able to use promises in multiCapabilities and/or collect ideas.