RSS Feed

Axe Test Automation Platform

By Blobs I don't mean binary large objects.  I mean objects that can't be seen by your automated tool.

Using a combination of key presses and image capture I can exercise the functionality.  However when it comes to using Axe I am not sure what is the best approach to referencing them in a spreadsheet.

In my case I have put each action as a command tied to an object.  Where the object is actually the parent object that I can capture.

Any thoughts?

Tim,

I tend to find with this kind of unrecognised object, use of the Axe object map features and creating a custom class is the best course of action, I will try to explain:

For a given Blob I would create a class of my own "MyBlob". An entry could then be created in an Axe object map for each object of this type. The properties for this object would include the parent object and any data required to perform the mouse movements or clicks to interact with the Blob.

An entry in the Local Action Map would map a "Set" for the "MyBlob" class to your custom function passing in the properties as parameters (e.g. the parent name and other data).

In this way we do not need lots of custom actions, still using the Set action to keep the testers happy.

Duncan

I enjoyed your naming of these "Problem objects" as Blobs perhaps we could open up a suitable name thread?

I suggest Unidentifiable Field or Object (UFO).

Thanks for this information.  I think I understand what you are saying.  That if I refer to the parent object in the object map I can still use the base Axe commands.  I am unsure how you would pass data with the parent object in the object map.  Can you give an example.

Currently I have used the brute force approach of creating a new command for each action.

For example I am automating Smart Tag menus in Word.  The menu cannot be seen, but I can access it using the Document as a parent object and the smart tag.  So for each command on the smart tag menu I Set the document then Set the smart tag and then have a custom function to select the menu command.

Tim,

You can include object map properties in you Action Maps using the &property& notation so to include say the parent property in a command the entry may be something like:

MyCommand("&parent&","%data%")

Have a look at pg.12 in the Technicians Guide.

Duncan