Do you know why I run test in Chrome and see UI. the case passed. but When I run in chrome headless mode, it failed with Unable to click on object ‘Object Repository/ZenoAir/span_Bookings’ I insert wait element step, still failed.
Same Issue I am facing, my test case executes on chrome successfully, but in headless browser it failed by not finding the object locator. I tried to increase the window size. Still not get success. Please help on that!
What is the reason you are using a headless browser to run your tests?
Usually this feature is used only during development to quickly check if the DOM is properly generated, makes no sense for real use-cases scenarios (unless you know some users which will run the browsers ‘in their mind’)