captureTimeout should start after a browser is granted

[vojtajina]

Most of the time it gets timeouted on just waiting for a browser, not actual problem.

[ChrisWren]

@vojtajina any idea how to do this? It looks like it has to interface with the karma internals: https://github.com/karma-runner/karma-sauce-launcher/blob/master/lib/sauce_launcher.js#L8

[ChrisWren]

Might be a matter of moving captureTimeoutLauncherDecorator(this); to somewhere else in the launcher. I tried moving it to the start function, but it never started...

[Krinkle]

Might be related to #40.

[pkozlowski-opensource]

@ChrisWren moving the captureTimeoutLauncherDecorator(this); to the start method won't do the trick as the captureTimeout starts only on the start event: https://github.com/karma-runner/karma/blob/51f1b8832b86c4f556b58381fa183776212cfaa7/lib/launchers/capture_timeout.js#L14
But when we are in the start method the start event was already fired.

I tend to think that we need to:

• add another method to the captureTimeoutLauncherDecorator - something like startTimer or sth.
• add another config option (autoStartCaptureTimer)

and then start a capture timer "manually" from the Sauce launcher (this way we could choose the exact moment, ex.: after a WD session is ready).

@vojtajina @ChrisWren does it sound like a sensible solution?

[mightyiam]

🐱

[JamesMGreene]

Any update, PR, or merged/equivalent implementation?

[wswebcreation]

Closing this due to inactivity, feel free to re-open if this is still an issue.