Access Alias Path Information from Stub Objects in TestComplete
Context When a TestComplete alias object isn’t yet present in the UI, TestComplete returns a stub object. These stub objects currently expose only .Exists. Unfortunately, this makes it hard to dynamically determine the full alias path (.MappedName or .FullName) until the object exists. The information does exist somewhere as the stub object is defined in code by calling the Alias. Problem QA Engineers writing reusable functions often need to accept an alias object as a parameter, discover its parent/child path, and call WaitAliasChild step-by-step. This creates a circle. To call WaitAliasChild, you need the parent alias name and the child name. To discover those, you need .MappedName or .FullName. But those properties aren’t available until the object exists—exactly when you no longer need to wait. Which forces brittle workarounds like: Passing hard-coded alias strings (error-prone, breaks IntelliSense and alias tree binding). Parsing alias paths out of exception messages (fragile). Re-architecting tests to rely solely on string paths, which loses the benefits of the Aliases library and auto-completion. Requested Enhancement Provide a supported way to obtain the full alias path of a stub object before it exists. For example: // Current stub: { Exists: false } // Suggested: { Exists: false, MappedName: "Aliases.Application.SearchField", FullName: "Sys.ApplicationName.MainWindow.SearchField" } or a dedicated API: aliasObj.GetAliasPath(); // returns "Aliases.Application.SearchField" aliasObj.GetFullName(); // returns "Sys.ApplicationName.MainWindow.SearchField" Benefits Enables dynamic, reusable functions that accept alias objects as parameters. Eliminates the need for fragile string-based or error-parsing hacks. Keeps code strongly tied to the Aliases tree for maintainability and IntelliSense. Example Use Case function test(aliasObj) { var parentPath = aliasObj.GetAliasPathParent(); var childName = aliasObj.GetAliasChildName(); var child = parentPath.WaitAliasChild(childName, 10000); } test(Aliases.Application.Screen1.SearchField); test(Aliases.Application.Screen2.SubScreenA.SearchField); Reasoning for this solution The stub object is defines by calling the Alias, therefore it is somewhere available in the code. An example of how this works can be seen in the aqObject.CheckProperty native TestComplet function. In the Test Log the Alias is actually listed in the details tab of the error, even is the object does not exist. This proves that the Alias is accessible even though the object cannot be assessed. See stubAlias.png attached. Summary Expose alias metadata (MappedName/FullName) on stub objects or provide a safe method to query it.
Name Mapping not Working in Latest Version
I am encountering a problem with name mapping in TestComplete where my script cannot find my mapped object. The mapped object is definitely visible, and if i go into the name mapping section of TestComplete and press "Highlight" test complete can see that it is on the screen and highlights it. It specifically cannot see the mapped object when the script is being run. This name mapping worked in an older version(15.61), however in the newest version of test complete(15.76). I am not sure exactly between which versions it stops working. When I initially ran into this issue, most people suggested just rolling back to the previous version, and 15.61 was the only installer i had that i knew would work. I am trying to solve this without rolling back versions because i would like to use python 3.11. Thank you, any help is appreciated.
Name mapping gone
Hi, we are a small team and finding ourselves in this issue where whenever we make changes to the name mapping, and stage them to be committed, we notice that the <typeinfo> entries in the namemapping.tcnm xml file suddenly disappear. I think this is due to us initially not committing the typeinfo.dat file. We know have no way to restore that file. Could someone please help us understand if there is a way around this? I'm hoping there is something we can do so that it can trigger the typeinfo.dat file to be populated again/or download it. ^ the above is what it looks like, but every single name mapped entry has lost its typeinfo tag. Thank you for taking the time, NameMapping is new to us.
Click Mapped Name in Script to Show It in NameMapping View
It would be helpful to be able to right-click on a mapped name and have an option in the context menu to go to the mapped name in the NameMapping view. For example, in this line of code right-clicking on "TextBox" (and selecting the relevant menu item, e.g. "Go to Mapping")... textbox = Aliases.TheAppName.HwndSource_TheSettingsDialog.TheSettingsDialog.TextBox ... would take me to "NameMapping", with the "TextBox" mapping selected. (See attached)
NameMapping issues after IF Object statement returns false?
I submit a ticket through support already, but has anyone else seen an issue in 15.72 and 15.73 where a web test will fail with an "Unable to find the following object when executing the Click command:" error immediately following an IF Object statement that returns false? I am seeing this issue on two separate web test suites. If I use debugging to pause the test on the failing line, then right-click and "Highlight on screen" then continue, the test will work. If I just pause, then continue it will still fail. I moved that item above the IF Object statement and it works, but now the next one after the IF fails. In this image, the green item fails when by the pink item, but works when I moved it above the IF. Now the pink one fails. If I go back to 15.71, this does not happen.
