Feature Request: Allow specifying of default browser.wait time on it's own

[Tom-Hudson]

Feature Request

Reasons for adopting new feature
It is suggested in #4154 that the default timeout for browser.wait is taken from jasmineNodeOpts.defaultTimeoutInterval. To me this doesn't make much sense, because I often want to have a short timeout when waiting for an element to be present or visible, where as I want a longer timeout for the spec itself.

Being able to specify a defaultWaitTimeout in your .conf file would be good!

Is this a breaking change? (How will this affect existing functionality)
Not if it is implemented so the timeout value used for browser.wait falls back to use jasmineNodeOpts.defaultTimeoutInterval if it's not specified.

[Xotabu4]

#4154 just means if you not specified timeout for wait, it will be waiting forever. But in real world we have lot of other timeouts - jasmine, selenium and so on, so they will abort test execution.

Your request makes sense. Basically it is not hard to implement. If i would need that - i would use this - https://github.com/angular/protractor/blob/master/lib/config.ts#L472

Here i created small example how that would work - https://github.com/Xotabu4/Protractor-Experiments/tree/master/experiments/default_wait_timeout

Idea is to wrap original wait, and keep function signature compatible, and save execution context with .apply

And also using of params - allows to define it right from command line, something like this:

protractor --params.EXPLICIT_WAIT_TIMEOUT 1000

[Xotabu4]

@srghma
It does not work because this feature is not implemented :)
This issue is only feature request