Bobcat ignoring explicitTimeout in config.yaml

Question

Bobcat ignoring explicitTimeout in config.yaml

DeChrish opened this issue 5 years ago · 5 comments

Config YML

default:
properties:
proxy.enabled: false
proxy.ip: 127.0.0.1
proxy.port: 9000
timings.implicitTimeout: 1 # in seconds
timings.explicitTimeout: 50 # in seconds
timings.pollingInterval: 500 # in milliseconds
page.title.timeout: 30
allure.report: true
allure.create.enviroment: true
contexts: [chrome,locator,dev]

Environment

Bobcat version:
6.4

Bobcat modules used:

bb-core

Browser + version:
any

Expected Behavior

Should have waited for 50 seconds

Actual Behavior

Time elapsed: 44.613 s <<< ERROR!
org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of BobcatWebElement(Proxy element for: DefaultElementLocator 'By.cssSelector: #userid') (tried for 10 second(s) with 500 milliseconds interval)
Caused by: org.openqa.selenium.NoSuchElementException:
no such element: Unable to locate element: {"method":"css selector","selector":"#userid"}

Steps to reproduce

Answer 1 · 2019-05-17T07:59:26.000Z

@mkrzyzanowski if i pass from command line - it accepts the new timeout value; Pl guide

Answer 2 · 2019-05-22T16:38:49.000Z

@Shaihuludus pl check what is wrong?

Answer 3 · 2019-05-24T15:13:29.000Z

Hi @DeChrish,
indeed the properties are ignored 🤦‍♂. I'm going to fix this and include it in the next release (which may happen next week :)).

Answer 4 · 2019-06-28T09:45:34.000Z

Hello,
When is this going to be released?

Answer 5 · 2019-07-31T12:43:40.000Z

Released in 2.1.0