URL is not opening in edge in robot framework however browser is launched - robotframework

I am trying to run my Robot Framework script in edge but its giving
WebDriverException: Message: Unknown error
while trying to launch the app.
Used Below snippet:
Open Browser https://www.amazon.com edge
Maximize Browser Window
I could see browser launched that too in maximized state but URL was not displayed like this
Also, my Teardown keyword is also not running(i.e. browser instance is not getting closed) which should ideally run if test case fails or gets completed.
Teardown step
Close Browser
In SeleniumLibrary.CapturePageScreenshot(default keyword to run on failure) it is showing that
"Cannot capture screenshot because no browser is open."
Also my same script is running successfully in Chrome Browser.
I am not sure if its bdriver compatibility issue, bcoz below Selenium-Java script is running fine
WebDriver driver = new EdgeDriver();
driver.get("https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/");
driver.manage().window().maximize();

Related

Running a Playwright Test that interacts with Maptile Headless, when running headless the map does not render

When running a Playwright Test that interacts with a page with Maptiles in a Headless browser, the map does not render
I've tried these without any success
passing --no-sandbox to chrome
passing --disable-gpu to chrome
setting preserveDrawingBuffer={true} inside of ReactMapGL
I'm open to any ideas

Ghost Inspector tests are failing on running

I record test using Ghost Inspector on a website. But when I run the test in Ghost Inspector, one of the buttons is always greyed (only in the test run), and the test fails. Not sure why this is happening. When I record the button is not greyed.
This is the console output in Ghost Inspector:
1788:23079 Uncaught Error: Error in attempt to create DIL instance
with DIL.c…pendency for DIL v8.0+: Invalid Visitor instance.
The same test if recorder and playback using Selenium IDE runs fine
I also tried exporting the failing test from Ghost Inspector as Selenium IDE (new) and opened in Selenium IDE, and test ran successfully
Without seeing the code/test its a bit hard to tell but I'll take a shot in the dark
1) could be ghost inspector test settings. I would go into settings at the top right corner when you are inside your test and look at browser settings. Make sure you're using the browser you want as well as the correct screen size.
2) Could be a timing issue. You might need to add an assertion to let the button load before trying to click that button.
If these don't help let us know a bit more about the test steps as well as the button you are targeting. what is its function and what are the circumstances when its supposed to be disabled.

Intern tests: cannot run local Firefox and Chrome tests together, Chrome will timeout and hang

I am trying to run functional tests with intern for Chrome and Firefox.
First, Chromedriver would not wait long enough for the page to load and element transitions to end and become visible, so I added sleep()'s in a few places and used pollUntil() to wait for the initial page load. None of this was necessary for Firefox.
I am able to run my tests on either Firefox, which all pass, or Chrome, which all pass half the time. But if I list both browsers in my Intern configuration, Chrome will fail all tests, the Chrome window will be frozen, and the chrome and chromedriver processes will remain running, detached from selenium webdriver process when I stop the webdriver from command line. The error I usually get from webdriver if I wait long enough is
Exception: timeout: Timed out receiving message from renderer: 600.000
I am running local selenium-server-standalone-2.45.0.jar and chromedriver v2.16 (Chrome v44, up to date) with Intern 3.0, on Windows7 64.
From what I've read, Chrome has issues with getting the active window, and when Firefox pops up, the Chrome processes are lost. I don't know if that would be an issue with the Firefox window or just other Chrome windows, though. Maybe it's bugging out when get() happens. Or just not loading all the way.
Is there anything I can do to run them together? Or will I have to run each browser separately until/if the chromedriver issues are taken care of? Any other suggestions? Thank you.

remote webdriver: Element is not currently visible and so may not be interacted with

I use JAVA + WebDriver (Thucydides) and Maven.
I'm trying to automate uploading of a file. If I launch test manually from IDE it passes, but when I launch it with Maven on Remote WebDriver the test fails halfway with the error:
net.thucydides.core.webdriver.WebdriverAssertionError: Element is not currently visible and so may not be interacted with
The browser is FireFox.
Thanks.
Look at screenshot in Thucydides report. It seems that your element is really not visible.

How to configure Dr. Watson to silently dump a crashing process without popping up any error dialog box?

I would like to know if it is possible to configure Dr. Watson to silently dump a crashing process without popping up any error dialog box?
We need this because I run a set of integration tests with some applications. We don't want the tests to be blocked by an error message box. We need a way to make Dr. Watson silent but still dump the image when the process crashes.
Best,
Dr.Watson itself is silent by default. anyway, if you want to control the way Dr.Watson works, enter "drwtsn32.exe" at a command prompt to display the configuration dialog for this software. also, to install Dr.Watson as the default debugger, use "drwtsn32.exe -i".
the settings for the default debugger is stored in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug. the Auto value should be set to 1 for the system to automatically launch the default debugger. in your case, it is mandatory to set this value to 1.
once all the above things are setup, you can instruct Windows to stop displaying the "X has encountered a problem and needs to close" dialog. on Windows XP, this is controlled in the System Control Panel, on the Advanced tab, the Error reporting button on the bottom of the dialog allows to control how the system reacts when an error occurs. (on other versions of Windows, there should be something similar, search for "Error reporting" on Google)
with the debugger set to auto, Dr.Watson properly configured and error reporting disabled, the system should not show any dialog when a crash occurs.

Resources