Hot answers tagged

3

You Can use Wait Until Keyword Succeeds keyword . like: Wait Until Keyword Succeeds 5x 4s click Element xpath=........ Here 5x is how many times you want to execute your action and 4s is your time duration, how frequently you want to wait until next try. Any Many More usage below - *** Settings *** Library ExampleLibrary Library ...


3

"chromedriver": "^2.36.0", "selenium-webdriver": "^4.0.0-alpha.1", here example of create driver function: import webdriver from 'selenium-webdriver' import chrome from 'selenium-webdriver/chrome' import chromedriver from 'chromedriver' const TIMEOUT = 300000000 export default async () => { chrome.setDefaultService( new chrome.ServiceBuilder( ...


2

The most important thing in this traceback is actually this part: The following tasks were pending: - $timeout: function () { clearEvents(type); } - $timeout: function setErrorMsg() { // Broadcast system timeout lock event $rootScope.$broadcast('um:LCK_TIMEOUT'); That $timeout is an Angular service which Protractor waits for to complete and does not ...


2

I had a same issue. It is due to a version issue. You can use: driver.manage().setTimeouts() or driver.sleep() please, check the documentation for more details.


1

I found a workaround: On the config file I added: allScriptsTimeout: 1100000, getPageTimeout: 60000, and on the spec file, on the function that was failing I added: browser.ignoreSynchronization = true;


1

You can also suppress error message using ChromeDriverService class: WebDriver browser = null; ChromeDriverService service = new ChromeDriverService.Builder() .usingDriverExecutable(new File("C:\\chromedriver.exe")).usingPort(4444).withSilent(true) .build(); service.start(); browser = new RemoteWebDriver(...


1

https://stackoverflow.com/questions/60114639/timed-out-receiving-message-from-renderer-0-100-log-messages-using-chromedriver This is a known-issue, it's not actually a failure but a retry attempt to listen to chrome. The severity tag confuses the user, and there is a fix on the way. You could also down grade to version 79 and it works with chrome 80. If ...


1

Looking into HTTPHC4Impl.java int rto = getResponseTimeout(); if (rto > 0){ requestParams.setIntParameter(CoreConnectionPNames.SO_TIMEOUT, rto); } int cto = getConnectTimeout(); if (cto > 0){ requestParams.setIntParameter(CoreConnectionPNames.CONNECTION_TIMEOUT, cto); } and HTTPAbstractImpl.java protected int getConnectTimeout() { ...


1

There are 2 ways you can pass properties 1. pass by command line options 2. pass by using properties files. To pass properties using command line options: The flag to set a property is -JpropertyName The function to read a property is ${__P(propertyName)} To pass properties using JMeter.properties file Define a property in JMeter.properties file (...


1

I was having the same problem and this fixed it: const capabilities = await driver.getCapabilities(); capabilities['map_'].set('timeouts', { implicit: TIMEOUT, pageLoad: TIMEOUT, script: TIMEOUT }); getCapabilities() retrieves the Map of the driver's capabilities which you can then interact with using the default methods outlined in the MDN Javascript ...


1

Remove the index attributes like @index='0' and waitForPage statements might fail if the page is loaded faster then your script. Use waitForPage with 2 parameters and 2nd parameter value to be true: web.window( “/web:window[@title=’Google’]”).waitForPage(200,true); OR Use: web.window( “/web:window[@title=’Google’]”).waitForPage(PAGEWAIT,true); where ...


1

Try setting the PageLoadStrategy capability to none when you create your driver instance, I use this when using Chrome to get around the issue where it times out after 30 seconds. Sometimes the page has not completely loaded but elements are there etc but the page is not in a ready state so it just sits there and does nothing.


1

For get() function the sequence will complete first action(open webpage) and wait till page is ready and if the next action is ready, for example element is present and no use for explicit wait or sleep , it will go for it directly and so on Try : driver.navigate().gotourl("URL") , also it allow some features like forward, back


1

I guess it depends on what exactly you're trying to get out of the test, but if the time element is merely a trigger for a particular behavior you might see if it can be mocked or stubbed out. So instead of waiting for the actual time to elapse, you could call some mock object to return the expected behavior after the time limit is reached without actually ...


Only top voted, non community-wiki answers of a minimum length are eligible