Q: Where does 'browser script timeout set to 16000' comes from

[nair-sumesh]

Describe the bug
How to overwrite the timeout in wdi5.

I tried several ways like below

browser.asControl({
      selector: {
        id: "",
      },
      timeout: 90000,
      forceSelect: true,
    });

in config as

  wdi5: {
   ....
    waitForUI5Timeout: 270000
  },
...
  waitforTimeout: 270000,
...
  cucumberOpts: {
 ...
    // <number> timeout for step definitions
    timeout: process.env.DEBUG === 'true' ? 999999 : 270000,
    
  },

Expected behavior
Should be able to set timeout out from the config file.

• wdi5/wdio-ui5-service-version: 2.0.2
• UI5 version: [1.119.0]
• wdio-version (output of wdio --version): 8.16.12
• node-version (output of node --version): v18.16.1
• OS:macOS 13.5.2
• Browser + Version : Chrome version 117.0.5938.92

[vobu]

what you're asking in the subject of this is in

wdi5/src/lib/wdi5-bridge.ts

Line 123 in 9d6cff1

const timeout = waitForUI5Timeout + 1000

so wdi5.waitForUI5Timeout and wdio's script timeout are aligned.

there is no timeout option in the browser.asControl-selector:

wdi5/src/types/wdi5.types.ts

Line 186 in 9d6cff1

export interface wdi5Selector {

[nair-sumesh]

as per the calculation for

const timeout = waitForUI5Timeout + 1000 

the timeout should be 271000.
However, I see the console log with timeout set to 16000.

The issue is in the code below

The config.wdi5 is undefined at runtime.
And hence, it always default the value with 15000.

This needs to be fixed.

[nair-sumesh]

TEMPORARY SOLUTION

wdi5/examples/ui5-js-app/webapp/test/e2e/ui5-late.test.js

Lines 3 to 4 in 9d6cff1

	const ui5Service = new _ui5Service()

const ui5Service = new _ui5Service(undefined,undefined,{wdi5:{waitForUI5Timeout:270000}});

[vobu]

ahhh, this means that programmatic instantiation of the ui5 service (aka wdi5 core) doesn't pull any existing config per default!
we could change this and make the constructor pull the config that was provided for starting wdi5 when late-injected.
Think this makes sense and you wanna give it a shot, @nair-sumesh 😸 ?

[nair-sumesh]

While I debugged , I couldn't find the config data. The browserInstance does have few config properties but not the specific wdi5 one.

Is the config already being persisted in any global variable?

[github-actions]

hey 👋 - silence for 30 days 🤐 ... anybody? 😀

[vobu]

fixed with #552

[paritagandhi]

I am migrating from WDI5 1-> 2 . How can I now access waitforTimeout? Previously, I used browser.config.waitforTimeout and now it just says TypeError: Cannot read properties of undefined (reading 'waitforTimeout')

[vobu]

here's the migration guide: https://ui5-community.github.io/wdi5/#/migration?id=from-1-to-2
this is where all the config lives: https://ui5-community.github.io/wdi5/#/configuration
and programmatically, there's

• browser.options
• and as a last resort: global.__wdi5Config