Strange behavior running headless vs non-headless
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Strange behavior running headless vs non-headless
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...)
Does anyone have any idea why this is happening or what can be done about it?
Thanks
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you have example script code, for step 2 and 3?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
They're keyword tests but here are screenshots:
#2
#3
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When running in headless mode and there's no UI, how does it click the export/download button or the browser alert dialog?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not sure what you mean, it's running the webdriver headlessly
https://support.smartbear.com/testcomplete/docs/app-testing/web/supported-browsers/headless.html
