Development Guidelines for QTP friendly controls
I'm sure many of you have had the experience of wanting to use QTP on a control or technology, and finding that the object is not recognized so that you can get and set it's critical properties (critical for testing, that is)
I've been unsuccessful at getting Mercury to provide some detailed standards and guidelines that could be forwarded to develoment groups so that this situation might be avoided.
I thought it might be a good idea to start a thread where people can drop specific examples, and after a number of contributions, we might have such a document.
1.) Develop an externally acessible COM Interface
2.) Subclassing if possible
3.) Ensure that the GUI spy can distinguish the children objects.
4.) Don't write text to bitmaps