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
Thanks for the response Simon. I'd had a look at checkpoints, and they didn't really seem to do what I was after.
I've had another look, and I still don't think they do what I need.
As I mentioned, I want this functionality to work on non-web based applications as well as web based. So that cuts out most of the checkpoint stuff.
It pretty much only leaves Object and Property checkpoints.
Property one is not what I need here.
Object is close, but not quite what I want. It doesn't use Aliases, or indeed the name map file, as far as I can tell. And although you can set it to include/exclude child objects, it's pretty klunky about how it does it. If I uncheck a parent item, it doesn't uncheck all the child items below it?!?!? On a few pages there are a LOT of child items which I wouldn't want to include but I'd have to go though and uncheck them all one by one?
And then if the page changes, I need to update the name map file AND the object checkpoints?
Nope. Too much duplication of effort for something that isn't really doing what I want in the first place.
The idea is, the important parts of application are stored in the name map file. Without going into too much detail about the application, I would want the user to be able to specify (we use a data driven framework) to check the content of a specific tab within a page. They would only specify the tab at the top level. The script would then identify the tab in the Aliases part of the name map file and t6hen cycle through the child Alias objects verifying them mainly by exists methods. The work would be done in selecting the right properties to store in the name map file in the first place.
I've had another look, and I still don't think they do what I need.
As I mentioned, I want this functionality to work on non-web based applications as well as web based. So that cuts out most of the checkpoint stuff.
It pretty much only leaves Object and Property checkpoints.
Property one is not what I need here.
Object is close, but not quite what I want. It doesn't use Aliases, or indeed the name map file, as far as I can tell. And although you can set it to include/exclude child objects, it's pretty klunky about how it does it. If I uncheck a parent item, it doesn't uncheck all the child items below it?!?!? On a few pages there are a LOT of child items which I wouldn't want to include but I'd have to go though and uncheck them all one by one?
And then if the page changes, I need to update the name map file AND the object checkpoints?
Nope. Too much duplication of effort for something that isn't really doing what I want in the first place.
The idea is, the important parts of application are stored in the name map file. Without going into too much detail about the application, I would want the user to be able to specify (we use a data driven framework) to check the content of a specific tab within a page. They would only specify the tab at the top level. The script would then identify the tab in the Aliases part of the name map file and t6hen cycle through the child Alias objects verifying them mainly by exists methods. The work would be done in selecting the right properties to store in the name map file in the first place.