Taiko: Timeout error occurs when I try to navigate to certain url immediately after opening the browser.

Created on 11 Feb 2019 · 50Comments · Source: getgauge/taiko

Issue: Timeout error occurs when I try to navigate to certain URL immediately after opening the browser. But when I try to navigate second time, I was able to navigate.

Please make sure I am able to navigate to any url immediately after opening the browser consistently.

I am attaching the screenshot for reference.

Steps:

Expected behavior

I should able to navigate to any url immediately after opening the browser.

Actual behavior

I am not able to navigate to certain url immediately after opening the browser. Timeout error occurs. Only after second time i am able to navigate successfully.

Steps to reproduce

OpenBrowser()
goto("url")

Error: Navigation took more than 30000ms. Please increase the timeout.,

Repeat step 2 again.. Now it will work.

waiting-for-upstream

Source

Prakash0989

Most helpful comment

Finally its working. Thanks for your workaround. Lets keep this issue open until original issue is resolved.

Prakash0989 on 27 Feb 2019

👍3 🎉2

All 50 comments

Suspect this is happening because whenever a browser is opened it is opened in clean state (i.e.) without any cache and localstorage with new profile, in the subsequent gotos there could be some requests loaded from cache which might make the load time lesser than the one done immediately after openBrowser since there will be no cache and everything has to be loaded from source when loaded for the first time.

Can you please try increasing the timeout?
goto("url",{timeout:60000})

NivedhaSenthil on 11 Feb 2019

👍1

@NivedhaSenthil Even after adding timeout i am getting timeout error message.But i could see the url is launched.
goto("url",{timeout:60000})

Also i feel sometimes chromium browser is slow.Tough this issue is inconsistent.

Prakash0989 on 11 Feb 2019

@Prakash0989 Do you get the timeout error running your tests in headless as well? Or its always in the REPL?

saikrishna321 on 11 Feb 2019

Yes i am getting error running headless as well.

Prakash0989 on 12 Feb 2019

I think @saikrishna321 wanted to know if this happening only on REPL or even when running script in headless mode. Like,

code.js

const { openBrowser, goto, closeBrowser } = require('taiko');
(async () => {
    try {
        await openBrowser();
        await goto("google.com");
    } catch (e) {
        console.error(e);
    } finally {
        await closeBrowser();
    }
})();

and run taiko code.js does it timeout even then. To confirm if it an issue with REPL or with general execution.

NivedhaSenthil on 12 Feb 2019

👍1

I think there are potentially 2 issues wrapped up here. I will try my best to give a decent explanation.

I noticed in the REPL. If you take focus away from the chromium browser window (perhaps click another browser window or another application). Then return to the REPL and proceed to navigate the chromium browser will run the next action (e.g goto ('somewhere'). However, sometimes, the repl window will report an error

e.g Error: Navigation took more than 30000ms. Please increase the timeout., run.tracefor more info.
If I can manage to consistently recreate this I will report it separately.

The reason I mention this is because I think it is occuring in some instances alongside issue 2 (below) and it all seems like it is part of the same problem.

@NivedhaSenthil to answer your question in the particular endpoint we are testing. The issue is in both the .code version and REPL. I think you are right that the speed of the endpoint is causing some of the issue with clean cache, I believe this is shown this can be seen by:
i. Hitting the same URL in the same REPL session twice. The second time it will usually succeed with loading.
II. Not everyone is experiencing the same issue with navigating to the site with either method.

However, the concern is when the page does appear to complete loading in ample time, but then the subsequent actions are not run. I'm not sure if the timeout you pass waits for anything particular to occur before it proceeds (or waits for the DOM to complete loading) with the next action?
As a guess - Maybe the loading of the page occurs in an obscure way passing what you are waiting to see but then it still doesn't have the next element available at this time the product is an off the shelf one, so i am limited in my understanding of how it works.

suleytron on 12 Feb 2019

Guess Point 1 is related to https://github.com/getgauge/taiko/issues/369

Taiko waits for page load and first meaningful paint events by default for every load. Even when navigation timeouts subsequent action should happen from REPL wherein taiko runner will break on any error.

NivedhaSenthil on 12 Feb 2019

@NivedhaSenthil Should we just wait for first meaningful paint(that proves the content is loaded) to resolve and give access to the users to add waits on _networkIdle_ and _loadEventFired_

saikrishna321 on 12 Feb 2019

Ideally yes waiting for firstMeaningfulPaint should ensure document load and page load, that way user don't have to wait for networkIdle and loadEventFired since those event should get triggered before firstMeaningfulPaint. I feel it will be great to give user the flexibility to choose any events to wait for and if not given default to firstMeaningfulPaint.

This may not be related to to the timeout issue though.

NivedhaSenthil on 13 Feb 2019

Dear Team, Do we have any update on this inconsistent issue which is blocking me to move forward.
Even with google.com i am getting timeout exception.