Forum Overview :: Still Life :: Re: (source)

[quote name="Ray of Light "][quote]Does it have some way of identifying links I want to click that is simpler than what I have done here?[/quote]You can tab along and watch the statusbar until its link text reads what you want, press enter. Or F6 and have ahk type the new url (if you know it already). In non-web applications, you can use the Window Spy (comes with ahk) to get the buttonclass, then use ControlFocus/ControlClick to click by name. You can use a FF extension (like Greasemonkey) to manipulate from the inside out: re-text an image link (using the image name to find it), and then use AHK to do a normal Find on your injected text. This does work on javascript links. Or, you could use the name of the image to download it before each test, and use the downloaded copy for in-test comparison. You can use the same fetch-and-compare trick for nonweb apps that lack usable buttonclasses but store their elements in a regular way (e.g., every Java app with its nonnative UI, you can pull the element images from the jar-which-is-really-a-zip file). [quote]The tool I'm accustomed to has an Object Repository that lets you set up identifying characteristics for all the "test objects" you want to use, which is nice because visual elements are usually subject to change.[/quote]Without having used this (but having read about it on the web just now), I can tell you the limitations are universal. Either the test tool needs a way to peek behind the screen (as AHK and QTP do with buttonclasses, and maybe QTP can examine a browser's DOM somehow), or it identifies the element using a combination of things that are visible on the screen. The comments I read about OR said that it will fall back to crude measures like XY screen positions if it can't come up with a unique set of identifiers otherwise. [/quote]