Sometimes, the test code references and operates with the UI object that is different from the one expected by the test author and the test author needs to find out what UI object is actually referenced by the code.
When I am faced with this problem I use the following set of actions:
-- Set a breakpoint to pause test execution;
-- Get a Full Name of the problematic object using the Evaluate dialog and copy the obtained full name to the notepad;
-- Close Evaluate dialog, switch to the Object Browser and manually, node by node, navigate to the required problematic object using its full name copied to the notepad;
-- Analyze why test code has found exactly this object, plan how to correct this, etc.
It would be really handy if you guys enhance Object Browser so that it is possible to provide it with the full name of some object as a string and command it to drill-down to this object in the objects tree.
This improvement will significantly improve performance and convenience of test code debugging, especially for the web applications with their deep and complex objects structure.