Strange behavior running headless vs non-headless

Question

I am observing three strange behaviors when running existing Keyword tests headless. I am not having these issues running non-headless.

1. There is a searchbar that restricts characters to 30 in the HTML (maxLength = "30"). This is seemingly ignored when running headless and more characters can be entered.
2. There is an export to file button that when clicked is not actually exporting the file to the Downloads folder
3. When running headless, TC/TE seemingly can't recognize the message on a browser alert/popup thus it can't be asserted. (I already have a post about this one: https://community.smartbear.com/t5/TestComplete-Questions/Browser-alert-popup-not-found-when-running-headless-no-issues/td-p/258299)

Does anyone have any idea why this is happening or what can be done about it?

Thanks

rraghvani · Answer

Do you have example script code, for step 2 and 3?

nastester · Answer

They're keyword tests but here are screenshots:&nbsp;#2&nbsp;#3

rraghvani · Answer

When running in headless mode and there's no UI, how does it click the export/download button or the browser alert dialog?

nastester · Answer

Not sure what you mean, it's running the webdriver headlesslyhttps://support.smartbear.com/testcomplete/docs/app-testing/web/supported-browsers/headless.html

Forum Discussion

Strange behavior running headless vs non-headless

Related Content

TestComplete: Headless Browser Testing in Parallel

Switching between headless/non-headless execution

Headless browser

Want to run existing non headless scripts in headless Chrome

Browser alert popup not found when running headless, no issues non-headless

Recent Discussions

Onscreen Object Selector Slowness

aqObject.CheckProperty() slowness

Problem with generated data table and keyword test

WebView2 support does not work

System checks for Object for every test