taiko

taiko copied to clipboard

Is your feature request related to a problem? Please describe. If I want to await waitFor(300e3) to wait for 5 minutes, I hit the global timeout first and the test ends

Describe the solution you'd like I'm not 100% on the solution, but perhaps really long wait times should not be bound to a global timeout, or should at least have an option to override the global for this invocation?

Describe alternatives you've considered I'm about to try something like:

step("I wait for <seconds> seconds", async function (seconds) {

+  // Set timeout really high
+  setConfig( { navigationTimeout: 999999});

  await waitFor(parseInt(seconds, 10) * 1000);

+  // Reset timeout for remaining steps 
+ setConfig( { navigationTimeout: 3000});

});

The global timeout in taiko should get overwritten by the one given at api level.. if the timeout you are facing is from Gauge please try updating the config in env/default/js.properties for step timeout.

The global timeout in taiko should get overwritten by the one given at api level.

Sorry, does API level mean as part of calling the waitFor or are you saying I need to explicitly override it?

I meant calling from waitFor here