Alias objects identifying through code?
Not sure if this is possible ... Can I take a name mapped object by it's Alias and then (using code) retrieve all the alias child objects that sit below it in the name map/alias file? I'...
Forum Discussion
OK. I'm sort of getting what I want using NameMapping.sys and NamedChild.
Next question:
If an object is not found, is there any way I can get more detail on what the object is besides it's index number as NamedChild? When the script is searching for the object, it pops up in the runtime dialog box saying
"Waiting for <object name>"
... until the object is not found.
I want to report out that these objects are missing. To someone viewing my test output, an object name would be far more useful than an index number. Is there any way I can get hold of this name whithin the script? It's obviously available as TestComplete uses it in the dialog while it looks for it. But it's not available as a property of the not found NamedChild.
As an addition to this, NameMapping.sys seems to allow you to interrogate the name map file during a run. I can't find any similar functionality for the Alias structure? Is there any way this could be added as an enhancement? I would find it incredibly useful to be able to use and interrogate the Alias structure during a run rather than just using it to shorten object names within script.
The full name map file contains parts of the application that the end user carrying out the testing (I provide a framework and modules for them to build tests from) is not likely to be interested in. I only really want it to report back on the controls they are interested in. If a control changes due to something changing further up the heirarchy and the check for it fails, I'm fine with that. It will flag up that I need to update the object map regardless. But I only want the reporting to the user to state things at certain levels. Anything beyond that will be investigated by me or the developers. Using the Alias file for this would be perfect!
Next question:
If an object is not found, is there any way I can get more detail on what the object is besides it's index number as NamedChild? When the script is searching for the object, it pops up in the runtime dialog box saying
"Waiting for <object name>"
... until the object is not found.
I want to report out that these objects are missing. To someone viewing my test output, an object name would be far more useful than an index number. Is there any way I can get hold of this name whithin the script? It's obviously available as TestComplete uses it in the dialog while it looks for it. But it's not available as a property of the not found NamedChild.
As an addition to this, NameMapping.sys seems to allow you to interrogate the name map file during a run. I can't find any similar functionality for the Alias structure? Is there any way this could be added as an enhancement? I would find it incredibly useful to be able to use and interrogate the Alias structure during a run rather than just using it to shorten object names within script.
The full name map file contains parts of the application that the end user carrying out the testing (I provide a framework and modules for them to build tests from) is not likely to be interested in. I only really want it to report back on the controls they are interested in. If a control changes due to something changing further up the heirarchy and the check for it fails, I'm fine with that. It will flag up that I need to update the object map regardless. But I only want the reporting to the user to state things at certain levels. Anything beyond that will be investigated by me or the developers. Using the Alias file for this would be perfect!