Forum Discussion
- tristaanogreEsteemed Contributor
Step 1: USe Object Spy on the window so you can get the properties
Step 2: Find the propery containing the header (probably WndCaption or something similar)
Step 3: Use aqString methods to parse out the Table ID (https://support.smartbear.com/testcomplete/docs/reference/program-objects/aqstring/index.html)
- msapFrequent Contributor
objectspy captures the whole window - no luck with this.
- tristaanogreEsteemed Contributor
Exactly... because, in this case, the text in the title is not a separate object... it is a property of the full window. So, ObjectSpy the Window and look for the desired text.... As I mentioned, it's probably something like "Caption" or "WndCaption" that is the property.
This is something that needs to be understood about applications, both Desktop and Web... sometimes what you see on screen is an object... sometimes it is the property of an object. ObjectSpy tool is your BEST FRIEND in investigating your application under test to search out and figure out what is what... along with that, the Object Browser is the FULL view so that, once you Spy something, you can go to Object Browser and see if there is anything else that might be helpful (maybe there IS a child object that you need to look at which ObjectSpy is not finding).
This is a note to ALL new users of TestComplete: The root and core of TestComplete is in how it identifies objects and makes them "readable" by your tests. The Object Browser and its extension Object Spy are your primary means of interacting with that. And, by extension, NameMapping is how you then encapsulate those objects for consumption by your tests. You would do well to spend MOST of your time in your test automation in these three areas... get these concepts and features "right", and everything works a LOT smoother.