> > With Pivot the testing tool should just be able to introspect the >> component hierarchy to find whatever it likes anyway (I want to say >> XPath, but you know what I mean). >> > > The main problem with this approach is that, if the layout changes (such > that a button no longer exists at a particular "path"), your test script > would break. Using automation IDs, the script would still run OK. >
Good point - our QA lead on a past [AJAX] project frequently complained about that when we told him to walk the DOM to find the element he needed, because every time we updated the DOM structure at all, his test scripts would break :-/
