Just an update, the SmartBear team was able to reproduce the issue and admitted that I found a bug. So, the headless mode is currently useless for us and we have to wait for the fix. At least the bug was finally confirmed :D
Hi, I'm not sure about dynamically drawn objects (the UI is Angular-based). But yes, I'm locating elements via xpaths and css. As mentioned, the test works fine in normal browser. And partially, it works also in headless mode. For example login works fine and even the property checkpoint for mapped element works fine...
It's just that the mapped element returns 0 children elements.
Champion Level 3Have a read through https://support.smartbear.com/testcomplete/docs/app-testing/web/general/common-tasks/dynamic-pages.html . Are you able to find out if those objects are dynamically drawn?
I'm having a feeling those objects are not being shown, until something has been clicked on or the page is loaded.
Thanks for the link. It's most probably not that case. The buttons are available directly after login to the app. I just tried to map the problematic button and of course, the button is found and happily clicked :) So the only issue is, why the parent mapped element returns 0 children?
Champion Level 3I don't have Intelligent Quality add-on, so I'm not able to test this and provide a possible solution. May be someone else may have a better explanation, unless it's a bug!
Thanks for your time and help. I'm really curious about this problem and looking forward to what the TC support will come with. So far, it looks like a bug in TC. We will see. I guess not many people are using TC in headless mode?
BTW, I already found another headless-related mode problem. The Password type variable is not translated to correct password, leading to login failure, due to incorrect password. This one is definitely a TC bug. Or nowhere mentioned limitation.
