It would be more helpful to see what other properties TestComplete exposes to use. It could be that what you're seeing as "name" is showing up somewhere else.
As for conditional mapping... why not? It seems like that would be an optimal way to go. Although, potentially, you could get an error about a property not being supported or something.
If you can provide screenshots of properties on the object, perhaps we can help find something that would work better.
I looked again. As I was taking the requested screen shots, I saw attributes.name.nodevalue seems to work. The conditional mapping was not going to work from the TC UI because of limitations to the UI for selecting the property.
Champion Level 2Hi,
> attributes.name.nodevalue seems to work.
This is probably the best way to go (https://support.smartbear.com/testcomplete/docs/app-testing/web/general/object-identification/using-custom-attributes.html) considering the technology your tested application is based on and obvious absence (or complete ignorance) of QA (not testing) activities. (Which is not your fault.)
Can you explain this
"considering the technology your tested application is based on and obvious absence (or complete ignorance) of QA (not testing) activities. (Which is not your fault.)"
Champion Level 2Hi,
> Can you explain this [...]
Your tested application seems to be created using React or Angular, both of which, by default, do not care about (external) testability of created html markup. While it is possible to create web pages with good semantic markup (i.e. with stable and unique identifiers for web elements), designers/developers usually do not care about this.
QA, which stands for 'Quality Assurance' is a set of preventive actions with the goal to assure the quality of the program been developed.
So, with QA activities and processes at place, management, stakeholders, other relevant people must be warned on the pre-development stage that created web pages will be of extremely low testability if no special attention and actions are taken from Development side. And this will be true regardless of test automation tool been used.
