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

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

Related

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

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();

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.

Handling IFrame using Watir WebDriver

Wanted to know how do you handle iframe using Watir WebDriver.
I am trying to automate a SalesForce based app which runs in a console mode.
All the GUI elements of the web applications are within iFrames.
The issue we are facing is the automated tests run perfectly fine in case of FireFox but when we try to run the same scripts in Chrome (using ChromeDriver ChromeDriver 2.20) the user action of selecting links within iFrames are not being performed.
Any idea if this is an issue/bug with the Chromedriver 2.20 being used.
Thanks,Umesh

Does using a headless browser with rselenium significanly faster?

I'd like to know if using a headless browser, (such as phantomJS) with RSelenium significanly faster than running scripts with a regular browser (such as chrome)? Also driving it directly or using a selenium server ?
Is there a short function to check/plot difference in speeds?

Debug Meteor Velocity Mocha tests

I want to debug my test using Velocity and Mocha, using breakpoints and REPL instead of console.logs.
For debugging my app code I can start my Meteor app with the NODE_OPTIONS='--debug' flag, and then bind the debugger like node debug localhost:5858. This doesn't work for the mirror, although its log says debugger listening on port 5858 (both main app and mirror logs say that).
How can I debug it?
Use meteor debug instead of meteor run to start your meteor application. It will add the node inspector package to your running Meteor app so that you can debug it. Node inspector works by hooking into your running Meteor server

Resources