I have a question I'm a bit embarrassed to ask... yet my curiosity drives me to ask it.
Sometimes while executing a test script against an AUT, the script fails because it has trouble locating the target object. 97% of the time that I've had this failure occur, it's because it cannot find a web element object. When I think about it, this makes sense because the number of objects appearing on one particular screen within an AUT may at the very least number in the hundreds, so it is possible for the script to not find the web element before the navigation and object sync timeouts are reached.
After searching the forums, reading Tarun's book (which is great, by the way), and using the QTP help (there's a thought), I've seen a couple of possible solutions to this problem. They both involve creating descriptions and verifying whether or not objects matching the descriptions exist. However, I haven't really found an answer to the question I'm about to ask; that being: why are there multiple matches on web elements on a page when only one of each web element is visible? Is this something I can tell my developers to stop doing, or it something I'll just have to deal with.
One thing I noticed is that if you define a container object and then search the container for child objects that mach the micclass you're looking for and then count how many times the object is found, you'll see that the web element is indeed found at least twice.