2009/9/23 Greg Brown <[email protected]>: > WTKX IDs are not exposed outside the serializer (except via the serializer's > Dictionary interface). We could try to repurpose them to suit this use case > as well, but I don't think that's the right approach, since it would > preclude performing automated testing on UIs that were created in code (not > via WTKX). > > In order to support what you are describing, we might want to add an > "automationID" property to Component. External code could use this obtain a > reference to a component and then invoke methods on it.
Which is pretty much how Flex does it as well, see: http://livedocs.adobe.com/flex/3/langref/mx/core/UIComponent.html#automationName Depends what you're doing, I suppose, but I wouldn't want to litter my code/WTKX with automation names, or at least it should be optional. 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). In Flex, I think the automation serves other purposes as well, for accessibility maybe? I've never actually used it myself though so don't know. We're using automated tools for our product but don't have the automation names specified - we just look at the right location in the component hierarchy, like I suggested above for Pivot. Cheers, Chris
